AI AGENTS
Daily Competitor Pricing Digest from Firecrawl Crawl to Discord
Each morning Firecrawl crawls competitor pricing and plans pages, an agent summarizes every change since yesterday into a single readable brief.
How it runs
The automated pipeline, trigger to output.
- TriggerMorning schedule triggers run
- ActionCrawl competitor pricing pages to markdownFirecrawl
- ActionLoad yesterday's markdown snapshotPostgres
- ActionAgent diffs and writes daily digestOpenAI
- LogicSkip delivery on a quiet day
- OutputPost digest to Discord channelDiscord
What it does
Produces one daily pricing brief instead of a stream of pings. Firecrawl crawls each competitor's pricing/plans page, an agent compares today's content to yesterday's stored markdown, and writes a human-readable digest of what changed across all competitors — new tiers, removed plans, price bumps, copy changes — then drops it in Discord.
When to use it
Use it when you want a calm, once-a-day rollup rather than real-time interrupts, and when competitors publish structured pricing pages that change subtly (feature gating, tier renames) rather than just headline prices.
How it works
- 1A morning schedule triggers the run.
- 2Firecrawl crawls and returns clean markdown for each competitor pricing URL.
- 3Yesterday's markdown is loaded from Postgres for comparison.
- 4An OpenAI agent diffs old vs. new, ignoring cosmetic noise, and writes a per-competitor summary plus an overall headline.
- 5A logic step skips delivery entirely on a fully quiet day to avoid empty digests.
- 6Today's markdown is persisted, and the formatted digest is posted to Discord.
Set it up
What you configure once, before turning it on.
- 1Connect FirecrawlCrawl, scrape, structured extract.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect OpenAIModels, embeddings, files.
- 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 AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.