Actions21
- Add Chat State
- Close Chat
- Collect Input
- Go To Step
- Go To Substep
- Mark Read & Show Typing
- Register Disposition
- Register Transaction
- Request Human
- Send Button
- Send Catalog Message
- Send Document
- Send List
- Send Product Carousel
- Send Product List
- Send Single Product Message
- Send Text
- Send WhatsApp Flow
- Set Flow State
- Start Survey
- Transfer Department
Send Button
AI-generatedSummary
Send a button message to a RAW chat by POSTing a SEND_BUTTON action to the configured callback URL. Configure up to three reply buttons in the form or provide them as JSON; button routes can trigger chat actions when selected, and optional retry settings apply when routes are configured.
Inputs
- Callback URL / Environment (required) — For node version 1, provide the callback URL, defaulting to
{{$json.meta.callbackUrl}}. Version 2 defaults to Automatic and readsmeta.callbackUrlfrom each input item; Homologation and Production use their RAW callback endpoints, while Custom requires a full callback URL. - Client ID (required) — Defaults to
{{$json.meta.clientId}}and is included in the callback request. - Chat ID (required) — Defaults to
{{$json.meta.chatId}}and identifies the chat receiving the message. - Bot ID — Defaults to
{{$json.meta.botId}}; when non-empty it is included so the server can use that bot’s configuration. - Title (required) — Title displayed in the button message.
- Description (required) — Description displayed in the button message.
- Footer — Optional footer text.
- Button input mode (required) — Choose Form or JSON. Form mode supports up to three buttons, each with display text, ID, and an optional click action: close chat, request a human, go to a step, or transfer department. Department ID and message apply to human/transfer routes; Step applies to go-to-step routes. JSON mode takes an array of button objects; an optional
routeis extracted by button ID and used as its click action. - Retry Limit — Defaults to 0 (disabled). When greater than 0 and button routes are configured, sets the number of attempts before the exhausted action is used.
- On Exhausted — Fallback action after retries: request a human, go to a step, transfer department, or close the chat. Step is available for go-to-step; Department ID and Message are available for human or department transfer.
- Next Step — Optionally updates the session step with the action without navigating to it.
- Next Sub Step — Optionally updates the session sub-step with the action.
Output shape
One output item per input item, containing { ok: true, operation, response } on success.
The node POSTs JSON to the callback URL with clientId, chatId, optional botId/step/sub-step, and a
SEND_BUTTONaction; when routes exist it also sends aSET_FLOW_STATEaction containing those routes and optional retry settings. With Continue On Fail enabled, a failed item instead returns{ error }; otherwise the node raises an item-indexed error. Theresponsefield contains the callback response, ornullif none is returned.