Node reference

Response nodes

A response node is where the workflow answers. Flux ships ten, and the rule is simple: match the response to the trigger the conversation came in on.

All ten

Response	Sends to	Use with
Chat	The generated chat UI	UI trigger
Webhook	Back to whoever called the endpoint	API trigger
WhatsApp	The WhatsApp conversation	WhatsApp trigger
WhatsApp Broadcast	Many WhatsApp recipients at once	Interval or spreadsheet trigger
Viber	The Viber conversation	Viber trigger
Telegram	The Telegram conversation	Telegram trigger
Facebook	The Facebook conversation	Facebook trigger
Instagram	The Instagram conversation	Instagram trigger
Outbound Chat	Back into Cognify	Inbound Chat trigger
Outbound Chat (Generic)	Back into any system you wired up	Inbound Chat (Generic) trigger

A mismatched pair is the most common reason a bot "does not reply". The workflow runs fine and the logs look healthy — the answer simply went somewhere the customer is not looking.

A workflow with three triggers on the left feeding one AI node, which fans out to three matching channel response nodes on the right

Screenshot to be added

Several channels, one brain — each with its own response node.

What goes in a response

The message is built with template expressions, usually pulling the AI node's answer:

{{POUT response}}

You can mix static text and expressions freely, which is how you add a signature, a disclaimer or a reference number the model did not produce.

Chat response

Answers in the interface the UI trigger generates. The right one for testing and for an internal tool where you do not need a public channel.

Webhook response

Returns data to whatever called the API trigger, which is what makes a workflow usable as a service. Shape the body deliberately — the caller is a program, not a person, so return a stable structure rather than prose. See Web and API channels.

The messaging responses

WhatsApp, Viber, Telegram, Facebook and Instagram each send back on their own channel, using the credential you stored when connecting it. Setup is covered in Messaging channels.

WhatsApp Broadcast

The one response node that is not a reply. Instead of answering one conversation it sends to many recipients, which makes it the outbound counterpart to the others.

Pair it with a spreadsheet trigger to message a list, or an interval trigger for a recurring send.

Broadcast messaging is governed by WhatsApp's own template and opt-in rules, and by messaging law in your recipients' countries. Send only to people who agreed to hear from you — the penalty for getting this wrong is losing the number.

Outbound Chat, and its generic twin

Outbound Chat

Sends the answer back into Cognify, onto the record the conversation belongs to.

Outbound Chat (Generic)

Sends it back to whatever system you connected, when Flux is running behind something other than Cognify.

More than one response

A workflow can hold several response nodes — one per branch of a Decision, or one per channel. Only the ones on the executed path actually send.