TICKET MANAGEMENT
Post a daily Linear cycle scope-delta digest to Discord
Once a day, compares the current cycle's committed points against its present scope and posts a Discord digest showing net points added, issues inserted, and percent over…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday morning schedule
- ActionPull active cycle and all issue estimates from LinearLinear
- LogicCompute added, removed, and net points vs commitment
- LogicAssign scope-health label from delta percentage
- OutputPost scope-delta digest to DiscordDiscord
What it does
Each morning this workflow snapshots the active Linear cycle, computes how its scope has drifted since planning, and posts a digest to Discord. The digest shows committed points versus current points, the net delta, the count of issues added and removed, and the scope as a percentage of the original commitment.
When to use it
Use it when a single real-time ping per addition is too noisy and you would rather have one daily summary of where the cycle stands. It suits team leads who run a quick standup and want a shared, objective scope number to anchor the conversation.
How it works
- 1A scheduled trigger runs every weekday morning before standup.
- 2An action step pulls the active cycle and all its issues with estimates from Linear.
- 3A logic step compares the current issue set against the stored commitment snapshot to compute added, removed, and net points.
- 4A logic step decides the health label (on track, watch, or over) from the delta percentage.
- 5The workflow posts the formatted scope-delta digest to Discord with the health label up front.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect DiscordCommunity channels + voice + bots.
- 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 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.