TICKET MANAGEMENT
Approve-to-Merge: Execute Front Conversation Merges from Slack
Listens for an agent clicking Approve on a Slack merge suggestion, then merges the duplicate Front conversations, links them, and confirms the result back in the thread.
How it runs
The automated pipeline, trigger to output.
- TriggerAgent clicks Approve in SlackSlack
- LogicParse survivor + duplicate IDs from payload
- LogicVerify both conversations still open
- ActionMerge, note, and archive in FrontFront
- ActionRecord merge in audit logPostgres
- OutputUpdate Slack thread to Merged statusSlack
What it does
This is the action half of the merge loop. When an agent clicks Approve on a duplicate suggestion in Slack, the workflow performs the actual merge in Front, archives the duplicate, leaves an internal note pointing to the surviving conversation, and confirms back in Slack.
When to use it
Pair it with a detector that posts merge suggestions. Use this when you want human approval to stay mandatory but the merge mechanics to be fully automated, so agents never touch Front to combine tickets.
How it works
- 1A Slack interaction webhook fires when an agent clicks the Approve button on a suggestion.
- 2The workflow parses the payload to read both conversation IDs and which one is the survivor.
- 3A guard checks that both conversations are still open and unmerged to avoid double-merging.
- 4The workflow moves the duplicate's messages into the surviving Front conversation, adds an internal note linking them, and archives the duplicate.
- 5The merge outcome and surviving link are written to Postgres for an audit trail.
- 6A confirmation replaces the Slack buttons with a Merged-by-agent status in the original thread.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect FrontShared inbox, conversations.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.