SUMMARIZATION
Agentic Slack Decision Triage to Linear and GitHub
An agent reads a flagged Slack thread, extracts the decision and action items, then autonomously routes each one — engineering work to GitHub issues.
How it runs
The automated pipeline, trigger to output.
- TriggerFlag emoji added to a Slack threadSlack
- ActionAgent fetches thread and extracts decision plus action itemsSlack
- LogicAgent classifies each item as engineering or non-engineeringOpenAI
- ActionCreate GitHub issues for engineering itemsGitHub
- ActionCreate assigned Linear issues for non-engineering itemsLinear
- OutputReply in-thread explaining routing with linksSlack
What it does
Not every action item belongs in the same system. This agent-driven workflow reads a flagged Slack thread, extracts the decision and its action items, and reasons about where each item should live. Code or infrastructure work is opened as a GitHub issue in the relevant repository; product, ops, and process items become assigned Linear issues. The agent explains its routing decisions and posts a summary with links to everything it created.
When to use it
Use it when a single discussion spawns mixed work — bug fixes that belong in GitHub alongside product tasks that belong in Linear — and you want the routing decided intelligently rather than dumping everything in one tracker. Best for teams comfortable letting an agent choose the destination per item.
How it works
- 1A flag emoji on a Slack thread fires the trigger.
- 2The agent fetches the full thread and extracts the decision plus action items.
- 3For each action item the agent classifies it as engineering work or non-engineering work.
- 4Engineering items are created as GitHub issues in the inferred repository.
- 5Non-engineering items are created as assigned Linear issues.
- 6The agent posts a thread reply explaining each routing choice with links to the created items.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 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 Summarization workflows
Daily Front Escalation Digest with Salesforce Rollup
Each morning, sweeps the prior day's escalated Front conversations, summarizes each, enriches with Salesforce account value, and emails account execs a single prioritized digest.
File a Linear ticket for regressed errors after deploy
Detects Sentry issues that regressed in the latest deploy's release window, summarizes what broke and when it was previously fixed.
Daily release-health rollup to Confluence
Each morning, compares the last 24 hours of Sentry activity against the deploys that shipped in that window and publishes a dated release-health page to Confluence summarizing…
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
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.