New User Guide: The First 3 Essential Steps

You’ve created your RapidPro.app account—now it’s time to make it usable. The quickest path to success is: connect a messaging channel so you can actually send messages, then build a simple “registration” flow that asks for a contact’s name and stores it, and finally test everything in the simulator before trying it on real users. In this guide, you’ll learn how to add your first channel, build a basic registration flow (ask name → capture reply → save to contact → add to group → confirm), and validate the end-to-end experience using the simulator.

Go live with your first test flow (fast path)

If you just want the short version, follow this:

  1. Log in and confirm you can access your workspace
  2. Add your first channel (Workspace settings → Channels)
  3. Create a new Messaging flow from the Flows tab
  4. Add a Send Message node that asks for the contact’s name
  5. Add Wait for Response and store the result (e.g., Name)
  6. Use Update the Contact to save @results.name into a contact field
  7. Add the contact to a Completed Registration group
  8. Send a final confirmation message using @contact.first_name
  9. Test end-to-end using the simulator

Once that works in the simulator, you’re ready to build more complex flows.

Step-by-Step Process

1
Make sure you can access your workspace

  1. Open your browser and go to your RapidPro.app login URL.
  2. Log in with your email and password.
  3. Confirm you land on your workspace home (dashboard or main view).

[CAPTURE: Logged-in workspace home screen with the main navigation visible.]

💡
Tip: If you’re not sure how to sign up or log in, start with the account creation and login articles first.

2
Add your first channel

Your flows cannot send messages without at least one connected channel.

  1. In the left sidebar, click the Settings gear icon to open Workspace settings.
  2. Go to the Channels section.
  3. Click Add channel (or equivalent) and connect a channel such as:
    • SMS
    • WhatsApp
    • Another supported messaging channel
  4. Follow the on-screen instructions to complete setup.

[CAPTURE: Channels section showing a list of channels and an “Add channel” button.]

⚠️
Warning: If no channel is connected, flows will not send messages—even if they look correct in the editor.

💡
Tip: For first tests, use the simplest channel available in your deployment (for example, a test SMS connection or sandbox channel).

3
Create a new Messaging flow

  1. From your workspace, click the Flows tab in the top navigation.
  2. Review any sample flows (if provided).
  3. Click New Flow.
  4. In the New Flow dialog:
    • Enter a name, for example: Registration – Ask for Name.
    • (Optional) Add keyword triggers later if you want contacts to start via SMS/chat.
    • Choose Messaging as the flow type.
    • Confirm the Language for editing.
  5. Click Create to open the flow editor.

[CAPTURE: Flows tab with “New Flow” button highlighted + New Flow dialog showing name, type (Messaging), and language.]

💡
Tip: Use a clear name so it’s easy to find later (e.g., “Registration – v1”).

4
Ask the contact for their name

  1. In the flow editor, start from the first node (or create one if needed).
  2. Add a Send Message action.
  3. Write a simple prompt, for example: “Hi! What is your name?”
  4. Save the node.

[CAPTURE: Flow editor showing a Send Message node with “Hi! What is your name?” configured.]

💡
Tip: Keep the first message short and clear. You can refine tone and personalization later.

5
Wait for the contact’s response (and store it)

Now you need to capture whatever the contact replies.

  1. On the Send Message node, find the exit dot (often a small red dot).
  2. Click and drag the exit dot downward to create a new node.
  3. Select Wait for Response (or equivalent).
  4. In the Wait for Response settings:
    • Set the result name to something like Name.
    • Leave response rules open/blank to accept All Responses.

[CAPTURE: Flow editor showing the connection dragged from Send Message to create a Wait for Response node, with Result Name set to “Name”.]

⚙️
Technical Detail: If you leave the response rule blank, the flow accepts any input and stores it under a named result (e.g., @results.name).

6
Save the name in the contact’s profile

To reuse the contact’s name later, save it to a contact field.

  1. From the Wait for Response node, drag the exit dot downward to create another node.
  2. Change the node type to Update the Contact.
  3. In the Update the Contact configuration:
    • Choose the target contact field (e.g., Name or your workspace’s preferred field).
    • Set the value to the result variable, for example @results.name.
  4. Save the node.

[CAPTURE: Flow editor showing the new node changed to Update the Contact (green), saving @results.name into the Name field.]

💡
Tip: Use the @ autocomplete to quickly find results, contact fields, and system variables.

7
Add the contact to a “Completed Registration” group

Groups help you mark progress and segment contacts later.

  1. After the Update the Contact step, add an action to Add Contact to a Group.
  2. If your editor shows a blue + button on the node, use it to stack the next action. Otherwise, create a new node from the exit dot.
  3. Select an existing group like Completed Registration, or create one with that name.
  4. Save the action.

[CAPTURE: Update the Contact node with the blue + button used to add “Add Contact to a Group” immediately after, with “Completed Registration” selected.]

⚙️
Technical Detail: Groups make segmentation easier for broadcasts, campaigns, and reporting.

8
Send a confirmation message

  1. After adding to the group, create a final Send Message action.
  2. Personalize the message using a contact variable, for example:

“Thank you, @contact.first_name! Your registration is complete.”

  1. Save the node.
  2. Confirm your flow now does:
    • Ask name → capture reply → save to contact → add to group → confirm

[CAPTURE: Final Send Message node with a confirmation message using @contact.first_name.]

💡
Tip: Using @contact.first_name keeps confirmation messages short and friendly.

9
Test your flow with the simulator

  1. In the flow editor, locate the simulator panel (often on the right side).
  2. Start the flow in the simulator (using the simulator start control or Start Flow for the simulated contact).
  3. In the simulator:
    • Confirm the first message appears.
    • Type a test name as the response.
    • Follow the flow until you see the confirmation.
  4. Open the simulated contact details (if available) to verify:
    • The Name field is saved correctly.
    • The contact is in the Completed Registration group.

[CAPTURE: Flow editor with simulator panel open, showing the conversation and a completed run.]

⚠️
Warning: Always test in the simulator before starting flows for real contacts. Fixing mistakes is much easier before anything is sent in production.

Common Issues & Quick Fixes

Problem: My flow doesn’t send any messages.

Fix: Confirm at least one active channel exists in Workspace settings → Channels. Then ensure the flow is started (manually via Start Flow, or via a trigger/campaign). Use the simulator to validate logic.

Problem: The flow doesn’t save the contact’s name.

Fix: In Wait for Response, confirm the result name is set (e.g., “Name”). In Update the Contact, verify the field is correct and the value points to @results.name (matching your result key).

Problem: Contacts are not added to the “Completed Registration” group.

Fix: Confirm the selected group is correct (and spelled consistently), and that the flow path connects correctly from Update Contact to Add to Group (no missing/broken links). Re-test in the simulator.

Problem: I can’t see the simulator.

Fix: Confirm you are inside the flow editor (not just the Flows list). Look for a Simulator/Test panel on the right. On smaller screens it may be collapsed—try resizing or zooming out.

Problem: I’m not sure which flow type to use.

Fix: For SMS and chat channels (WhatsApp, Telegram, etc.), choose Messaging. It’s the default and best for your first end-to-end test.