Integrations

Connect your AI agents and workflows to external systems, databases, and services.

Axellero Studio provides two directions of integration between your AI solutions and external systems: actions (your agents/workflows perform actions on external services) and events (external services push events into your agents/workflows). Both are configured in Studio at design time and used at runtime.

Overview

Integrations in Axellero follow this flow:

                                                            ┌─────────────┐    ┌──────────────┐
                                                            │  Connector  │    │   External   │
                                                       ┌───▶│  (Action)   │───▶│   Service    │
┌──────────────┐    ┌───────────┐    ┌──────────────┐  │    └─────────────┘    └──────────────┘
│   External   │    │  Trigger  │    │ AgentFlow /  │  │
│   Service    │───▶│  (Event)  │───▶│  Workflow    │──┤
└──────────────┘    └───────────┘    └──────────────┘  │    ┌─────────────┐    ┌──────────────┐
   Gmail             "New email"      Process &        └───▶│ MCP Server  │    │   External   │
   Telegram          "New message"    decide                │  (Action)   │───▶│   Service    │
   CRM               "Lead created"   AI logic              └─────────────┘    └──────────────┘

Connectors handle actions — your agents and workflows perform actions on external services: send data, execute operations, or query information
Triggers handle events — external services push events into your agents and workflows via webhooks
Credentials store the authentication that both connectors and triggers need
MCP Servers provide an additional way to perform actions on external services via the Model Context Protocol

Integration Components

Component	Type	Best For	Setup
Credentials	—	Store API keys, OAuth tokens, passwords	First step
Connectors	Actions	Databases, APIs, popular services	Minutes (requires Credential)
Triggers	Events	Real-time events, webhooks, push notifications	Minutes (requires Connector)
MCP Servers	Actions	Custom tools, legacy systems	Hours (standalone)

Actions vs Events

	Actions (Connectors)	Events (Triggers)
Flow	Your app → External service	External service → Your app
Initiated by	Agent or workflow action	External event (new message, status change, etc.)
Used in	Any node in AgentFlow or Workflow	Starting node of a Workflow or AgentFlow
Example	Send a Telegram message, create a Linear issue, query a database	New Telegram message received, Gmail email arrived, CRM lead created
Setup	Credential → Connector	Credential → Connector → Trigger

Getting Started

Create credentials — store authentication for your external services
Set up a connector — connect to a database or API
Configure triggers — receive real-time events from connected services
Explore MCP servers — add custom tools via the Model Context Protocol

Integration Use Cases

Scenario	Actions (Connectors)	Events (Triggers)
Customer Support	Send replies via Telegram/WhatsApp, create tickets in Linear	New message from customer, ticket status change
Data Processing	Read/write databases, call analytics APIs	Schedule-based data sync, webhook from data source
Business Automation	Update CRM records, send notifications via email	New lead created, deal stage changed
Content Management	Publish to CMS, upload to storage	New content submitted, approval status changed
E-commerce	Process payments, update inventory	New order placed, payment confirmed