← Help centre

Chatbot flows in the visual builder

Where: Automations > "My automations", then open or create a flow.

The flow builder lets you design a full conversation. Available blocks include:

  • Send a message, with or without media.
  • Ask a question and wait for the answer — with a timeout branch, so someone who never replies gets a reminder instead of being forgotten.
  • Buttons and quick replies, each opening its own branch.
  • A card carousel (Instagram and Facebook).
  • Delay: wait seconds, minutes, hours or days (decimals work: 1.5 hours), a random time between two values so replies don't look automated, or until a date — a fixed one, or one saved in a field or an answer, such as the day before an appointment. A delay can also be limited to some days and hours, so nothing goes out at 3 a.m.
  • Conditions: branch on the person's last answer, their tags and custom fields, the network, the day and time, or whether they have already been through this automation. Each branch can combine several rules.
  • Whether the person follows you (Instagram).
  • Add or remove tags, save or clear a custom field, capture an email, and enrol the contact in a sequence or take them out of one.
  • Book an appointment with buttons (service → day → time → details), without AI. See "Appointments".
  • Ask the AI to answer freely using your knowledge base, once ("AI answer") or across a conversation ("AI agent"). Each reply uses 1 AI credit, or 1 per 3 if you untick "Use what Ignix knows about your business"; by DM it also counts as a DM. Both blocks can have exits with a condition (below).
  • Hand the conversation to a human.
  • Team: notify your team (the conversation owner, a person or a team), change the conversation's status in the inbox, or pause the bot for this contact — without sending the person anything.
  • HTTP request: call Zapier, Make, a webhook or your own API, and save values from the answer to use later in the flow.
  • Go to another automation: jump to another flow and continue there, in the same conversation. Automations whose trigger is "Only from another automation" exist to be reached this way.
  • A/B split, to alternate between two branches and compare results.
  • Random split, to send people down 2 to 6 paths by weight (optionally always the same path for the same person). It doesn't measure results: for that, use the A/B split.

Texts can carry variables, such as {{first_name}}, a contact field or a question's answer, with a fallback in case it's empty: {{first_name|there}}. In comment flows there are also {{comment_text}} (the comment) and {{post_text}} (the post). AI blocks take them in their instructions, and they already know on their own the comment and post that brought the person in, what was said to them in public, their answers, fields and tags.

On the trigger, Only once per person makes sure someone who already went through the automation doesn't get it again if they repeat the keyword or comment again. On comment automations you choose whether that counts across the whole automation or per post.

The full list of blocks, with every field, is in "Automation nodes and triggers".

Step by step

  1. Go to Automations > "My automations".
  2. Create a flow and choose the trigger (a comment, a DM, a keyword, a story reply).
  3. Drag blocks onto the canvas and connect them.
  4. Save and activate the flow.

Quick templates: the "Templates" tab has ready-made automations you can set up by filling in a short form, without touching the builder.

Exits with a condition on AI blocks

"AI answer" and "AI agent" can each have up to five Exits with a condition, written in your own words: "gets the answer right", "wants prices or to hire us", "is upset or mentions a refund". When one clearly applies, the AI writes nothing and the flow carries on through that exit, so whatever you connect does the answering: a fixed public reply with variants, another AI block that uses your knowledge, a DM with a button, "First come only" so there is a single winner, or a hand-off to a person. When none applies, the AI answers as usual.

  • Deciding costs the same as a reply: 1 credit, or 1 per 3 when the block doesn't use what Ignix knows about your business.
  • In "AI agent", taking an exit ends the AI conversation and the flow continues from there — on to booking, for example.
  • The exit formerly called "Escalate" is now Asks for a person. "Escalate to a human if the AI can't answer" only shows when the block uses your knowledge.

A typical recipe for a comment game: an AI block without knowledge replies in public → exit "gets it right" → a public reply plus a DM with a fixed text and a button → an AI block with knowledge, now in DMs, to inform or book. The button matters: the first DM after a comment is Instagram's private reply, which allows only one message until the person answers, and tapping the button opens the conversation.

Vary with AI

When the same message goes out to a lot of people, it starts to look like what it is: an automated message. Under the text of every block that sends something (message, buttons, question, media, public reply…) there is a check, Vary with AI. When you save, Ignix writes fifteen versions of that message — same meaning, same tone, same language, with links, codes and numbers kept exactly as they are, and never longer — and each person gets a different one, picked at random alongside yours. There is nothing to review: the versions aren't shown, and if you edit the text they are discarded and written again.

It comes with every paid plan, with AI turned on in the workspace. If you turn it off or leave your plan later, the versions already written keep working; new ones just stop being generated.

Media in a DM

What travels, and how, depends on the network. On Instagram and Facebook a message with buttons is a template, and a template only carries an image. So each kind of file takes the route that looks best in the chat:

What you attachHow it arrives on Instagram and Facebook
ImageInside the message, above the buttons
VideoAs its own message right before the buttons — it plays in the chat
AudioAs its own voice message
DocumentAs a link button you name, pointing at your file

Documents can be PDF, Word, Excel, CSV or ZIP, up to 200 MB, and they live on our own domain — you do not have to paste a Drive or Dropbox link into a DM and hope people trust it. Name the button ("Download the guide") and we fill in the link. Its taps are counted like any other button in the flow.

On WhatsApp and Telegram the media travels alongside the buttons, so nothing changes there.

Two limits that Instagram enforces quietly, without an error:

  • Audio must be AAC, M4A, WAV or MP4. MP3, OGG and WebM are dropped — a recording made in Chrome or on Android is WebM, while Safari records MP4.
  • A video attached to a DM cannot exceed 25 MB.

The builder warns you about both before you send.

All articles

Chatbot flows in the visual builder — Ignix Help