Triggers

Triggers are the events side of integrations — they listen for real-time events from external services and start AgentFlows or Workflows automatically. When a subscribed event occurs — such as a new email, a chat message, or a CRM update — the trigger delivers the event data to your AgentFlow or Workflow.

Overview

Triggers are managed in Application > Integrations > Triggers. Each trigger is linked to a connector and subscribes to specific events from that service.

┌──────────────┐    ┌───────────┐    ┌──────────────┐
│   External   │    │  Trigger  │    │  AgentFlow / │
│   Service    │───▶│  (Event)  │───▶│   Workflow   │
└──────────────┘    └───────────┘    └──────────────┘
  Event occurs       Receives &        Processes
                     delivers event     event data

Trigger Lifecycle

Triggers follow a state-based lifecycle:

Prerequisites

Before creating a trigger, you need:

1. A credential for the external service — see Credentials Guide
2. A connector with trigger support — see Connectors Guide

Creating a Trigger

1. Navigate to Application > Integrations > Triggers
2. Click the "Create trigger" button
3. Select the Connector you want to receive events from
4. Enter a Code (unique identifier) and Name for the trigger
5. Optionally add a Description
6. Under Trigger options, select the events to listen for and optionally set a secret for webhook signature verification
7. Click Create

The available events depend on the selected connector type. For example, a Telegram connector offers events like Message, Edited Message, Channel Post, Callback Query, and more:

Configuration Fields

Subscribing and Unsubscribing

After creating a trigger, it starts in PENDING status. Click the subscribe icon in the trigger's row actions to activate it. Axellero will generate a unique webhook URL, register it with the external service (when supported), and begin listening for events. The status changes to SUBSCRIBED and a webhook URL becomes available.

You can also subscribe from the edit dialog by clicking the "Subscribe" button next to the status indicator.

For most services, Axellero handles webhook registration automatically. Some services (like Linear) require you to register the webhook URL manually — copy it from the Webhook URL column and paste it into the service's webhook settings.

Click the subscribe icon again to unsubscribe — this stops receiving events and deregisters the webhook. The status returns to PENDING.

Managing Triggers

Viewing Triggers

The Triggers tab displays a table with all triggers in the current application:

Each row has three action buttons: subscribe/unsubscribe, edit, and delete.

Editing a Trigger

1. Click the edit icon on the trigger row
2. Update the configuration options as needed
3. Click Update

The edit dialog also shows the current Status and a Subscribe/Unsubscribe button to manage the trigger lifecycle directly.

Deleting a Trigger

1. Click the delete icon on the trigger row
2. Confirm the deletion in the confirmation dialog

Using Triggers in AgentFlows and Workflows

Triggers serve as the starting node in an AgentFlow or Workflow. When an event is received, the trigger passes the event data to the execution context.

Adding a Trigger

1. Open AgentFlow Builder or Workflow Builder
2. Find your trigger in the Triggers section of the node palette
3. Drag the trigger onto the canvas as the starting node
4. Connect subsequent nodes to process the event data

Accessing Trigger Data

Trigger event data is available in the execution context:

{{ctx.nodes.<trigger_code>.outputs.data}}

For example, if your trigger code is telegram_trigger:

{{ctx.nodes.telegram_trigger.outputs.data.message.text}}

The data structure depends on the external service. See each service's setup guide for payload examples.

Troubleshooting

Related Guides

• Credentials — Set up authentication for external services
• Connectors — Connect to external services before creating triggers
• MCP Servers — Add custom tools via the Model Context Protocol