Main Agent Integrations
Connectors let external systems spawn and update agent tasks automatically. Each connector is configured at the workspace level and inherits the workspace's brand context.
Jira
Connect a Jira workspace to let the agent react to ticket activity.
Capabilities
| Capability | Description |
|---|---|
| @mention bot | When the bot is @mentioned in a Jira ticket comment, a Main Agent task is spawned automatically |
| Project routing | Tickets are deterministically routed to a XainFlow project based on Jira project key |
| Ticket sessions | Each Jira ticket gets a tracked session — replies and updates flow back into the agent's task |
| Ticket splits | The agent can break a parent ticket into subtasks. Default is build-only (subtasks are linked but the parent is not duplicated) |
| ADF comments | Replies are posted in Atlassian Document Format so they render natively in Jira |
| Strict triggers | Only configured trigger phrases (or @mentions) start a task — avoids accidental spawns |
Setup
- Go to Workspace Settings > Integrations > Jira.
- Authorize the Jira workspace.
- Configure project routing: map each Jira project key to a XainFlow project.
- Save. The Jira bot is now active across all configured projects.
Monday.com
Monday.com works similarly to the Jira connector, but on items and subitems within a board.
Capabilities
| Capability | Description |
|---|---|
| @mention in items and subitems | Mentioning the bot spawns a Main Agent task tied to the Monday item |
| Board-aware badges | Tasks display as <BoardAbbrev>-<LastDigits> (e.g., BF-2949 for a Black Friday board item ending in 2949) |
| Schema-aware updates | Column updates respect each column's type — status, dropdown, date, person, etc. |
| Subitem-aware | Subitem events fire against the parent board so context is preserved |
| Webhook auto-registration | A token-protected webhook is registered per board automatically when you connect |
Available Tools
The Main Agent uses these tools when reacting to Monday events. They are also available via MCP — see MCP Server — Monday.com.
| Tool | Description |
|---|---|
monday_list_boards | List boards in the connected workspace |
monday_get_board | Get board metadata and groups |
monday_get_board_columns | Get column schema for a board |
monday_get_item | Get an item with its column values |
monday_create_update | Post an update (comment) to an item |
monday_update_column_values | Set column values on an item |
monday_create_subitem | Create a subitem under a parent item |
monday_move_item_to_group | Move an item between groups |
Setup
- Go to Workspace Settings > Integrations > Monday.com.
- Authorize the Monday workspace.
- Select the boards you want to connect. Webhooks register automatically for each.
- Save. @mention the bot in any item or subitem to spawn a task.
Google Drive
Drive integration gives the agent a place to read input files and write generated outputs.
Capabilities
- OAuth folder picker — choose a default folder when connecting; the picker also appears whenever you change the destination on a task.
- Default upload folder — generated assets are saved here unless overridden.
- Subfolder rules — when uploading 2+ files at once, the agent honors per-asset subfolder hints.
Setup
- Go to Workspace Settings > Integrations > Google Drive.
- Authorize the Drive account.
- Pick the default folder using the OAuth picker.
- Save.
Email Broadcast
For admin and marketing use cases, the Main Agent can send broadcast emails through the workspace's configured provider (Resend). Use it for announcements, drip campaigns, or templated newsletters generated by the agent.
Email broadcast requires Owner or Admin permissions and is rate-limited per workspace. Contact support to enable bulk sending limits.
Related Pages
- Skills — recipes the agent runs across these connectors
- Scheduled Tasks — combine connectors with cron triggers
- MCP Server Overview — call the same tools from your IDE