> ## Documentation Index
> Fetch the complete documentation index at: https://fliqr.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Trigger a Flow

> Start a published Fliqr AI Flow from Automation Rules, menus, broadcasts, the inbox, drip campaigns, or the API.

A Flow does nothing until something starts it. Publish first, then attach one or more entry points.

## Entry points

| Entry point                  | Typical use                                          | Learn more                                                     |
| ---------------------------- | ---------------------------------------------------- | -------------------------------------------------------------- |
| **Automation Rules**         | Keywords, new contact, tag applied, button payloads  | [Automation Rules](/docs/core-concepts/automation-rules)            |
| **Default Reply**            | Fallback when nothing else matches                   | Automation Rules → Default Reply                               |
| **Channel menus / starters** | Persistent menu, conversation starters, ice breakers | Channel docs (Messenger, Instagram, …)                         |
| **Broadcasts**               | Send a published Flow to a segment                   | Channel broadcast guides                                       |
| **Drip campaign step**       | Timed nurture touches                                | [Drip campaigns](/docs/core-concepts/flows/drip-campaigns)          |
| **Inbox → Send Flow**        | Agent manually launches a script                     | Below                                                          |
| **API**                      | Your backend enrolls a contact in a Flow             | [Send Flow to user](/docs/api-reference/contacts/send-flow-to-user) |

## Send a Flow from the inbox

When a human is chatting and wants a scripted path:

1. Open the conversation in the inbox.
2. Click **Send Flow**.
3. Select a **published** Flow.
4. Send it to the contact.

Use this for common routines (collect address, share FAQ, start booking) without typing every step.

## Keyword → Flow pattern

1. Publish the Flow.
2. Create an Automation Rule with a **Keyword match** trigger.
3. Action: **Start a Flow** → select the Flow.
4. Place more specific keywords **above** broad rules. Leave Default Reply last.

## API and webhooks

* Use the contacts API to send/enroll a Flow when your system decides the moment.
* Listen for `flow_completed` on [Webhooks](/docs/integrations/webhooks) if your backend should continue after the script ends.

## Checklist before you attach a trigger

* Flow is published
* Happy path and fallback path tested
* Channel messaging windows / templates considered for outbound starts
* Contact fields the Flow expects are documented

## Next

<CardGroup cols={2}>
  <Card title="Automation Rules" icon="bolt" href="/docs/core-concepts/automation-rules">
    Full trigger and action reference.
  </Card>

  <Card title="Test and publish" icon="play" href="/docs/core-concepts/flows/test-and-publish">
    Make sure the Flow is live-ready.
  </Card>
</CardGroup>