MARKETING

Sustained INP regression escalation → PagerDuty + Linear

Polls Cloudflare RUM on a schedule for landing-page INP, and only after the regression persists across consecutive windows pages on-call via PagerDuty and opens a Linear incident…

CategoryMarketing
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled interval check
  • ActionQuery Cloudflare RUM p75 INP per routeCloudflareCloudflare
  • LogicFlag breaches and update consecutive-breach counterPostgreSQLPostgres
  • LogicExit unless breach is sustained across windows
  • ActionTrigger PagerDuty incident for on-callPagerDutyPagerDuty
  • OutputOpen linked Linear incident taskLinearLinear

What it does

This workflow checks Cloudflare Web Analytics RUM for p75 Interaction to Next Paint on your key landing pages at a regular interval. To avoid false alarms from noisy short windows, it requires the regression to hold across consecutive checks before escalating. Once a regression is confirmed sustained, it triggers a PagerDuty alert for on-call and opens a Linear incident task with the affected route and trend.

When to use it

Use it when INP regressions on revenue pages are serious enough to warrant paging on-call, but you want confirmation across multiple windows so you don't wake someone for a transient blip.

How it works

  1. 1A schedule triggers the check on a fixed interval.
  2. 2The flow queries Cloudflare RUM for current p75 INP per tracked route.
  3. 3A branch flags routes above the INP threshold and updates a consecutive-breach counter in Postgres.
  4. 4If the breach count hasn't reached the sustained threshold, the run ends.
  5. 5Once sustained, it triggers a PagerDuty incident for on-call.
  6. 6It opens a linked Linear incident task with the route and trend.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect PagerDutyIncidents, on-call, escalations.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  4. 4
    Connect PostgresAny Postgres URL — query, write, migrate.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.