CUSTOMER SUPPORT
Weekly digest of shipped fixes mapped to the tickets they closed
On a schedule, compile the week's Sentry issues resolved in deploys, link each to the support tickets it affected.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery Sentry issues resolved in deploys this weekSentry
- ActionCount linked Zendesk tickets per issueZendesk
- ActionAgent writes non-technical changelog entriesOpenAI
- ActionPublish entries to Notion changelogNotion
- OutputPost impact-ranked recap to SlackSlack
What it does
Turns a week of shipped fixes into two artifacts: a public-facing changelog entry of what got fixed, and an internal recap of how many tickets each fix cleared. It aggregates rather than notifying per-event, giving stakeholders the big picture.
When to use it
Use it when individual fix-live replies are already handled elsewhere and you instead want a periodic rollup for a status page, changelog, or weekly support-engineering sync. Good for reporting resolution impact.
How it works
- 1A weekly schedule triggers the workflow.
- 2The flow queries Sentry for all issues resolved in deploys over the past seven days.
- 3For each issue it counts the linked Zendesk tickets to measure customer impact.
- 4An agent writes a clear, non-technical changelog entry per fix from the issue title and notes.
- 5It publishes the compiled entries to a Notion changelog page.
- 6It posts an internal Slack recap ranking fixes by tickets cleared, for the team sync.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect ZendeskTickets, queues, knowledge base.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Connect OpenAIModels, embeddings, files.
- 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.