Shortcut Integration
Push TigerOps incidents to Shortcut stories with priority, labels, team assignment, and trace context. Keep your engineering sprint synchronized with what is actually happening in production.
How It Works
Generate a Shortcut API Token
In Shortcut, go to Settings > API Tokens and create a new token. The token grants TigerOps write access to create and update stories in your workspace.
Connect Shortcut in TigerOps
Enter your Shortcut API token in the TigerOps integration panel. TigerOps automatically retrieves your workspaces, projects, teams, and workflows for mapping.
Configure Story Mapping Rules
Map TigerOps services and severity levels to Shortcut projects, teams, workflow states, and labels. Define priority mapping between TigerOps severity and Shortcut story priority.
Incidents Become Shortcut Stories
On qualifying incidents, TigerOps creates a Shortcut story with the AI summary, trace context, labels, team, and priority all pre-filled. Resolution marks the story done.
What You Get Out of the Box
Automatic Story Creation
TigerOps creates a Shortcut story automatically when an incident fires, with severity-based priority, labels, team assignment, and AI-generated description already populated.
Priority and Label Mapping
Map TigerOps severity levels to Shortcut story priorities (p0–p3) and apply labels like "incident", "production", and service-specific labels automatically.
Team and Owner Assignment
Route stories to the correct Shortcut team and assign an owner based on TigerOps service ownership configuration. No manual routing or story triage needed.
Trace and Metric Context
Story descriptions contain the AI summary, impacted metric values, relevant trace deep links, and a link to the TigerOps incident for complete investigation context.
Story Completion on Resolution
When TigerOps resolves an incident, the Shortcut story is moved to the configured "Done" workflow state and a resolution comment is added with duration and root cause.
Epic Linking
Optionally link all incident stories for a service to a recurring "Reliability" epic in Shortcut, giving engineering leadership a consolidated view of production issues.
Shortcut Story Mapping Config
Map TigerOps services to Shortcut projects, teams, and workflow states.
# TigerOps — Shortcut Integration Config
integrations:
shortcut:
api_token: "${SHORTCUT_API_TOKEN}"
min_severity: warning
auto_complete: true
dedup_window_minutes: 60
priority_mapping:
critical: 0 # p0
warning: 2 # p2
info: 3 # p3
service_mappings:
- tigerops_service: "api-gateway"
project_id: "${SHORTCUT_PROJECT_PLATFORM}"
team_id: "${SHORTCUT_TEAM_PLATFORM}"
workflow_state_id: "${SHORTCUT_STATE_IN_PROGRESS}"
done_state_id: "${SHORTCUT_STATE_DONE}"
labels: ["incident", "production", "platform"]
epic_id: "${SHORTCUT_EPIC_RELIABILITY}"
- tigerops_service: "payments-service"
project_id: "${SHORTCUT_PROJECT_PAYMENTS}"
team_id: "${SHORTCUT_TEAM_PAYMENTS}"
labels: ["incident", "production", "payments"]
story_template:
name: "[{{severity}}] {{incident_title}}"
description: |
## Incident Summary
{{ai_summary}}
**Service:** {{service_name}} | **Severity:** {{severity}}
**Metric:** {{metric_name}} = {{metric_value}}
**Trace:** {{trace_url}}
**TigerOps:** {{tigerops_url}}Common Questions
Can TigerOps create Shortcut stories in multiple workflows?
Yes. Each TigerOps service mapping can target a different Shortcut project and workflow. Different services can use different workflows — for example, infrastructure incidents go to the "Ops" workflow and app errors go to the "Engineering" workflow.
How does TigerOps map story priority to Shortcut's priority levels?
TigerOps maps its severity levels (critical, warning, info) to Shortcut priority values (p0 through p3). The default mapping is critical → p0, warning → p2, info → p3. You can override this mapping in the integration configuration.
Will the integration create duplicate stories for recurring incidents on the same service?
TigerOps checks for an open Shortcut story with a matching TigerOps incident ID in the story description before creating a new one. Subsequent incidents on the same service within a configurable dedup window add comments to the existing story.
Can I link TigerOps stories to an existing Shortcut epic?
Yes. In the TigerOps service mapping config, you can specify an epic ID to link all created stories to. You can also create a new epic per major incident from the TigerOps incident panel using the Shortcut integration action.
Does TigerOps support Shortcut's Iterations for sprint planning of incident follow-ups?
TigerOps can assign created stories to the current active Shortcut iteration when enabled. This is useful for ensuring incident follow-up tasks automatically appear in the active sprint without manual iteration assignment.
Sync Production Incidents with Your Shortcut Workflow
No credit card required. Connect Shortcut in minutes. Stories created with full context immediately.