{
  "nodes": [
    {
      "parameters": {
        "resource": "group",
        "operation": "createGroup",
        "groupName": "My Automated Group",
        "phones": "5511999999999,5511888888888"
      },
      "name": "Create Group",
      "type": "n8n-nodes-wafly.wafly",
      "typeVersion": 1,
      "position": [250, 300],
      "credentials": {
        "waflyApi": "Wafly API"
      }
    }
  ]
}

Example 3: Check the instance status

{
  "nodes": [
    {
      "parameters": {
        "resource": "instance",
        "operation": "getStatus"
      },
      "name": "Check Status",
      "type": "n8n-nodes-wafly.wafly",
      "typeVersion": 1,
      "position": [250, 300],
      "credentials": {
        "waflyApi": "Wafly API"
      }
    }
  ]
}

Example 4: Let your AI agent understand voice notes

Half of every WhatsApp conversation in Brazil is a voice note, and an LLM cannot
listen. Set Audio Transcription makes the transcript arrive in the webhook,
so you skip building download + speech-to-text.

The OpenAI key is yours — the cost lands on your own OpenAI account and Wafly
charges nothing for it. It is stored encrypted and never returned by the API.

{
  "nodes": [
    {
      "parameters": {
        "resource": "instance",
        "operation": "setTranscription",
        "transcriptionApiKey": "sk-proj-...",
        "transcriptionMaxAudioSeconds": 300,
        "transcriptionMonthlyCap": 500
      },
      "name": "Transcribe Voice Notes",
      "type": "n8n-nodes-wafly.wafly",
      "typeVersion": 1,
      "position": [250, 300],
      "credentials": { "waflyApi": "Wafly API" }
    }
  ]
}

Run it once per instance. After that, the audio webhook carries:

{
  "audio": { "audioUrl": "https://...", "seconds": 4 },
  "transcription": { "status": "ok", "text": "oi, queria saber o preço", "latency_ms": 1180 }
}

If the provider refuses (wrong key, quota) or the monthly cap is reached, **the
message still arrives** — only with transcription.status = "error" and the
reason. Nothing is lost.

Leave the key field empty on later calls to keep the stored key and change only
the limits.

Example 4: Stop your AI agent from answering three times

Nobody writes a paragraph on WhatsApp. People send hi, then you there?, then
how much is it? — three separate webhooks, so an AI agent replies three times,
and the first two replies were written without knowing what the person was still
about to type.

Set Message Buffer groups those into a single webhook call:

{
  "nodes": [
    {
      "parameters": {
        "resource": "instance",
        "operation": "setMessageBuffer",
        "bufferWindowSeconds": 8,
        "bufferMaxWaitSeconds": 30,
        "bufferMaxMessages": 10,
        "bufferMode": "concat",
        "bufferIncludeGroups": false
      },
      "name": "Group Split Messages",
      "type": "n8n-nodes-wafly.wafly",
      "typeVersion": 1,
      "position": [250, 300],
      "credentials": {
        "waflyApi": "Wafly API"
      }
    }
  ]
}

Run it once per instance — it is a setting, not a per-message step.

What your webhook receives after that. Before:

POST /your-webhook   { "text": { "message": "hi" } }
POST /your-webhook   { "text": { "message": "you there?" } }
POST /your-webhook   { "text": { "message": "how much is it?" } }

After:

{
  "phone": "5511999999999",
  "text": { "message": "hinyou there?nhow much is it?" },
  "buffered": { "count": 3, "messageIds": ["...", "...", "..."], "waitedMs": 8012 }
}

The payload keeps the exact same shape, so **an existing workflow keeps working
without edits** — your AI Agent node just receives the whole thought at once.
When a single message arrives, the payload is identical to before, without the
extra buffered field.

| Field | Default | What it does |
|—|—|—|
| Window (seconds) | 8 | Silence window. Restarts on every new message, so delivery happens when the person stops typing. Max 20. |
| Max Wait (seconds) | 30 | Hard ceiling from the first message, so someone typing non-stop cannot postpone delivery forever. Max 30. |
| Max Messages | 10 | Deliver immediately once this many pile up. Max 50. |
| Mode | concat | concat keeps the usual payload shape. batch adds a bufferedMessages array and changes it. |
| Include Groups | false | Grouping in group chats is per participant — different people never get merged. |

> Media, reactions and button replies are never grouped. If text is still waiting
> in the window when an audio arrives, the pending text is delivered first, so
> the conversation never reaches your agent out of order.

Use Get Message Buffer to read the current setting and **Disable Message
Buffer** to go back to one webhook call per message.

Example 4: Full workflow — daily message

This workflow sends an automatic message every day at 9am:

{
  "name": "Daily WhatsApp Message",
  "nodes": [
    {
      "parameters": {
        "rule": {
          "interval": [
            {
              "field": "cronExpression",
              "expression": "0 9   *"
            }
          ]
        }
      },
      "name": "Cron - 9am Every Day",
      "type": "n8n-nodes-base.cron",
      "typeVersion": 1,
      "position": [250, 300]
    },
    {
      "parameters": {
        "resource": "message",
        "operation": "sendText",
        "phone": "5511999999999",
        "message": "Good morning! Automatic 9am reminder."
      },
      "name": "Send Message",
      "type": "n8n-nodes-wafly.wafly",
      "typeVersion": 1,
      "position": [450, 300],
      "credentials": {
        "waflyApi": "Wafly API"
      }
    }
  ],
  "connections": {
    "Cron - 9am Every Day": {
      "main": [
        [
          {
            "node": "Send Message",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  }
}

📚 API documentation

For more information about the available endpoints and their parameters, see the full API documentation: