SUMMARIZATION
Earnings miss-only conditional alert with full brief
Scrapes a transcript on a webhook trigger, scores guidance vs actuals, and only when a material miss is detected, escalates a Slack alert plus a detailed Notion brief.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook with new transcript URLHTTP webhook
- ActionScrape transcript to clean textFirecrawl
- ActionExtract metric variances vs guidanceOpenAI
- LogicBranch on material-miss threshold
- ActionWrite full variance briefNotion
- OutputPost urgent miss alertSlack
What it does
Filters the noise. It analyzes an earnings transcript and only interrupts the finance lead when there's a material guidance miss worth their attention. Clean or in-line quarters are logged silently; misses beyond a set threshold trigger an urgent Slack ping linked to a full variance brief in Notion.
When to use it
Use when the team tracks many tickers and only wants to be pulled in on bad news. The conditional branch prevents alert fatigue while still archiving every quarter for the record.
How it works
- 1A webhook fires when an upstream IR monitor posts a new transcript URL.
- 2Firecrawl scrapes the transcript to clean text.
- 3OpenAI extracts each metric's guidance range, actual, and percentage variance.
- 4A logic step checks whether any metric misses guidance by more than the threshold.
- 5If no material miss, the run ends silently after archiving.
- 6If a miss is found, OpenAI writes a full variance brief to Notion and Slack posts an urgent alert linking it.
Set it up
What you configure once, before turning it on.
- 1Connect FirecrawlCrawl, scrape, structured extract.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Connect HTTP webhookTrigger any URL on agent actions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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 this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.