Integrations — Connect External Services

Integrations connect FleetQ to external services via OAuth2. Once connected, agents and workflows can interact with these services through their APIs — creating issues, sending messages, querying repositories, and more. Integrations also power inbound Signal connectors for GitHub, Linear, and Jira.

Scenario: An engineering team connects their GitHub and Linear accounts. A workflow agent automatically creates a Linear issue when a GitHub PR is merged without a linked ticket, then posts a Slack summary to the engineering channel.

Available integrations

Activepieces — 660+ integrations at once

Activepieces is an open-source automation platform. Each "piece" it ships with is natively exposed as an MCP server endpoint. FleetQ's Activepieces connector lets any team that runs an Activepieces instance auto-import all of them as mcp_http Tool records — zero per-connector maintenance, maximum integration surface.

• Hourly sync job discovers new pieces and updates existing ones.
• Piece filter — restrict which pieces are imported (e.g. only stripe, slack, notion).
• SSRF guard — the Activepieces URL is validated on every sync and API call.
• Manual trigger — run integration_manage({action: "activepieces_sync"}) to refresh on demand.

Connecting an integration

All integrations use the standard OAuth2 authorization code flow. Tokens are stored encrypted at rest using your team's per-team key.

1. 1 Go to Integrations in the sidebar.
2. 2 Click Connect next to the provider you want to add.
3. 3 Authorize FleetQ in the provider's OAuth screen and grant the requested scopes.
4. 4 You are redirected back to FleetQ. The integration status changes to Connected.

Using integrations in agents and workflows

Once connected, an integration exposes a set of named capabilities — discrete actions the connected account can perform. Agents and workflow nodes can invoke these capabilities without handling OAuth tokens directly.

Use the integration_capabilities MCP tool to list all available actions for a connected integration, then use integration_execute to run an action against the live service.

// integration_capabilities({ integration_id: "..." })
{
  "capabilities": [
    { "action": "create_issue",    "description": "Create a new issue in a repository" },
    { "action": "list_issues",     "description": "List issues with filters" },
    { "action": "create_pr",       "description": "Open a pull request" },
    { "action": "list_repos",      "description": "List accessible repositories" },
    { "action": "merge_pr",        "description": "Merge a pull request" }
  ]
}

// integration_execute({ integration_id: "...", action: "create_issue", params: { ... } })
{
  "result": {
    "id": 42,
    "url": "https://github.com/acme/api/issues/42",
    "title": "Automated: missing Linear ticket for PR #118"
  }
}

Integration status and health

Ping an integration at any time to verify that the stored token is still valid and the remote service is reachable. If a token expires or is revoked at the provider, FleetQ marks the integration as disconnected and stops routing agent actions through it.

# Via API
curl -X POST https://your-fleet.example.com/api/v1/integrations/{id}/ping \
  -H "Authorization: Bearer YOUR_TOKEN"

Signal connectors

Integrations also power inbound Signal connectors. Once you have connected GitHub, Linear, or Jira, you can create per-repository or per-team subscriptions that automatically ingest events as Signals — issues created, PRs opened, comments added, and more.

Signal connector setup is covered in the Signals documentation. The short version: connect the integration first here, then configure subscriptions under Signal Sources → Subscriptions.

MCP tools

The following MCP tools are available for integration management. Use them via the MCP server or the AI Assistant.

API endpoints

All integration endpoints are under /api/v1/integrations and require a Sanctum bearer token. Full OpenAPI 3.1 docs are available at /docs/api.