Asana Integration
Create Asana tasks from TigerOps incidents with project and section mapping, smart assignee rules, and full incident context. Bridge production monitoring and engineering project management automatically.
How It Works
Generate an Asana Personal Access Token
In Asana, go to My Settings > Apps > Manage Developer Apps and create a personal access token. This token grants TigerOps read/write access to your Asana workspace.
Connect Asana in TigerOps
Paste your Asana PAT into the TigerOps integration panel. TigerOps retrieves your workspace, projects, and sections so you can configure mappings without leaving TigerOps.
Map Services to Asana Projects
Link each TigerOps service or alert policy to a target Asana project and section. Assign default assignees and due date offsets per severity level.
Incidents Create and Update Asana Tasks
When a TigerOps incident fires, an Asana task is created with title, description, AI summary, trace links, and the configured project/section/assignee. Resolution marks the task complete.
What You Get Out of the Box
Automatic Task Creation
TigerOps creates an Asana task the moment a qualifying incident fires — pre-filled with the AI summary, impacted service, severity, and a direct link to the TigerOps investigation.
Project and Section Routing
Route incident tasks to the correct Asana project and section based on service ownership, severity, or environment tag — critical issues to the "Urgent" section, warnings to "Backlog".
Assignee and Due Date Rules
Configure automatic assignee and due date rules per service and severity. Critical incidents are assigned to the on-call engineer with a due date of today; warnings get a 3-day window.
Trace Context in Task Description
Task descriptions include the AI-generated incident summary, relevant trace IDs with clickable links, impacted metric values, and a link to the TigerOps incident timeline.
Task Completion on Resolution
When TigerOps resolves an incident, the corresponding Asana task is automatically marked complete and a resolution comment is added with duration and root cause.
Custom Field Population
Populate Asana custom fields (severity, service name, SLO impact, environment) from TigerOps incident data, enabling Asana reporting and filtering by incident attributes.
Asana Task Creation Config
Map TigerOps services to Asana projects, sections, and configure field and assignee rules.
# TigerOps — Asana Integration Config
integrations:
asana:
access_token: "${ASANA_PAT}"
workspace_id: "${ASANA_WORKSPACE_ID}"
min_severity: warning
auto_complete: true
attach_metric_chart: true
service_mappings:
- tigerops_service: "api-gateway"
project_id: "${ASANA_PROJECT_PLATFORM}"
section_id: "${ASANA_SECTION_URGENT}"
default_assignee_gid: "${ASANA_USER_PLATFORM_LEAD}"
due_date_offset_days: 0
- tigerops_service: "payments-service"
project_id: "${ASANA_PROJECT_PAYMENTS}"
section_id: "${ASANA_SECTION_BACKLOG}"
default_assignee_gid: "${ASANA_USER_PAYMENTS_LEAD}"
due_date_offset_days: 1
task_template:
name: "[{{severity}}] {{incident_title}}"
notes: |
**AI Summary:** {{ai_summary}}
**Service:** {{service_name}} | **Severity:** {{severity}}
**Metric:** {{metric_name}} = {{metric_value}}
**Trace:** {{trace_url}}
**TigerOps:** {{tigerops_url}}
custom_fields:
severity_field_gid: "{{severity}}"
service_field_gid: "{{service_name}}"
environment_field_gid: "{{environment}}"Common Questions
Does TigerOps support Asana OAuth or only personal access tokens?
TigerOps supports both personal access tokens and OAuth 2.0. The OAuth flow allows team members to authorize TigerOps using their own Asana account without sharing tokens, and is recommended for production team setups.
Can TigerOps create tasks in multiple Asana projects for the same incident?
Yes. An alert policy can have multiple Asana targets — for example, creating a task in both the Platform Engineering project and the Customer Escalations project when a critical payment service incident fires.
What happens to the Asana task if TigerOps fires multiple incidents for the same service?
TigerOps checks for an open Asana task with a matching TigerOps incident ID in the custom field before creating a new one. Repeat incidents add a comment to the existing task instead of creating duplicates.
Can I attach TigerOps metric charts to the Asana task?
Yes. When metric chart attachments are enabled, TigerOps generates a PNG snapshot of the anomalous metric chart and attaches it to the Asana task, giving engineers a visual reference without opening TigerOps.
Does the integration work with Asana Business and Enterprise plans only?
The core integration works with all Asana plans. Custom fields population requires Asana Business or Enterprise, as custom fields are a paid-tier feature. All other task creation, assignment, and completion features work on the free and Premium tiers.
Bridge Production Incidents and Asana Automatically
No credit card required. Connect Asana in minutes. Tasks created with full context immediately.