SUMMARIZATION
Axiom Reliability Note That Files Its Own Follow-Ups
Summarizes the week's Axiom log patterns into a plain-English reliability note, then has an agent open prioritized GitHub issues for the patterns worth fixing and posts…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionFetch ranked recurring patternsAxiom
- ActionDraft note and pick fix-worthy patternsOpenAI
- ActionOpen or de-dupe GitHub issuesGitHub
- OutputPost note with issue links to DiscordDiscord
What it does
Goes one step past summarizing: it not only writes the weekly plain-English reliability note from Axiom logs, but also decides which recurring patterns deserve engineering work and files tracked follow-up issues for them. The Discord digest then links straight to the issues it created, closing the loop between observation and action.
When to use it
Use it when reliability reviews keep surfacing the same unactioned errors. The agent turns the recurring offenders into real tickets so they stop reappearing in next week's note.
How it works
- 1A weekly schedule trigger starts the run.
- 2An Axiom action returns ranked recurring error patterns with counts and trends.
- 3An agent step reasons over the patterns, drafts the plain-English note, and chooses which ones are fix-worthy versus expected noise.
- 4For each fix-worthy pattern, a GitHub action opens (or de-dupes against) a prioritized issue with sample lines and context.
- 5A Discord output posts the reliability note with links to every issue filed.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect DiscordCommunity channels + voice + bots.
- 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
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.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
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.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
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.