CUSTOMER SUPPORT
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue moved to DoneLinear
- LogicKeep only deployed support-escalation issues
- ActionRead linked Zendesk ticket IDs from attachmentsLinear
- ActionFetch requester + status per ticketZendesk
- ActionPost resolved reply and set ticket solvedZendesk
- OutputComment notified-tickets list back on LinearLinear
What it does
Bridges the engineering tracker and the support desk. When a Linear issue that originated from a support escalation is moved to Done, this workflow finds the Zendesk tickets that spawned it and tells those requesters the work is complete and live.
When to use it
Use it when escalations flow Zendesk to Linear and customers never hear back once engineering finishes. Best for teams whose 'Done' column means deployed, so the notification is truthful.
How it works
- 1A Linear webhook fires when an issue transitions to the Done state.
- 2A filter keeps only issues that carry a support-escalation label and a deployed marker.
- 3The flow reads the linked Zendesk ticket IDs from the Linear issue's attachments.
- 4It fetches each ticket's requester and current status from Zendesk.
- 5It posts a public reply that the reported issue is resolved and sets the ticket to solved.
- 6It comments back on the Linear issue listing which tickets were notified, for an audit trail.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect ZendeskTickets, queues, knowledge base.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Article Volume-Rebound Early Warning (Datadog)
Streams support ticket-tag events into Datadog, watches for topics whose volume is reaccelerating against a decaying article.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.