Step-by-Step Guide: How to Start Your First Flow

Flows are how you automate conversations in RapidPro.app. In a flow, you build steps (messages, questions, decisions, updates) that guide contacts through a structured interaction. Creating a flow is the first step before you can test logic, connect triggers, or launch to real users.

In this guide, you’ll learn how to create a new flow from the Flows page, set the flow name, type, language, and optional keyword triggers, then open the flow editor and start building with a clean, readable layout.

Create a new flow in minutes

If you just need the fast path, follow this:

  1. Open the Flows page
  2. Click New Flow / Create Flow
  3. Set name, type, editing language, and optional keyword triggers
  4. Click Create to open the flow editor
  5. Keep a clean layout (mostly vertical-first)

You’re done. Your flow exists and you can now add nodes, test with the simulator, and connect triggers when ready.

Step-by-Step Process

1
Open the Flows page

  1. Log in to your RapidPro.app workspace.
  2. From the main navigation, click the Flows tab.

[CAPTURE: Workspace navigation with the “Flows” tab highlighted.]

2
Start a new flow

  1. On the Flows page, click Create Flow or New Flow (top-right corner, depending on your UI).
  2. The New Flow dialog opens.

[CAPTURE: Flows page showing the “New Flow” / “Create Flow” button at the top-right.]

3
Configure your flow settings

In the New Flow dialog, complete these fields:

  1. Flow name

    • Choose a clear name that reflects the goal, for example:
    • Registration – Collect Name
    • Clinic Reminder – Confirm Appointment
  2. Keyword triggers (optional)

    • If you want contacts to start the flow by texting a keyword, add one or more keywords here.
    • You can also add triggers later from the flow settings.
  3. Flow type

    • Select the type that matches your use case (for example, Messaging for SMS and social channels).
  4. Editing language

    • Choose the language you want to use in the flow editor (this is for building the flow, not necessarily the language contacts will receive).

[CAPTURE: New Flow dialog showing fields for name, keyword triggers, flow type, and editing language.]

💡
Tip: Use a naming convention that helps your team sort flows quickly, such as Program – Goal – Version (e.g., MOH – Registration – v1).

4
Create the flow and enter the flow editor

  1. Review your selections in the dialog.
  2. Click Create.
  3. RapidPro.app opens the flow editor, where you can start adding nodes.

[CAPTURE: Flow editor opened right after clicking “Create”, showing a blank or starting canvas.]

⚙️
Technical Detail: The flow editor is where you add nodes (actions and split actions), connect exits, and define the full conversation logic.

5
Keep your flow layout readable (vertical-first design)

As your flow grows, layout impacts readability and maintenance.

  1. Build with a vertical structure as your default.
  2. Use horizontal branching only when needed (for example, Yes/No splits).
  3. Keep related steps aligned so it’s easy to scan and debug.

[CAPTURE: Example flow layout showing mostly vertical structure with a small horizontal split.]

💡
Tip: The editor supports vertical growth indefinitely. If you build too wide horizontally, long flows become harder to navigate and review.

Common Issues & Quick Fixes

Problem: I don’t see the New Flow / Create Flow button.

Fix: Look in the top-right corner of the Flows page. Check your role (you may need Editor or Admin permissions). If you’re in the wrong workspace, switch to the correct one and try again.

Problem: My flow starts in the wrong language.

Fix: In the New Flow dialog, confirm the Language dropdown before clicking Create. If the flow is already created, create a new flow with the correct language (or update flow language settings if your environment allows changing it post-creation).

Problem: I created the flow but it doesn’t send messages.

Fix: Confirm your workspace has at least one connected channel. Test in the simulator to confirm the flow logic starts correctly. Make sure the flow is started via manual Start Flow or a trigger/campaign.