SUMMARIZATION
New Axiom Error Pattern Instant Explainer
When Axiom detects a log signature it has not seen before, this workflow fetches sample lines, has AI explain the likely cause and blast radius in plain English.
How it runs
The automated pipeline, trigger to output.
- TriggerNew unseen log signature detectedAxiom
- ActionFetch sample lines and trendAxiom
- ActionExplain cause, blast radius, severityOpenAI
- LogicBranch on severity guess
- OutputPage on-call (high) via PagerDutyPagerDuty
- OutputPost triage note (low/med) to SlackSlack
What it does
Instead of a weekly recap, this watches for the first appearance of a never-before-seen error signature and explains it immediately. It grabs a few representative log lines, asks AI what the error likely means and how widespread it is, then decides whether to quietly log it or wake someone up.
When to use it
Use it to shorten the gap between a new failure mode appearing and a human understanding it — especially right after a deploy, when novel errors are the early warning sign of a regression.
How it works
- 1An Axiom monitor trigger fires when a log signature with no prior history crosses a minimum count.
- 2An Axiom action pulls a small sample of matching log lines plus the count trend.
- 3An OpenAI action writes a plain-English explainer: likely cause, affected service, and a low/medium/high severity guess.
- 4A logic step branches on that severity.
- 5If high, a PagerDuty output opens an incident with the explainer attached; otherwise a Slack output drops a low-priority note for later triage.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.