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

# Manage Triggers

> Monitor and control event-based triggers that automatically start process instances. Manage Triggers provides a centralized interface to view, activate, and deactivate triggers configured in your project builds.

## Overview

The **Manage Triggers** feature provides a centralized interface for monitoring and controlling event-based triggers that automatically start process instances. Triggers connect external events (such as email arrivals, message events, or other data sources) to your process definitions, enabling event-driven automation.

> [card] Trigger Types
>
> Supported trigger types:
>
> * **Email Trigger** (IMAP): Start processes when emails arrive via [Email Trigger](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/email-trigger.md) data sources
> * **Microsoft Outlook** (MS Graph): Start processes when emails arrive via [Microsoft Outlook](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/microsoft-outlook-data-source.md) data sources. These rows show the trigger type **Email Trigger**.
> * **Webhook**: Start or resume processes when an external system calls an [Incoming Webhook](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/incoming-webhooks.md)

![Manage Triggers Interface](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.x/emt.png)

## Accessing manage triggers

Navigate to **Runtime** → **Runtime Settings** → **Manage Triggers** in your project to access the triggers management interface.

> [!NOTE]
>
> You must have appropriate runtime permissions to view and manage triggers. See [Workspace runtime editor](https://docs.flowx.ai/6.x/setup-guides/access-management/workspaces-access-rights.md#workspace-runtime-editor) for details.

## Trigger list

The **Manage Triggers** interface displays all triggers configured in your active build. Each trigger appears as a row in the table with the following information:

| Column | Description |
| - | - |
| **State** | Current status: `Active` (monitoring enabled) or `Deactivated` (monitoring paused) |
| **Trigger Type** | The type of trigger: `Email Trigger` (IMAP and Microsoft Outlook data sources) or `Webhook` |
| **Event Name** | The name of the trigger data source or event configuration |
| **Location** | `Local` when the trigger is defined in this project, or the name of the library project the trigger comes from |
| **Used in** | How many resources subscribe to the trigger, as a count such as `2 resources`, with a breakdown by processes and workflows on hover. A trigger nothing uses shows `0 resources`, and its hover reads `Not used by any resource`. |

![The Manage Triggers list showing webhook triggers with their state, type, event name, location, and the Used in column reporting how many resources subscribe to each](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/manage-triggers-used-in.png)

### Empty state

When no triggers are configured for your project, the interface displays an empty state message: **"There are no triggers on this project yet."**

Triggers appear in this list once:

1. ✅ A trigger data source is created (for example, Email Trigger in Integration Designer)
2. ✅ The trigger is linked to a Message Start Event node in a process definition (Email Trigger or Incoming Webhook), to a Message Catch Intermediate Event that waits for an Incoming Webhook, or to the Start node of an [integration workflow](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/integration-designer.md#external-triggers) 
3. ✅ The process is included in a build that is part of the **Active Policy**

## Activating and deactivating triggers

You can control trigger monitoring directly from the **Manage Triggers** interface:

**1. View triggers**

Navigate to **Runtime** → **Runtime Settings** → **Manage Triggers** to see all available triggers for your active build.

**2. Change the trigger state**

Open the row menu (**⋮**) on the trigger and select **Activate** or **Deactivate**, then confirm. The **State** column updates to:

* **Active**: The system monitors for events and creates process instances automatically
* **Deactivated**: Monitoring is paused; no new process instances are created from this trigger

For webhook triggers, the same menu also has **Get URL**, which shows the webhook endpoint to give to the calling system.

![Manage Triggers Interface](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.x/emt1.png)

> [!WARNING]
>
> When you change the **Active Policy** (switch to a different build), triggers retain their previous activation state. If a trigger is removed from the new active build, it will be automatically deactivated.

## Trigger activation requirements

For a trigger to appear in **Manage Triggers**, it must meet all of the following requirements:

1. **Trigger data source exists**: The trigger must be configured as a data source (for example, Email Trigger in Integration Designer)
2. **Linked to process**: The trigger must be connected to a Message Start Event node in a process definition (Email Trigger or Incoming Webhook), to a Message Catch Intermediate Event that waits for an Incoming Webhook, or to the Start node of an [integration workflow](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/integration-designer.md#external-triggers)
3. **In active build**: The process containing the trigger must be part of a build that is set as the **Active Policy**

> [!NOTE]
>
> Triggers are read-only in the Runtime view. To modify trigger configurations (for example, change email server settings, update filters), you must edit the data source in Integration Designer and create a new build.

## Use cases

> [card] Email-based automation
>
> Automatically start customer support processes when emails arrive in monitored mailboxes. Email Triggers enable event-driven workflows for support ticket creation, document processing, and request handling.

> [card] Event-driven processes
>
> Connect external systems to FlowX processes through event triggers. When external events occur (emails, messages, API calls), processes start automatically without manual intervention.

> [card] Production control
>
> Pause or resume trigger monitoring in production environments without redeploying builds. This is especially useful for maintenance windows or when troubleshooting issues.

> [card] Multi-environment management
>
> Manage trigger states independently across different environments (dev, staging, production) while using the same build configuration.

## Monitoring trigger activity

### Failed triggers

When triggers fail to process events (for example, email validation errors, connection issues), they appear in the **Failed Triggers** section.

Navigate to **Runtime** → **Processes** → **Failed Triggers** to view:

* Timestamp of the failure
* Trigger type and name
* Cause type (for example, "File type not permitted," "File size exceeded")
* Context information (for example, sender email, file details)

> [card] [Handling failed triggers](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/email-trigger.md#handling-failed-triggers)
>
> See the Email Trigger documentation for the failure causes, the details view, and how to resolve failed email triggers.

## Best practices

> [card] Test before activation
>
> Always test triggers in development environments before activating them in production. Verify that process instances start correctly and handle edge cases.

> [card] Monitor failed triggers
>
> Regularly check the Failed Triggers section to identify and resolve issues. Common causes include file size limits, connection problems, and validation errors.

> [card] Use descriptive names
>
> Give triggers descriptive names in Integration Designer to make them easily identifiable in the Manage Triggers list.

> [card] Document trigger behavior
>
> Document which processes are triggered by each trigger and under what conditions. This helps with troubleshooting and maintenance.

## Related resources

> [card] [Email Trigger](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/email-trigger.md)
>
> Learn how to configure Email Triggers in Integration Designer and connect them to Message Start Events.

> [card] [Message Start Events](https://docs.flowx.ai/6.x/docs/building-blocks/node/message-events/message-catch-start-event.md)
>
> Understand how Message Start Events work and how to configure them in process definitions.

> [card] [Active Policy](https://docs.flowx.ai/6.x/docs/projects/runtime/active-policy.md)
>
> Learn how to set the Active Policy to control which build's triggers are available for management.

> [card] [Failed Process Start](https://docs.flowx.ai/6.x/docs/projects/runtime/active-process/failed-process-start.md)
>
> View and debug exceptions raised when a process instance fails to start.

> [card] [Incoming Webhooks](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/incoming-webhooks.md)
>
> Configure Incoming Webhook data sources that start or resume processes, and find the webhook URL to share with callers.


## Related topics

- [Microsoft Outlook](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/microsoft-outlook-data-source.md)
- [Email Trigger](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/email-trigger.md)
- [FlowX.AI 5.9.0 Release Notes](https://docs.flowx.ai/release-notes/v5.x/v5.9.0-june-2026/v5.9.0-june-2026.md)
- [Message Start Event](https://docs.flowx.ai/6.x/docs/building-blocks/node/message-events/message-catch-start-event.md)
- [Incoming Webhooks](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/incoming-webhooks.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.