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 List
AI-generatedSummary
Sends a list message to a RAW chat through its callback endpoint. Configure list rows using a form, JSON sections, or an input array; rows can carry selection routes, and the node can also set retry handling for routed selections.
Inputs
- Callback URL / Environment (required) — For node version 1, provide the callback URL (defaults to
meta.callbackUrl). For version 2, choose automatic (readsmeta.callbackUrlfrom the input item), Homologação, Produção, or a custom callback URL. - Client ID (required) — RAW client ID; defaults to
meta.clientIdfrom the input item. - Chat ID (required) — Target chat ID; defaults to
meta.chatIdfrom the input item. - Bot ID — Optional bot ID; when supplied, RAW uses that bot's configuration. Defaults to
meta.botId. - Title, Description, Button Text (required) — Text shown with the list and on the button that opens it. Button Text defaults to “Ver opções”.
- Footer Text — Optional footer shown with the list.
- Modo Das Linhas — Choose Formulário, JSON, or Mapear De Array (Loop).
- Rows or Sections (required) — Formulário: enter up to 10 rows with Row ID, title, description, and optional per-row action. JSON: provide sections containing rows such as
{ "rowId": "1", "title": "Opção 1", "description": "" }; JSON rows may include arouteproperty. Array: provide an array (defaults to$json.items) and map its ID, title, and optional description fields. Array rows share one configured selection action. - Selection routes — Rows can have no action, close the chat, request a human, transfer department, or go to a step. Human and transfer routes can include a department ID and message; go-to-step routes can include a step. With no route, the selected row ID is available to the workflow.
- Retry Limit and On Exhausted — Retry Limit defaults to 0 (disabled) and only applies when routes are configured. If attempts are exhausted, choose request human, go to step, transfer department, or close chat; the applicable step, department ID, and message fields are optional.
- Next Step and Next Sub Step — Optional session values updated with the action; Next Step does not navigate to that step.
Output shape
One output item per input item, containing { "ok": true, "operation": "sendList", "response": ... } on success.
The node POSTs an action to the callback URL. If Continue On Fail is enabled, a failed item returns
{ "error": "..." }; otherwise the node raises an item-indexed operation error. Invalid JSON used for sections or array input falls back to an empty object/list, so provide valid JSON or an array.