TICKET MANAGEMENT
Post a daily digest of new regression tickets needing repro details to Slack
Every morning the workflow scans Zendesk for regression-tagged tickets opened in the last day, scores each on how complete its repro details are.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled each weekday morning
- ActionQuery Zendesk for last 24h regression ticketsZendesk
- ActionAgent scores each ticket ready/partial/blockedOpenAI
- LogicSort and group tickets by repro readiness
- OutputPost prioritized digest to triage Slack channelSlack
What it does
Gives the triage standup a single ranked list each morning. The workflow pulls every regression ticket from the last 24 hours, and for each one the agent judges whether it already has repro steps, an environment, and a version. It posts a Slack digest sorted by readiness, calling out exactly which tickets are missing what so the team chases the right customers first.
When to use it
Use it if regression triage is a daily ritual and people waste the first ten minutes figuring out which tickets are actionable versus which still need info from the customer.
How it works
- 1A scheduled trigger fires each weekday morning.
- 2The workflow queries Zendesk for tickets tagged `regression` created in the last 24 hours.
- 3The agent scores each ticket as ready, partial, or blocked based on presence of repro steps, environment, and version.
- 4A logic step sorts and groups tickets by readiness.
- 5A formatted Slack digest is posted to the triage channel with per-ticket gaps and links.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect OpenAIModels, embeddings, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Ticket Management workflows
Enrich Discord bug reports with Sentry errors before filing in Linear
Takes a Discord bug report, has an LLM pull out likely error signatures, searches Sentry for matching events.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
Weekly reopen-by-agent coaching digest
Aggregates each agent's solved-then-reopened tickets for the week, identifies the most common reopen reason per agent, and emails a private coaching digest to the support manager.
Escalate repeat reopens to a Linear bug
Detects when the same underlying issue reopens across multiple tickets, uses an AI agent to cluster them by root cause.
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.