MARKETING

Daily Cloudflare RUM CLS watch → Slack digest with worst pages

Each morning pulls Cloudflare Web Analytics RUM for the last 24 hours, flags landing pages whose Cumulative Layout Shift crossed the 'needs improvement' line.

CategoryMarketing
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionQuery Cloudflare RUM p75 CLS per page (24h)CloudflareCloudflare
  • LogicKeep pages above CLS threshold; compute day-over-day delta
  • LogicEnd silently if none regressed
  • OutputPost ranked worst-pages digest to SlackSlack

What it does

Once a day this workflow reads Cloudflare Web Analytics real-user metrics for your marketing domain, computes p75 CLS per page over the trailing 24 hours, and identifies any landing pages that slipped above the 0.1 'good' boundary. It posts a concise Slack digest ranking the worst offenders with their CLS value and day-over-day change, so the team sees layout-shift problems before a weekly review.

When to use it

Use it when ads, embeds, or late-loading banners cause layout jank on high-traffic landing pages and you want a lightweight daily pulse instead of digging through the Cloudflare dashboard manually.

How it works

  1. 1A scheduled trigger runs every morning.
  2. 2The flow queries Cloudflare Web Analytics for per-page p75 CLS over the last 24h.
  3. 3A filter keeps only pages above the CLS threshold and computes the delta vs. the prior day.
  4. 4If nothing crossed the line, the run ends silently.
  5. 5Otherwise it formats a ranked list of worst pages with values and trend arrows.
  6. 6The digest is delivered to the marketing Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.