The Flow Builder lays an automation out on a canvas, so it can branch, wait and tag. Connect blocks by dragging from one block’s output to the next block.
Blocks
- Trigger — where the flow starts.
- Message — up to 640 characters, with up to 3 buttons or up to 11 quick replies. A button with a link opens it (and is tracked); a button without a link continues the flow. Messages can be sent as a private reply to the comment or as a DM.
- Condition — checks whether they follow you, have a tag, are subscribed, or wrote certain words. Match all rules or any, then continue down the “yes” or “no” path.
- Delay — waits between 1 second and 30 days.
- Action — adds or removes tags, subscribes or unsubscribes the contact, and sets up to 5 fields. Each field can be set for this contact or for the whole account (a bot field), and values can use tokens such as {{username}}. Every value in one step is worked out before any of them is saved, so one row can’t read what another row in the same step writes.
- Randomizer — sends people down one of 2 to 5 paths at random, weighted however you like (for example 50/50), so you can compare two versions.
- Start automation — hands the conversation to another automation. By default this flow stops once the other one takes over.
- Note — a sticky note for you and your team. It never sends anything.
Triggers
An automation can have several triggers — comments, DM keywords, story replies, or any DM that no other live automation answers. Add one with New trigger and switch each on or off on its own; every trigger that’s on can start the flow. Trigger changes save right away.
Personalize
Use the Personalize menu in a message to insert the contact’s first name, full name or @username, your account name, or any custom field. Tokens work in message text and button labels. Add a fallback for people whose details you don’t have: {{first_name|there}} becomes “there” when there’s no first name.
Drafts, publishing and version history
Your edits are saved as a draft — marked “Draft — unpublished changes” — while live conversations keep running the published version. Publish to make your changes live. Open History to see earlier versions; restoring one copies it into your draft, and you publish it when you’re ready.
Checks before you publish
The builder lists anything that needs fixing before going live — a condition missing its “yes” or “no” path, or a delay with nothing after it. The preview panel shows the conversation as the contact will see it.
Metrics
Open Metrics for the automation’s runs, sends, clicks, click-through rate and unique contacts, plus sends per day. Each step on the canvas shows its own sends, clicks and click-through rate. Instagram doesn’t report deliveries or reads, so MuChat doesn’t either.
Tidying the canvas
Auto-arrange lays a flow out neatly in one click; zoom in and out, or fit the whole flow on screen.
Delays and the 24-hour window
Delays are scheduled on MuChat’s side and run even when nobody is logged in. Instagram only lets businesses message someone within 24 hours of their last message, so long delays are only useful if the person has written again by then.
Didn’t answer your question?
A person reads every email. Tell us your workspace name and what you were trying to do.