Receive Message | Chatigram Documentation

Plan availability #

Feature	Free	Starter	Pro	Enterprise
Active workflows	3	10	45	Unlimited

Allowances follow the published Chatigram pricing page. Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.

When to use this node #

Wait and receive the next message of the selected types

Add Receive Message to a workflow branch using the node picker. Configure its fields in the inspector, then connect the next step.

Ask, then wait for the answer #

Place Receive Message after the step that asks the customer a question. It waits for the next message of the types you select; it does not send the question itself or create a customer conversation for a Manual workflow.

For example, Send Text Message asks for an order number, Receive Message accepts Text, and the next node uses Text Message from this received reply to look up the order.

Choose message types and branches #

Select the types your workflow can handle: Text, Audio, Image, Video, or File. Connect each selected type’s branch to suitable processing. Do not connect every attachment to a step that assumes plain text.

The visible branches depend on those selections. If you change the accepted types later, inspect the branch labels and their connected steps again. Enable at least one intended type rather than leaving the node without a useful input path.

Use the received outputs #

Output	How to use it
Message ID	Identify the received message, including when passing an attachment to a compatible processing node
Text Message	Read the text reply when Text is selected and that path receives text
Caption	Use an attachment’s caption when present; it may be empty
Attachment URL	Refer to attachment content where the following action supports that value

Choices in the variable picker depend on the enabled types. An output being selectable does not mean it has a value on every message-type branch.

For speech or images, follow attachment processing with the actual Message ID and a supported connection. An audio message is not a text transcript, and a file is not automatically parsed into fields.

Check the reply before using it #

Use Check condition for text checks or numeric thresholds after validating the input. Ask for a corrected value when the received answer does not fit the task. Do not assume an order number, amount, or date is valid simply because a text message arrived.

Understand a waiting run #

A run can remain waiting while the customer has not sent the expected reply. Check the selected types, source conversation, and Workflow Activity before treating that as a failure. A message outside the selected types does not provide the text or attachment output your next step expects.

Test each selected type with a controlled conversation. For Inbox-based follow-up, use a team-supported Line; Private AI mode hides its conversations from human agents even when the automated workflow can receive messages.

This node needs conversation context. Use it in a conversation workflow; a Manual or scheduled trigger does not create a customer conversation by itself.

Configure the fields #

Field	What to enter
Text	Receive text messages
Audio	Receive audio messages
Image	Receive image messages
Video	Receive video messages
File	Receive file messages

Use the result #

Choose the output from the variable picker in a later step. Output names below identify the values supplied by this node; the picker inserts the correct reference for your node instance.

Output	Meaning / label
`messageId`	Message ID
`textMessage`	Text Message

Connect the next step #

Connect the continuation shown on the canvas. Some nodes calculate their branches from the configured options. Read each branch label in the editor and connect the paths your workflow needs.

Test it in a workflow #

Configure this node with a small, recognizable test input or a test resource.
Check the variables from preceding steps and the connection selected in the inspector.
Save the workflow. For event-driven flows, generate the actual event; use Run only for a Manual workflow.
Open Workflow Activity and check the outcome before enabling wider use.

If something goes wrong #

Check empty variables, selected resource IDs, and any fields that appeared after resource selection.
Check the failed step in Workflow Activity before retrying. If the action may already have completed, inspect the destination first to avoid duplicates.
Follow the troubleshooting guide for a symptom-by-symptom checklist.

Catalog coverage #

This is the currently documented selection. Chatigram continues to add nodes, triggers, App Connections, and integrations. Use each page’s review date and the current application selectors to check what is available now; this catalog is not a fixed limit on future features.