Schedule icon
Request icon
Script icon
Docker icon
If icon
SlackIncomingWebhook icon

Linear stalled customer support escalation sync sentinel

Audit Linear customer escalation issues via GraphQL API for inactivity and SLA breaches, alerting support and engineering teams in Slack to speed resolution.

Categories
BusinessCloud

Continuously audits customer support escalations in Linear using the GraphQL API, identifies tickets with zero updates past a defined day threshold, and dispatches priority notifications to Slack to avert SLA breaches.

What you get

  • Real-time detection of high-impact customer escalations that have stalled without updates.
  • Automated SLA tracking based on ticket updatedAt timestamps and priority labels.
  • Targeted Slack notifications with ticket identifiers, assignee names, and direct Linear links.
  • Improved customer trust and faster mean time to resolution (MTTR) on critical bugs.

Who it's for

  • Customer Success and Support Engineering Leads responsible for customer response SLAs.
  • Product Managers and Engineering Directors managing escalation backlogs.
  • Software Engineers on triage rotation addressing tier-3 customer bug reports.

Why orchestrate this with Kestra

Customer escalations often get lost in broad engineering project boards. Kestra automates periodic GraphQL queries to Linear, isolates tickets marked with customer tags, computes inactivity periods in Python, and routes actionable summaries to triage channels, eliminating manual spreadsheet tracking or custom webhook infrastructure.

Prerequisites

  • A Linear API key or personal API token with read access to issues and teams.
  • A Slack Incoming Webhook URL configured for customer support or triage alerts.

Secrets

  • LINEAR_API_KEY: Linear API token passed in the Authorization header.
  • SLACK_WEBHOOK_URL: Slack Incoming Webhook URL used to deliver escalation alerts.

Quick start

  1. Define LINEAR_API_KEY and SLACK_WEBHOOK_URL in Kestra Secrets.
  2. Set team_key to your Linear team key (e.g., ENG) and verify escalation_label matches your tag.
  3. Run a manual execution from the Kestra UI to verify that escalated tickets are queried.
  4. Enable the daily_escalation_audit_schedule trigger to run weekday checks before morning standup.

How to extend

  • Add automated Linear comment creation or priority elevation mutations via GraphQL when tickets remain idle past 10 days.
  • Integrate with Zendesk or Salesforce to cross-reference ticket customer tiers (e.g. Enterprise vs Starter).
  • Aggregate monthly escalation aging trends into Google BigQuery or Snowflake for quarterly SLA reporting.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.