MARKETING
LCP regression guard after Vercel deploy → Linear fix task
After each production deploy to a landing page, waits for fresh Vercel Speed Insights data, compares LCP against the pre-deploy baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel production deployment succeedsVercel
- LogicWait for RUM data-collection window
- ActionFetch current p75 LCP per tracked routeVercel
- LogicCompare to stored baseline; pass if within tolerance
- ActionOpen Linear bug for regressed routesLinear
- OutputWrite new readings back as baselinePostgres
What it does
After a Vercel production deployment finishes, this workflow waits for real-user LCP data to accumulate, pulls the latest Largest Contentful Paint for your tracked landing routes, and compares it to the baseline from the previous deploy. If LCP regresses past your threshold (e.g. +200ms or crossing the 2.5s 'good' line), it files a Linear issue with the route, before/after numbers, and the deploy URL so an engineer can act before the regression reaches more visitors.
When to use it
Use it when marketing ships frequent landing-page changes (hero swaps, new scripts, font updates) and you need an automatic guardrail so a heavy third-party tag or unoptimized image doesn't quietly tank conversion-critical LCP.
How it works
- 1A Vercel deployment-succeeded webhook fires for the production environment.
- 2The flow holds for a data-collection window so Speed Insights has enough samples.
- 3It queries Vercel analytics for current p75 LCP per tracked route.
- 4A branch compares each route to the stored baseline and exits quietly if all are within tolerance.
- 5Regressed routes trigger a Linear issue with deltas and the deploy link.
- 6The new readings are written back as the next baseline.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.