ClickUp Integration
Create ClickUp tasks from TigerOps alerts with custom field mapping, status sync, and full incident context. Connect production monitoring to your ClickUp project management workflow.
How It Works
Generate a ClickUp API Token
In ClickUp, go to Settings > Apps > API Token and copy your personal API token. TigerOps uses this to create and update tasks in your ClickUp workspace.
Connect ClickUp in TigerOps
Paste your ClickUp API token into the TigerOps integration panel. TigerOps retrieves your workspaces, spaces, folders, lists, and custom fields for mapping.
Map Services to ClickUp Lists
Map each TigerOps monitored service to a ClickUp list and status. Configure custom field mappings for severity, service name, environment, and SLO impact.
Alerts Create and Update Tasks Automatically
Qualifying TigerOps incidents create ClickUp tasks with AI summary, priority, custom fields, and trace context. Task status syncs with incident lifecycle automatically.
What You Get Out of the Box
Custom Field Mapping
Map TigerOps incident attributes — severity, service name, environment, SLO burn rate, error rate — to any ClickUp custom field type: dropdown, text, number, or date.
Status Sync Across Lifecycle
ClickUp task status updates automatically with incident lifecycle: In Progress on detection, Under Investigation on AI analysis, Resolved on recovery.
Priority Mapping
TigerOps severity maps to ClickUp task priorities: critical → Urgent, warning → High, info → Normal. Priority is set automatically on task creation.
Rich Task Description
Task descriptions include the AI summary, impacted metric values, trace IDs with links, deployment correlation data, and a direct link to the TigerOps incident.
Assignee and Watcher Rules
Configure default assignees and watchers per ClickUp list or per TigerOps service tag. On-call engineers are automatically added as task watchers during active incidents.
Resolution and Comment Sync
Task status moves to the configured Done state when TigerOps resolves an incident. A resolution comment with incident duration and root cause is added automatically.
ClickUp Task Creation Config
Configure list mapping, custom field values, and status sync for ClickUp tasks.
# TigerOps — ClickUp Integration Config
integrations:
clickup:
api_token: "${CLICKUP_API_TOKEN}"
team_id: "${CLICKUP_TEAM_ID}"
min_severity: warning
auto_resolve: true
track_time: true
priority_mapping:
critical: 1 # Urgent
warning: 2 # High
info: 3 # Normal
service_mappings:
- tigerops_service: "api-gateway"
list_id: "${CLICKUP_LIST_PLATFORM}"
status_active: "In Progress"
status_done: "Resolved"
assignees: ["${CLICKUP_USER_PLATFORM}"]
tags: ["incident", "production"]
- tigerops_service: "payments-service"
list_id: "${CLICKUP_LIST_PAYMENTS}"
status_active: "Investigating"
status_done: "Closed"
custom_fields:
- field_id: "${CF_SEVERITY}"
value: "{{severity}}"
- field_id: "${CF_SERVICE}"
value: "{{service_name}}"
- field_id: "${CF_ENVIRONMENT}"
value: "{{environment}}"
- field_id: "${CF_SLO_BURN}"
value: "{{slo_burn_rate}}"
task_template:
name: "[{{severity}}] {{incident_title}}"
description: |
**Summary:** {{ai_summary}}
**Metric:** {{metric_name}} = {{metric_value}}
**Trace:** {{trace_url}}
**Dashboard:** {{tigerops_url}}Common Questions
Does TigerOps support ClickUp Workspace-level tokens or only personal API tokens?
TigerOps supports personal API tokens and ClickUp OAuth app tokens. For team setups, OAuth is recommended as it does not tie the integration to a single user's account. ClickUp workspace-level automation tokens are also supported when available.
Can I map the same ClickUp custom field to multiple TigerOps incident attributes?
Each ClickUp custom field maps to one TigerOps template variable. However, you can use template expressions to combine multiple values — for example, mapping a text custom field to "{{service_name}} — {{environment}}" to concatenate both values.
How does TigerOps handle incidents that fire in rapid succession for the same service?
TigerOps deduplicates alerts into a single incident per service per event window before creating ClickUp tasks. If multiple related alerts fire within a configurable dedup window, only one ClickUp task is created and additional alerts are added as task comments.
Can TigerOps create tasks in ClickUp Docs or only in task lists?
TigerOps creates tasks in ClickUp task lists via the Tasks API. ClickUp Docs are not supported for automated task creation. However, you can link a ClickUp Doc (such as a runbook) to the created task using a custom field in the integration config.
Does the integration support ClickUp time tracking for incident duration?
Yes. When time tracking is enabled in the integration config, TigerOps starts a time entry on the ClickUp task when the incident fires and stops it when the incident resolves, recording the exact incident duration in ClickUp's native time tracking feature.
Bring Production Incidents into ClickUp Automatically
No credit card required. Connect ClickUp in minutes. Custom field mapping immediately available.