When CauseFlow investigates an incident, its agents need context about your services — architecture decisions, runbooks, past incidents, and related tickets. Project management integrations give agents access to this context automatically, without anyone needing to paste links manually.
During an investigation, agents search your connected project management tools for:
- Related tickets — open or recently closed issues linked to the affected service
- Architecture docs — Notion pages, Confluence spaces, or wiki entries describing the service
- Runbooks — step-by-step guides for known failure modes
- Deployment notes — release tickets or stories that describe recent changes
This context enriches the root cause analysis, especially for incidents where the code and infrastructure look healthy but a process or configuration change caused the issue.
The more context CauseFlow has about your services, the more accurate its investigations. Connect your project management tools to give agents access to architecture docs and runbooks.
Available integrations
| Tool | What CauseFlow accesses |
|---|
| Jira | Issues, epics, comments, and attachments for the affected service |
| Linear | Issues and cycles linked to the affected team or project |
| Notion | Pages in workspaces you authorize, searched by service name and incident keywords |
| Shortcut | Stories and epics linked to the affected component |
| Trello | Cards and board descriptions linked to the affected service |
Connecting via OAuth
All project management integrations use OAuth for authorization.
Open the catalog
Go to Dashboard > Integrations and find the tool you want to connect.
Click Connect
Click Connect to begin the OAuth flow.
Authorize in the tool
You’ll be redirected to the tool’s authorization page. Sign in and grant the requested permissions.
Return to CauseFlow
You’ll be redirected back. The integration will show as connected and agents will begin using it on the next investigation.
Security
OAuth tokens are stored in CauseFlow’s credential vault using KMS envelope encryption (AES-256-GCM). CauseFlow never stores tokens in plaintext, and access is scoped to read-only operations on the resources you authorized.
Access tokens are refreshed automatically using the OAuth refresh token flow. If a token expires or is revoked from the tool’s side, CauseFlow will show the integration as disconnected and pause context enrichment until you reconnect. 
