Keyword Trigger: Using the First Word of a Message to Launch a Flow

A keyword trigger starts a flow automatically when the first word of an incoming message matches one or more keywords you define (for example, starting a registration flow when a contact sends “JOIN”), with options to control matching behavior and optionally restrict the trigger by channel and/or contact groups.

Create a keyword trigger in a few steps

If you just need the essentials, follow this:

  1. Open Triggers and click + New Trigger
  2. Select Create message keyword that launches a Flow
  3. Add your keyword(s) and choose how matching should work
  4. Select the flow to start and optionally restrict by channel and groups
  5. Save, confirm it’s active, and test with a real message

You’re done. The flow will start automatically when an incoming message matches your keyword rules.

Step-by-Step Process

1
Start a new trigger

  1. Go to the Triggers tab.
  2. Click + New Trigger.

[CAPTURE: Triggers page showing “+ New Trigger”.]

2
Choose the keyword trigger type

  1. Select Create message keyword that launches a Flow.

[CAPTURE: New Trigger options with “Create message keyword that launches a Flow” highlighted.]

3
Enter keywords and define matching behavior

  1. Enter one or more keywords in the keyword field (you can also add common misspellings).
  2. Choose whether the trigger should fire when the message starts with the keyword or contains only the keyword.

[CAPTURE: Keyword input field with multiple keywords added.]
[CAPTURE: Trigger options showing “starts with” vs “contains only”.]

⚙️
Note: Keywords are evaluated based on the first word of the incoming message.

💡
Tip: If contacts might write “JOIN yes” or “PROMO please”, starts with is usually more forgiving than contains only.

💡
Tip: Include common misspellings (for example, prmo) so contacts still reach the right flow.

4
Select the flow and optional restrictions

  1. Select the flow to start when the keyword matches.
  2. Optional: Restrict the trigger to a specific channel, or leave it blank to allow any channel in the workspace.
  3. Optional: Add include/exclude group rules to control who can trigger the flow.

[CAPTURE: Flow dropdown showing a selected flow.]
[CAPTURE: Optional Channel dropdown (showing “None” vs a selected channel).]
[CAPTURE: Group include/exclude selector with sample groups chosen.]

⚙️
Note: Channel restrictions are useful in multi-channel workspaces so a keyword intended for one channel (for example, Telegram) doesn’t also trigger via another (for example, SMS).

⚠️
Warning: Group filters can block expected behavior. If a contact isn’t in an included group (or is in an excluded group), the keyword won’t start the flow—even if the keyword is correct.

5
Save, confirm it’s active, and test

  1. Save the trigger.
  2. Confirm the trigger appears in your list of active triggers.
  3. Send a real message using the keyword to verify the flow starts, and review logs if it doesn’t.

[CAPTURE: Triggers list showing the newly created keyword trigger.]

💡
Tip: Always test once after saving to confirm the trigger fires and starts the expected flow.

6
Example configuration

Example: Start the “Coupon Group” flow when members of “New Registrations” (but not “Completed Registration”) send a message starting with
promo, promotion, or prmo, and only when messaging via a specific Telegram channel.

[CAPTURE: Completed trigger configuration showing keywords + channel + include/exclude groups.]

Common Issues & Quick Fixes

Problem: The keyword doesn’t start the flow.

Fix: Check spelling and spacing (the keyword must be the first word), confirm the trigger is enabled, verify group include/exclude rules, and if the trigger is channel-restricted, confirm the message arrived on the selected channel.

Problem: The keyword starts the wrong flow.

Fix: Look for overlapping keywords across triggers, then simplify keywords or separate triggers by channel or group to avoid collisions.

Problem: Some contacts trigger it and others don’t.

Fix: Review group inclusion/exclusion rules and confirm contacts are using the correct channel when a channel restriction is set.