Understanding Triggers: Roles and Types of Flow Initiation

Triggers define how and when a flow starts in RapidPro.app, letting you launch the right automation based on events such as a keyword message, an unmatched message, a scheduled date/time, a missed call, a new conversation, a Facebook referral, a ticket closing, or Facebook opt-in/opt-out events.

Create a trigger in a few steps

If you just need the essentials, follow this:

  1. Open the Triggers tab from the left sidebar
  2. Click + New Trigger and choose the trigger type
  3. Select the flow to start and configure options (including group filters when needed)
  4. For scheduled triggers, confirm your workspace timezone before testing
  5. Test with a real message/call (or a near-future schedule) and review logs

You’re done. Your trigger can now launch the right flow at the right time based on messages, calls, referrals, tickets, or schedules.

Step-by-Step Process

1
Open the Triggers section

  1. In your workspace, open the left sidebar.
  2. Click the Triggers tab.

[Left sidebar with “Triggers” highlighted.]

2
Create a new trigger and choose a type

  1. Click + New Trigger.
  2. Choose the trigger type that matches your use case.

[Triggers page showing the “+ New Trigger” button.]
[“New Trigger” modal/panel displaying available trigger types.]

Common trigger types include:

  • Keyword trigger: starts a flow when a contact sends a specific keyword.
  • Unmatched message trigger: starts a flow when a message does not match any existing keyword triggers.
  • Scheduled trigger: starts a flow in the future or on a recurring schedule.
  • Missed call trigger: starts a flow after receiving a call.
  • New conversation trigger: starts a flow when a contact initiates a new conversation.
  • Facebook referral trigger: starts a flow when Facebook refers a contact.
  • Ticket closed trigger: starts a flow after a support ticket is closed.
  • Facebook opt-in / opt-out triggers: starts a flow when a contact opts in or opts out of a topic.

[Trigger type dropdown/list showing Keyword, Unmatched Message, Schedule, Missed Call, New Conversation, etc.]

💡
Tip: If you’re new to triggers, start with a Keyword Trigger and test it in a sandbox workspace before adding schedules and filters.

3
Select the flow and configure trigger options

  1. Select the flow you want the trigger to start.
  2. Configure the trigger options based on the type you selected.
  3. If needed, add group inclusion/exclusion rules.
  4. Save the trigger.

[Trigger configuration screen showing Flow selection and Group include/exclude options.]

⚙️
Note: If you need different outcomes (for example, different flows for different keywords or channels), create separate triggers rather than trying to handle everything inside one trigger.

⚙️
Note: Group filters can block triggers. If inclusion/exclusion is enabled, contacts outside those groups won’t start the flow even if they send the correct keyword.

4
Confirm timezone for scheduled triggers

Scheduled triggers run according to your workspace’s configured timezone.

⚠️
Warning: If a scheduled trigger runs at an unexpected time, check Workspace Settings → Timezone before troubleshooting the trigger itself.

5
Test the trigger with real activity

  1. Send a real message (for keyword/unmatched triggers) or place a test call (for missed call triggers).
  2. For scheduled triggers, set a near-future run time for a quick test.
  3. Review logs to confirm the trigger fired and the flow started as expected.
💡
Tip: Testing with real traffic (or a near-future schedule) is the fastest way to verify your trigger configuration before going live.

Common Issues & Quick Fixes

Problem: The trigger fires, but the flow doesn’t start.

Fix: Confirm the trigger is enabled, verify it points to the correct flow, and review group inclusion/exclusion rules to ensure the contact is allowed to start the flow.

Problem: My keyword trigger doesn’t work.

Fix: Check the keyword spelling, look for conflicting keyword triggers, and confirm another trigger isn’t taking priority over the one you expected.

Problem: A scheduled trigger doesn’t run when expected.

Fix: Confirm your workspace timezone settings, then recheck the schedule’s date, time, and recurrence configuration.

Problem: An unmatched message trigger causes loops.

Fix: Ensure the flow routes contacts to a useful outcome and avoid logic that immediately puts contacts back into the same unmatched condition. Include a clear fallback path such as a menu, help flow, or human handoff.