MARKETING

Weekly CWV trend report → Notion page + Slack summary

Every week pulls Vercel Speed Insights field data for all landing pages, builds a week-over-week LCP/CLS/INP trend table, publishes it to a Notion page.

CategoryMarketing
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionPull Vercel Speed Insights field metrics for all pagesVercelVercel
  • LogicCompute week-over-week deltas and rank movers
  • ActionPublish trend table to Notion report pageNotionNotion
  • OutputPost top movers summary to SlackSlack

What it does

Once a week this workflow gathers Vercel Speed Insights field metrics for every tracked landing page, computes week-over-week changes in p75 LCP, CLS, and INP, and assembles a trend table. It publishes the full report as a Notion page for the record and posts a short Slack summary highlighting the biggest improvements and regressions, giving marketing a recurring performance scorecard without manual data pulls.

When to use it

Use it for a standing weekly performance review when you want a durable, shareable history of Core Web Vitals across all landing pages rather than only reactive per-deploy alerts.

How it works

  1. 1A weekly schedule triggers the report.
  2. 2The flow pulls Vercel Speed Insights field metrics for all tracked pages.
  3. 3It computes week-over-week deltas per metric and ranks the movers.
  4. 4The full trend table is published to a Notion report page.
  5. 5A concise summary of top improvements and regressions is posted to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect VercelDeploys, runtime logs, analytics.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.