SUMMARIZATION
Earnings-call guidance-vs-actuals delta brief to Notion
Scrapes a freshly posted earnings-call transcript, extracts every forward guidance figure and actual result, and publishes a one-page delta brief to Notion flagging each beat.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled run on earnings morning
- ActionScrape transcript to clean textFirecrawl
- ActionExtract guidance and actuals tableOpenAI
- LogicClassify each metric beat / miss / inline
- ActionDraft headline and variance narrativeOpenAI
- OutputPublish dated delta brief to NotionNotion
What it does
Turns a long earnings-call transcript into a tight finance-ready brief that pairs each prior-quarter guidance number against the actual reported result, labels it beat / miss / inline, and explains the variance in plain English. The output lands as a structured Notion page the finance lead can scan in two minutes.
When to use it
Run it the morning after a portfolio company, competitor, or your own company reports. Good for FP&A teams, IR analysts, and operators who track a watchlist and need the guidance-vs-actuals story without reading 12,000 words of transcript.
How it works
- 1A scheduled check fires on earnings morning.
- 2Firecrawl scrapes the published transcript URL and strips it to clean text.
- 3OpenAI extracts a structured table of metrics: prior guidance range, actual, and management commentary per line item.
- 4A logic step classifies each metric as beat, miss, or inline using the guidance midpoint.
- 5OpenAI drafts a headline takeaway plus a variance narrative for the flagged misses.
- 6The brief is written to Notion as a dated page under the earnings database.
Set it up
What you configure once, before turning it on.
- 1Connect FirecrawlCrawl, scrape, structured extract.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 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 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.