Logic Flow node reference

Waaru groups 28 Logic Flow nodes by the job they perform. Choose the node that makes the next customer-visible or operational step explicit.

Triggers

• Keyword starts from a matching inbound text.
• Conversation entry starts when a conversation enters the eligible flow path.
• Fallback handles inbound activity that did not match another automation.
• Template quick reply starts from a reply button on a template message.
• Click-to-WhatsApp starts from eligible referral context.
• Received media starts when the inbound message contains an eligible image, video, audio file, or document.

Use one clear entry intent per flow. Overlapping triggers make ownership harder to reason about.

Messages

• Text sends a text message.
• Media sends supported image, video, audio, or document content.
• Reply buttons presents a small set of tap choices.
• List presents a longer structured choice list.
• Template sends an eligible approved template.
• WhatsApp Flow form opens a configured form experience.
• Location sends a location.
• Contact card sends contact details.
• Catalog message sends a linked catalog, one product, or a product list. Use the catalog linked to the flow’s WhatsApp Business Account and sending number. A missing or mismatched catalog prevents the message from sending.

Interactive messages should always have a meaningful next connection. Keep the copy understandable even when a customer reads it without the rest of the flow diagram.

Collection and data

• Collect response waits for and validates the customer's next answer.
• Set variable stores a value for later nodes in the same journey.
• Update contact field changes one supported contact value.
• Update contact tags changes the contact's supported classification.

Treat customer input as untrusted. Use the configured validation and a recovery path for invalid responses.

Routing

• Condition evaluates ordered named branches with all/any conditions and a no-match fallback.
• Short delay waits from 1 to 10 seconds for conversational pacing.
• Jump continues at another node in the same flow.
• Published sub-flow enters a pinned published version of another flow.
• Exit ends the current flow path.

The short delay is for message pacing, not future scheduling. A sub-flow remains pinned to its selected published version until you update and republish the parent configuration.

Integrations and Inbox

• Integration action runs an action currently available in the workspace action catalog.
• Handoff or assign transfers the conversation to an eligible teammate or queue.
• Conversation status updates the active session state.
• Internal note adds team-only context to the conversation.

Only select an integration action that the editor reports as available. Always connect an error or handoff path where a failed external action would otherwise leave the customer waiting.

Configure more than the node name

Follow response validation and ordered routing, published sub-flow mappings, and connected action setup for the required fields, outputs and recovery paths.

Next: Publish and troubleshoot the flow.