CUSTOMER SUPPORT
Auto-File Linear Tickets for Contradictory Macros
Scans Zendesk macros against linked Confluence articles weekly and opens a deduplicated Linear issue for each macro that contradicts current docs.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule starts the scan
- ActionPull macros and linked articlesZendesk
- ActionLLM detects contradictions and drafts corrected textOpenAI
- LogicCheck Linear for an existing open issue for the macroLinear
- ActionCreate or update the Linear issue with the fixLinear
- OutputPost new/updated issue counts to SlackSlack
What it does
This workflow turns macro drift into tracked, assignable work. On a weekly cadence it audits macros against their help-center sources, and for every genuine contradiction it drafts a suggested replacement and files a Linear issue containing the old text, the conflict, and the proposed fix. Existing open issues for the same macro are updated rather than duplicated.
When to use it
Choose this over a Slack digest when drift fixes need to flow through your normal engineering or content backlog with owners, priorities, and status. Best for teams that triage support-content work in Linear and want an auditable trail of what was corrected and when.
How it works
- 1A weekly schedule starts the scan.
- 2Pull active macros and their linked articles from Zendesk and Confluence.
- 3The LLM detects contradictions and drafts corrected macro text for each one.
- 4Check Linear for an existing open issue keyed to the macro.
- 5If one exists, append the latest finding; otherwise create a new issue with the diff and suggested fix.
- 6Post a summary count of new and updated issues to Slack for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect LinearIssues, projects, cycles, triage.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Flag Live Intercom Chats With No Help Article and Alert Slack
When an Intercom conversation closes, checks whether the customer's question is already covered by a help article.
Negative VIP CSAT to Owner Callback Scheduler
When a VIP submits a low Intercom CSAT rating, drafts a recovery note with an LLM and books a callback on the account owner's Google Calendar within their working hours.
CEO Agent: Mine Last Month's Tickets and Publish a Deflection Plan
Monthly, an agent investigates the top recurring Zendesk ticket themes, drafts and publishes the highest-confidence help articles to ReadMe.
Mine a Discord Support Channel for Recurring Questions to Document
On a daily schedule, scans a Discord support channel for questions the community keeps asking, deduplicates against existing ReadMe docs.
Daily VIP Sentiment Digest for Account Owners
Each morning, pulls the prior day's Intercom conversations for VIP accounts, summarizes the overall mood per account with an LLM.
VIP Reply Sentiment Watcher with Account-Owner Escalation
Scores every inbound Intercom reply from a VIP customer for frustration and, when it crosses the anger threshold, pings the account owner in Slack with the conversation link…
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.