> For the complete documentation index, see [llms.txt](https://flowmate.gitbook.io/flowmate-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flowmate.gitbook.io/flowmate-documentation/event-based-automation-guide/event-based-automation.md).

# Event-Based Automation

FlowMate processes these incoming events immediately and executes the corresponding Flows. This creates reactive, low-latency integrations that respond directly to changes in your application.

With Event-Based Automation, you can:

* Provide real-time integrations without relying on polling intervals
* Build Flows without a Connector, using your API as the data source
* Define custom events and payloads that match your system exactly
* Enable deeper and more flexible workflows, driven by your own business logic

## Understanding the FlowMate process

The FlowMate integration follows a structured process, from creating a flow to executing it with real data. Below is a high-level overview of how it works:

1. **User creates a flow**: A user creates a new flow in FlowMate using the Integration Center or Integration Portal. Each flow is assigned a unique ID, such as `1234`.
2. **Retrieving flows for active users:** As a FlowMate Partner, fetch all active flows via API to get the flow IDs.
3. **Match flows to users:** Link each active flow to the corresponding user in your system.
4. **Set up the webhook:** Configure a webhook to send data to the user’s flow.
5. **Trigger the flow:** When data is sent to the webhook URL, the flow executes with the provided payload.

<figure><img src="/files/QRkDxrd04C8xPKF6PDqv" alt=""><figcaption></figcaption></figure>
