Nodes Reference

Every chatbot flow is built from nodes — the building blocks that define what happens at each step of a conversation. The editor provides 17 node types in six categories, listed in the node sidebar. Drag a node onto the canvas, then double-click it to configure.

In the app: Dashboard → Automation → Chatbot → [Edit] → node sidebar

Trigger nodes are the entry points of a flow. Which one fires depends on the chatbot's trigger type, set when you create it (see Triggers & Variables).

Starts the flow on the first contact ever from a new customer, and fires once per contact. No configuration. Use it for onboarding and first-time welcome flows.

Starts the flow when an incoming message matches the chatbot's keywords or pattern. This is the entry point for keyword, exact-match, starts-with, and regex chatbots. The match itself is configured by the chatbot's trigger type and keywords, not on the node.

Nodes that send content to the customer. They're send-only: they don't wait for a reply. Use an input node when you need to capture an answer.

Send text, an image, a video, or a document.

Add attachment opens a picker. Upload a new file, or pick one from your Media Library.

The selected file is confirmed in the dialog before you apply it.

Once attached, the button becomes Change attachment, and the file name shows on the node.

When to use: Welcome messages, confirmations, instructions, or sending media — any message where you don't need a reply.

Send a message with a single clickable button that opens a URL.

Personalize the body with the </> picker. Insert a customer field such as their name:

Or a contact attribute, referenced with dot notation:

When to use: Driving customers to a product page, a smart link, a booking page, or any external destination from inside the chat.

Nodes that send a message and wait for the customer's reply. The reply is captured for use later in the flow.

Ask a free-text question and wait for the customer to type a reply.

The Save response to variable dropdown lists existing variables, or use + to create one inline.

Pick a validation rule to enforce the reply's format: None, Regex, Email, Phone, or Number.

With a rule set, an Invalid message appears for the customer if their reply doesn't pass.

Send up to 3 quick-reply buttons and wait for the customer to tap one. Each button becomes its own branch.

Each button you add gets its own row and its own outgoing edge. Connect each edge to the next node for that choice.

Send a scrollable list of options grouped into sections, and wait for the customer to select one. Use it when you need more than three choices or want descriptions.

Build the list with as many sections and rows as you need. Each section groups related options under a heading.

When to use: Menus with 4+ options, product or service categories, or any selection that benefits from descriptions.

Nodes that control the path and manage data.

Branch the flow by comparing a variable against a value. Add one or more conditions; each row has a variable, an operator, and a value.

The operator dropdown offers six comparisons: Equal to, Not equal, Greater than, Less than, Greater than or equal, Less than or equal.

Stack multiple conditions to test more than one thing at once.

Each condition compares a variable against a value, which can itself be another variable.

When to use: Routing on a customer's answer, gating on a contact attribute, or checking an API result before the next step.

Assign a value to a variable, for storing data, setting a flag, or preparing a value for a later node.

When to use: Storing computed or copied values, setting flags, or seeding a default before a Condition.

Nodes that connect the flow to forms, your own APIs, and outbound messaging.

Send a Form as a link button and wait for the customer to submit it. Submitted fields are saved to a variable for use later in the flow.

Pick the form to send from your published forms.

The submission is stored in an object variable — create one with + if you don't have it yet.

Once a form is selected, its available fields are listed (for example form_response.name, form_response.phone, form_response.rating) so you can reference individual answers downstream.

When to use: Lead capture, surveys, appointment booking, or any structured data collection mid-conversation.

Call an external API and use the response in your flow — look up an order, check inventory, or create a record in your CRM.

When to use: Order lookups, inventory checks, CRM writes, or any external data the flow needs to branch on.

Send an outbound message via the Enotify API. Useful for notifying a different number than the one in the conversation.

Fill in the token, recipient, and message body.

When to use: Internal alerts, notifying a second number, or sending a confirmation through the API.

Nodes that act on the conversation and the contact: assignment, tagging, attributes, and tickets.

Assign the conversation to one or more specific agents in Team Chats.

Once saved, the node shows the assigned agent on the canvas.

When to use: Routing to a known account manager, VIP handling, or direct assignment based on flow logic.

Route the conversation to a skillset. The next available agent with that skill picks it up.

You can route to several skillsets at once.

When to use: Skill-based routing after the bot identifies the need (for example, customer chose "Technical issue" → Technical Support skillset).

Add or remove tags on the customer's contact during the flow.

Add and remove in the same node — useful for swapping a contact from one stage tag to another.

When to use: Auto-categorizing leads ("interested", "hot_lead"), marking flow completion, or clearing outdated tags.

Update one or more contact attributes on the customer's profile.

Choose the attribute and give it a value. Add more assignments to set several at once.

When to use: Saving preferences, recording data collected in the flow, or updating profile fields for later segments.

Create a support ticket from the conversation.

Set the urgency with the priority dropdown.

Pick assignees and tags, and optionally save the new ticket's number to a variable to reference it later.

The completed node carries everything an agent needs to pick the ticket up.

When to use: Logging issues that need follow-up, capturing complaints, or any conversation that should become trackable work.