TICKET MANAGEMENT
Publish a Weekly Intercom Issue-Theme Digest to Notion
Every Monday, summarizes the prior week's top recurring Intercom themes with trend deltas and representative quotes.
How it runs
The automated pipeline, trigger to output.
- TriggerMonday-morning schedule kicks off
- ActionPull this week and prior week theme countsPostgres
- ActionSummarize themes and pick quotesOpenAI
- LogicCompute trend deltas and sort by momentum
- OutputPublish dated digest page to NotionNotion
What it does
Produces a clean weekly readout of what customers complained about most, how each theme moved week over week, and verbatim quotes that capture the pain — published straight into Notion for product planning.
When to use it
Use it for a recurring product or support sync where you need a curated, skimmable summary of customer pain instead of raw ticket dashboards. It replaces the manual Friday-afternoon roundup.
How it works
- 1A Monday-morning schedule kicks off the digest.
- 2The flow pulls the past week's clustered themes and counts from the Postgres `issue_themes` table, plus the prior week's counts for comparison.
- 3OpenAI writes a tight summary per theme and selects one representative customer quote from the source Intercom conversations.
- 4A logic step computes week-over-week trend deltas and sorts themes by volume and momentum.
- 5The flow formats the digest with headings, counts, deltas, and quote callouts.
- 6It creates a new dated page in the target Notion database so the team has a permanent, searchable archive of weekly digests.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect IntercomConversations, contacts, articles.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect NotionPages, databases, comments.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Ticket Management workflows
Deduplicate Discord bug reports against existing Linear issues
Before creating anything, searches Linear for issues matching a new Discord bug report; if a duplicate exists it comments and links the report there, otherwise it opens a fresh…
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.
Promote a Discord message to a Linear issue via an emoji reaction
When a moderator adds a designated emoji reaction to any Discord message, an LLM converts that message into a structured Linear issue and threads the link back.
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.
Route Discord bug reports by severity to Linear or PagerDuty
Classifies each Discord bug report by severity using an LLM, then files normal bugs as Linear issues while escalating critical outages to a PagerDuty incident so on-call gets…
Triage Discord bug threads into structured Linear issues with repro checklists
Watches a Discord bug-report channel, uses an LLM to extract a clean title, severity, and step-by-step reproduction checklist from the messy thread.
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.