MARKETING
Promote a winning Vercel variant to 100% and publish a retro
When a winner-declared event fires, ramps the winning Vercel Edge Config variant to full traffic, generates a written experiment retro, files it in Notion.
How it runs
The automated pipeline, trigger to output.
- TriggerWinner-declared event fires with experiment and variant
- ActionPromote winning variant to 100% traffic in Vercel Edge ConfigVercel
- ActionGenerate experiment retro with lift and next stepsOpenAI
- ActionSave retro as a linked Notion documentNotion
- OutputAnnounce rollout and retro link in SlackSlack
What it does
Handles the happy-path ending of an experiment. When a variant is declared the winner, this flow promotes it to 100% of traffic in Vercel Edge Config (replacing the old split), drafts a concise retro covering the hypothesis, the lift achieved, and what to test next, saves that retro to Notion, and broadcasts the win to the team. The experiment's success becomes a durable, shareable artifact instead of a Slack thread that scrolls away.
When to use it
Use it the moment a test reaches a confident winner and you want the rollout plus documentation to happen in one consistent motion, with no manual Edge Config edits and no forgotten write-up.
How it works
- 1A winner-declared event triggers the flow with the experiment and winning variant.
- 2Rewrite Vercel Edge Config to send 100% of traffic to the winning variant.
- 3Generate a retro summarizing hypothesis, measured lift, and next tests.
- 4Save the retro as a Notion document linked to the experiment record.
- 5Announce the rollout and link the retro in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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
UTM Link Linter: Block Malformed Tracking URLs Before Launch
Validates every campaign tracking link queued in an Airtable launch table against your UTM naming rules.
Spin up a rush localization handoff from a Slack chat request
A marketer asks the CEO agent in chat to rush-translate a piece of approved copy into specific languages; the agent files the source in Google Drive.
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.
UTM Audit for Campaign Spreadsheets in Google Drive
Watches a Google Drive folder for new or updated campaign link spreadsheets, lints every URL inside.
Real-Time UTM Validator API for Link-Building Forms
Exposes a webhook that validates a tracking URL on the fly and returns a structured pass/fail JSON response.
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.
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.