big docs

Branch on replies and followers

An automation doesn't have to be one straight line. A branch step waits for the person's next reply and routes them down a different path depending on what it says — or on whether they follow you.

How a branch waits

When the run reaches a branch, it pauses and waits for the person to reply. Their next message picks the path:

  • Each branch arm has a condition like reply contains any of: "yes", "sure", "ok". The first arm that matches wins, checked in the order you arranged them.
  • Reply matching here is contains, not whole-word or exact — "yes please!" matches an arm keyed on yes. That's looser than trigger matching on purpose: people answer branches in sentences.
  • Every branch also has an otherwise arm. A reply that matches nothing takes it, so the run never gets stuck on an unexpected answer.

Buttons and quick-reply chips work with branches too: a tapped button can jump the run straight to any step, including a branch. See Sending DMs for the message formats that carry buttons.

The follower check

A branch arm can also test does this person follow you? When the run reaches it, big asks Instagram for the person's live follow status and routes accordingly — follower one way, non-follower the other.

If the check can't complete (Instagram doesn't answer in time, say), the run takes the otherwise arm rather than stalling. Design that arm so it reads fine for someone whose status you couldn't confirm.

The re-check loop

The classic use: "Follow me, then tap ✅ when you're done." A follower-check branch can loop back to itself — the person taps, big re-checks, and if they still haven't followed, asks again.

Loops are always bounded. You set a maximum number of tries on the branch, and the builder requires an after N tries exit arm. When the person burns through all their attempts without following, the run takes that exit instead of prompting forever. Give it a graceful message; some people just won't follow, and that's fine.

Things worth knowing

  • While a run is parked at a branch, new messages from that person continue the run — they won't start a different automation until this one finishes or expires.
  • A branch reply still has to arrive inside the messaging window. If the person goes quiet past the window, the run expires where it stands.
  • The follower check costs a live Instagram lookup, so it happens only when the person actually reaches that branch.

Next step

If a branched flow ever seems stuck, "Why didn't my automation fire?" covers the wait-and-window cases.

Branch on replies and followers | big