Integrations

Send Flamio's findings to Jira, GitHub or Trello, ask Flami and get digests in Slack, and query Flamio from AI tools over MCP.

Integrations connect Flamio to the tools your team already uses. Approved issues from reports become tasks on your board, Flami answers in Slack, and AI tools read your Flamio data over MCP.

What connects

Jira

Create approved issues as Jira issues in the project and issue type you pick.

GitHub Issues

Create approved issues in a GitHub repository, with default labels.

Trello

Create approved issues as cards on the board and list you pick.

Slack

Ask Flami in Slack and get project digests in a channel.

Claude, Cursor and Codex

Query your Flamio data from an AI tool over MCP.

How it works at a glance

Task trackers are connected per project. Each project picks its own Jira project, GitHub repository or Trello list. Connect them in Settings > Integrations, with the right project selected in the sidebar.
Slack is one connection for the whole organization. Each project then picks its own channel in its digest settings.
MCP uses tokens from Settings. A personal access token reaches every project; a per-project key reaches one.
Connecting, changing and removing integrations needs the Editor, Admin or Owner role.

Limitations

Flamio does not connect to analytics tools such as PostHog, Mixpanel, Amplitude or GA4 — nothing is sent to or pulled from them. Instead, to read Flamio's data from outside, create a token in Settings > API & MCP and query it over MCP.
Flamio does not connect to Linear, Asana, ClickUp, Notion, Azure DevOps, Monday or a generic webhook — the task trackers are exactly GitHub Issues, Trello and Jira, so approved issues export only to one of those three.
Flamio does not connect to self-hosted Jira (Server or Data Center) — instead, connect a Jira Cloud site (yourname.atlassian.net).
Flamio has no GitHub App and no sign-in with GitHub or Trello — instead, GitHub uses a fine-grained personal access token and Trello a Power-Up API key plus a token, both pasted into the connect dialog. Only Slack connects with a sign-in popup.
Flamio does not send a test issue to check a tracker connection — instead, Re-validate re-checks the stored credential, and exporting an approved issue from a report is the first real proof. Slack digests have their own Send now.
Flamio does not limit an MCP token to some projects or some tools, and tokens do not expire — a token reaches every project in your account and a per-project key reaches exactly one. Instead, use a per-project key for a tool that should see one project, and revoke a token to retire it.