MARKETING
Agent-driven CWV regression triage → root-cause note in Linear
When a Core Web Vitals alert fires, an agent pulls the RUM breakdown and recent deploy diff, reasons about the likely cause (image, script, font, or layout), and opens a Linear…
How it runs
The automated pipeline, trigger to output.
- TriggerCWV regression alert webhookHTTP webhook
- ActionFetch Cloudflare RUM metric breakdown for routeCloudflare
- ActionPull GitHub diff for triggering deployGitHub
- LogicCorrelate metric shift with diff; rank likely causes
- OutputOpen Linear issue with hypothesis and suggested fixLinear
What it does
On a Core Web Vitals regression alert, this agent gathers the Cloudflare RUM metric breakdown for the affected page and the GitHub diff of the deploy that preceded it. It reasons about which change most plausibly caused the regression — an oversized hero image, a new blocking script, a font swap, or a shifting ad slot — and opens a Linear issue containing the metric deltas, the suspect commit, a plain-English root-cause hypothesis, and a concrete remediation suggestion.
When to use it
Use it when raw alerts aren't enough and you want first-pass triage done for you, so the engineer who picks up the ticket starts from a hypothesis rather than a blank investigation.
How it works
- 1A webhook delivers a CWV regression alert with the affected route.
- 2The agent fetches the Cloudflare RUM metric breakdown for that route.
- 3It pulls the GitHub diff for the commit range of the triggering deploy.
- 4The agent correlates the metric shift with the diff and forms a ranked hypothesis.
- 5It writes a Linear issue with deltas, suspect commit, root cause, and a suggested fix.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 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.