Contacts can only be active in one Messaging flow at a time. Background flows solve this limitation by letting you run automation without interrupting an active conversation. They are ideal for behind-the-scenes work like updating contact fields, moving contacts into groups, triggering integrations, or running scheduled processing.
In this guide, you’ll learn how to create a Background flow, what Background flows can (and can’t) do, how they avoid interrupting active Messaging flows, and how to start them manually or on a schedule.
Create a Background flow without breaking active conversations
If you already know what you need and just want the fast path, follow this:
- Confirm your use case fits Background (no replies needed)
- Go to Flows and click New Flow
- Set Flow type = Background
- Add your action nodes (Update Contact, Add to Group, Webhook, etc.)
- Use Background to run in parallel (avoid the “one Messaging flow at a time” issue)
- Start it manually or schedule it
You’re done. Your automation can run without taking control of the contact’s replies.
Step-by-Step Process
Use a Background flow when you need to:
- Perform updates on a contact without asking questions
- Run actions while a contact is already in an active Messaging flow
- Trigger integrations (webhooks, Zapier events) without changing the user’s conversation
- Execute maintenance logic like tagging, grouping, or enrichment
- Log in to your RapidPro.app workspace.
- Click the Flows tab at the top navigation.
- Click New Flow (top-right).
[CAPTURE: Flows page showing the “New Flow” button in the top-right.]
- In the New Flow dialog:
- Enter a clear flow name (example:
Post-Survey – Update Fields) - Open the Flow type dropdown
- Select Background
- Choose the editing language (for builders)
- Enter a clear flow name (example:
- Click Create to open the flow editor.
[CAPTURE: New Flow dialog showing Flow type = Background selected.]
Background – Partner Sync).
- Add one or more action nodes based on what you want the flow to do.
- Connect nodes in a clear, mostly vertical layout.
- Save each node as you configure it.
[CAPTURE: Background flow in the editor with several action nodes connected vertically.]
Most actions available in Messaging flows are also available in Background flows.
Common actions you can use:
- Send Message (send text/media to the contact)
- Send Message to Someone Else (notify a supervisor)
- Add an additional URN (add a new contact address like email, phone, Telegram ID)
- Add / Update Contact Fields
- Add / Remove Contacts from a Group
- Call a Webhook
- Send an Email
- Set Contact Preferred Language
- Start Another Flow (Background → Background only, in many environments)
- Start Someone Else in a Flow
- Open a ticket (if ticketing is enabled)
- Call Zapier (send data to external tools)
- Send Airtime (if enabled)
- Create splits (branching), such as:
- By expression
- By contact field
- By group membership
- Random split (A/B)
- Other supported split types
[CAPTURE: Action type dropdown in a Background flow showing available actions and split options.]
Messaging flow rule: a contact can only be active in one Messaging flow at a time.
What can happen:
- If you start a second Messaging flow for a contact, it may interrupt their current flow.
- This can cause confusing conversations and incomplete data.
A Background flow avoids this because it can run in parallel without taking control of the contact’s message handling.
[CAPTURE: Two screenshots: (1) a contact being interrupted when a Messaging flow starts, (2) the same contact not interrupted when a Background flow starts.]
You can start contacts in a Background flow in two common ways:
Option A — Start manually (immediate)
- Open the Background flow in the flow editor.
- Click Start Flow.
- Choose contacts or groups.
- Start it immediately.
[CAPTURE: Flow editor showing the Start Flow button and contact/group selection for a Background flow.]
Option B — Schedule it for later (or repeat)
- From the flow editor (or scheduling tools in your workspace), choose the option to schedule the flow.
- Select:
- Start date/time
- Optional repetition (daily/weekly/monthly)
- Save the schedule.
[CAPTURE: Scheduling screen showing a Background flow scheduled for the future with a repeat option.]
Common Issues & Quick Fixes
Problem: I can’t find “Wait for Response” in my Background flow.
Fix: This is expected: Background flows cannot collect replies. If you need responses, create a Messaging flow instead. If you only need silent updates, keep the flow as Background.
Problem: My Background flow interrupted a contact anyway.
Fix: Confirm the flow type is actually Background. Then check if a separate trigger or campaign started a Messaging flow at the same time. Review automation rules to avoid launching multiple Messaging flows in parallel.
Problem: I tried to enter another flow from a Background flow and it didn’t work.
Fix: In many environments, Background flows can only start other Background flows. If you need to start a Messaging flow, do it from Messaging triggers/campaigns—or redesign so the Background flow prepares data and the Messaging flow handles interaction.
Problem: I scheduled a Background flow but nothing happened.
Fix: Confirm the schedule is active and set to the correct timezone (workspace timezone matters). Confirm the target contacts/groups are not empty. Check the flow contains at least one action node (a blank flow won’t do anything). Review workspace limitations if scheduling is restricted.