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…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled interval check
- ActionQuery Cloudflare RUM p75 INP per routeCloudflare
- LogicFlag breaches and update consecutive-breach counterPostgres
- LogicExit unless breach is sustained across windows
- ActionTrigger PagerDuty incident for on-callPagerDuty
- OutputOpen linked Linear incident taskLinear
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
- 1A schedule triggers the check on a fixed interval.
- 2The flow queries Cloudflare RUM for current p75 INP per tracked route.
- 3A branch flags routes above the INP threshold and updates a consecutive-breach counter in Postgres.
- 4If the breach count hasn't reached the sustained threshold, the run ends.
- 5Once sustained, it triggers a PagerDuty incident for on-call.
- 6It opens a linked Linear incident task with the route and trend.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect PostgresAny Postgres URL — query, write, migrate.
- 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 Marketing workflows
Agentic UTM Taxonomy Steward: Detect, Explain, and Propose Fixes
An agent reviews the full backlog of campaign links in Airtable, reasons about taxonomy drift beyond rigid rules, drafts standardized replacements for malformed UTMs.
Slack UTM Check: Paste a Link, Get an Instant Verdict
Lets marketers drop a tracking URL into a Slack channel and get an immediate threaded reply that says whether the UTMs are valid, what is wrong, and a corrected suggestion.
Backlink Outreach Drafter for Verified Mentions
Picks verified, high-authority unlinked mentions from Airtable, drafts a personalized backlink-request email for each.
Source-Authority Verifier for Mention Provenance
Takes a queue of detected brand mentions and runs an agent that verifies whether each source is a legitimate, authoritative publisher versus a scraper or syndication copy.
Unlinked Brand-Mention Detector with Authority Scoring
Scans the web for fresh brand mentions, filters to ones that name you without linking back, scores the publishing domain's authority.
Weekly Brand-Mention Provenance Digest to Notion
Aggregates the week's tracked mentions from Airtable into a single summarized report covering new opportunities, authority distribution, and outreach progress.
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.
