+
Connect Linear to Pagerduty
Automate Linear and Pagerduty with AI
PagerDuty pages should spawn Linear issues with service context before on call finishes triage. Operator.io runs OpenClaw on PagerDuty and Linear so an incident opens or links a Linear issue with severity and runbook notes filled, Linear completion can resolve the linked PagerDuty incident when the fix ships, and chat lists open pages with their Linear ticket keys. Tell it to summarize the overnight pages and it reads PagerDuty and updates Linear.
It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.
What your agent can do with Linear and Pagerduty
What your agent does in Linear
Create attachment
Creates a new attachment and associates it with a specific, existing Linear issue.
Add reaction to comment
Tool to add a reaction to an existing Linear comment. Use when you want to programmatically react to a comment on an issue.
Create a comment
Creates a new comment on a specified Linear issue. This action modifies shared workspace data and is not reversible — confirm the target issue and comment content before executing.
Create linear issue
Creates a new issue in a specified Linear project and team, requiring team_id and title, and allowing optional properties like description, assignee, state, priority, cycle, and due date. All UUID parameters (state_id, assignee_id, cycle...
Create issue relation
Create a relationship between two Linear issues using the issueRelationCreate mutation. Use this to establish connections like 'blocks', 'duplicate', or 'related' between issues.
Create a label
Creates a new label in Linear for a specified team, used to categorize and organize issues. Label names must be unique within each team. If a label with the same name already exists, the existing label will be returned. Both new and exis...
What your agent does in Pagerduty
Add service to incident workflow trigger
Adds a service to an existing incident workflow trigger in PagerDuty, enabling the trigger to fire for incidents on that service. Associates a specific service with an incident workflow trigger to automate incident management for that se...
Aggregate escalation policy incident metrics
This endpoint analyzes and aggregates incident metrics across all escalation policies in PagerDuty. It allows for detailed filtering and customization of the analysis, enabling users to gain insights into incident patterns, response time...
Aggregate incident metrics with filters
Retrieves and aggregates metrics for incidents across all services in PagerDuty. This endpoint allows for extensive filtering and customization of incident data, enabling detailed analysis of operational performance. It's particularly us...
Associate service dependencies
Associates multiple service dependencies in PagerDuty, allowing you to define relationships between supporting and dependent services. This endpoint is used to establish a hierarchical structure of services, which is crucial for effectiv...
Associate team with automation action
This endpoint associates a specific team with an automation action in PagerDuty. It allows you to link a team to an automated workflow, enabling better organization and management of automation actions within your incident response proce...
Audit escalation policy records
Retrieves the audit records for a specific escalation policy in PagerDuty. This endpoint allows users to access a detailed history of changes made to the escalation policy, including modifications to escalation rules, associated services...
How it works
Tell the agent what you want to happen between Linear and Pagerduty, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Linear, works out what to do, and runs the matching action in Pagerduty without you mapping a single field.
You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.
Common questions about Linear and Pagerduty
- How do I connect Linear and Pagerduty to Operator?
- You authorize Linear and Pagerduty once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
- What can my agent do across Linear and Pagerduty?
- You describe the outcome in plain language and your agent works between the two, reading from one and acting in the other. It picks the right Linear and Pagerduty actions on its own, so you do not map fields or pick triggers.
- Can my agent keep Linear and Pagerduty in sync?
- Yes. It can watch Linear and act in Pagerduty, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
- Do I need to build a workflow or write code?
- No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.
Linear and Pagerduty integrations
Put your agent on Linear and Pagerduty
Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.
Try for free