Skip to content
Integrations

Every door opens onto the same records

The app, the Falrow Slack bot, Sentry, your notetakers, your agents and the REST API share one database, one set of roles and one set of workflow rules. Nothing syncs, so nothing drifts.

Integrations

Every door opens onto the same records

The app, your agents, Slack, Sentry, your notetakers and the API do not sync copies of each other. They read and write one database, under one set of roles and version checks, so there is nothing to drift.

135 tools

MCP for Claude Code, Codex and more

A Streamable HTTP MCP server with OAuth 2.1 sign-in, a workspace resource, and prompts for a daily update and for planning open tickets. Plus an agent package with a development workflow skill.

plan_contextsearch_issuesbulk_update_issuesconvert_meeting_actionsdevelopment_reportrollover_cycle
Bot · threads

Falrow in Slack

Mention @Falrow or use /falrow to create, find, take and move tickets. Each ticket gets a thread that tags whoever asked, and progress is posted there.

@Falrow the export button 500s on staging@Falrow take NOR-231/falrow search invoice/falrow update FAL-409 In review

Meeting notetakers

Granola, Fathom, Fireflies or tl;dv with your own API key, stored encrypted. Preview privately, import once, turn actions into tickets.

How meetings work

REST API

Authenticated /api/v1 for projects, tickets, cycles, milestones, customers, notes, documents, saved views and reports, plus search, bulk edits, transitions, rollover and meeting conversion. The same service layer as the app and MCP.

PATCH /api/v1/issues/{id}
{ "priority": "High", "version": 7 }

Sentry

Route each Sentry project and environment to an application. Errors above your minimum level become one bug ticket per Sentry issue, owned by your type rules.

How routing works
Not yet

GitHub & importers

Applications record their repository so agents find the right plan, but pull request sync and backlog importers are not built yet. Tell us if you need them.

Falrow in Slack

Ask in the channel, get the answer in the same thread

Mention @Falrow or send it a direct message in plain words: create a ticket, find one, take it, move it, comment or nudge the owner. It acts as your linked account, so your role applies. Every ticket gets one thread that tags whoever raised it and whoever owns it, and assignment, status, priority and comments are posted there as they happen.

  • Channels map to projects; one Slack team can serve several workspaces
  • Agents post progress and ask questions in the ticket's thread
  • Slack people are matched by email, and an admin confirms every link
#nordlys-app · threadone thread per ticket
MH@Falrow the booking form drops the Arabic name field on submitM. Haddad · #nordlys-app
Created NOR-231 · Bug · owner R. Nakamura (type rule). I'll post progress here.Falrow · thread root
NOR-231 → In progress. Claude Code: plan attached, fix touches the form encoder.Falrow · status update
@M. Haddad does the field also drop on the mobile app?Falrow · ask_ticket_member
NOR-231 → In review. @M. Haddad @R. NakamuraFalrow · status update
/falrow

Work the tickets from the channel

The /falrow command creates, lists, searches, updates, snoozes and triages the mapped project's tickets, in 20-row pages with exact totals.

  • Opt-in project updates posted to mapped channels
  • Signed requests, and retries that never repeat an update
  • Failed or uncertain posts wait for an admin, never blindly resent
#nordlys-appmapped to Nordlys booking app
/falrow create Fix the login redirect/falrow list [page]/falrow search [--page N] text/falrow statuses /falrow status FAL-1/falrow update FAL-1 In progress/falrow duplicate FAL-2 FAL-1 reason/falrow triage ready | snoozed | all/falrow snooze FAL-1 time reason/falrow unsnooze FAL-1 reason
K. Osei moved NOR-218: Add Arabic to the booking flow · In review
Sentry

Production errors arrive as bug tickets

Connect one or more Sentry organizations to a workspace, so a website, an app and a CRM can each keep their own account. Route each Sentry project and environment to an application, with a minimum level. Project type rules pick the owner and stage, exactly as they would for a ticket someone typed.

  • At most one ticket per Sentry issue
  • Unrouted and filtered events are recorded, not silently dropped
  • Write-back to Sentry is opt-in and never blocks a ticket
Sentry · acme-agencyone ticket per Sentry issue
client-portal-web · production→ Client portal · Bug · min level errorticket
client-portal-web · staging→ Listed, no ticketlisted
booking-api · any→ Nordlys booking app · Bugticket
marketing-site · production→ No routeunrouted

The same Sentry issue never opens a second ticket. Write-back to Sentry is opt-in per connection.

Meeting notetakers

Meeting notes in, reviewed tickets out

Connect Granola, Fathom, Fireflies or tl;dv with your own API key, preview privately, edit and import. Then choose which action items become tickets linked to the meeting and the customer, or link them to tickets that already exist.

  • Imports each meeting once
  • Keys stored encrypted, previews only you can see
  • File upload and paste work without any of them
Meetings · sourceseach meeting imports once
GranolaYour own API key · private preview
FathomYour own API key · private preview
FirefliesYour own API key · private preview
tl;dvYour own API key · private preview
File or pasteAny notetaker's export, up to 200 KB
MCP

Claude Code, Codex and any MCP client

A Streamable HTTP MCP server with OAuth 2.1 discovery, dynamic client registration, PKCE, consent and revocation, plus workspace tokens for scripts. Every connection is listed and revocable.

  • 135 tools, a workspace resource and three prompts
  • Agent package for Claude Code and Codex
  • Read-only endpoint checker
Integrations · agent connectionsDigital Horizon
Claude CodeOAuth · write · 2 min agoRevoke
CodexOAuth · read · yesterdayRevoke
CI scriptToken · write · expires in 83 daysRevoke

Connect the tools you already use

Request access. We set up Slack, Sentry, your notetaker and your agents with you.