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
Collect Input
AI-generatedSummary
Send a COLLECT_INPUT action to the RAW callback endpoint, asking the chat user for configured fields and directing the session to a next step after collection.
Inputs
- Callback URL / Environment (required) — For version 1, provide the callback URL, which defaults to
meta.callbackUrlfrom the input item. Version 2 defaults to Auto and uses that same payload URL; you can instead select Homologation or Production, or provide a custom callback URL when Custom is selected. - Client ID (required) — Identifies the RAW client; defaults to
meta.clientIdfrom the input item. - Chat ID (required) — Identifies the chat session; defaults to
meta.chatIdfrom the input item. - Bot ID — Optional bot identifier; defaults to
meta.botIdfrom the input item. - Fields (JSON) (required) — Array of fields to collect. Each field can include a field name, question, and validation; declared validation types are
text,number,cpf,cnpj,cpf_cnpj,phone,date,email, andregex. - Next Step (required) — Step to set in the
COLLECT_INPUTaction for the session after collection. - Next Sub Step — Optional substep included in the action when nonempty.
- Next Step / Next Sub Step — Optional shared parameters that update the session step or substep alongside the action; the operation-specific Next Step and Next Sub Step are also included in the action when configured.
Output shape
One output item per input item, containing { ok: true, operation, response } after the callback request succeeds.
Posts a JSON body containing the client ID, chat ID, optional bot ID and shared step updates, and a
COLLECT_INPUTaction with the configured fields and operation-specific next step/substep. With Continue On Fail enabled, a failed item returns{ error }; otherwise the node throws an item-level error.