MARKETING

Launch a Vercel Edge Config A/B variant with a tracked Notion record

On demand, provisions a new A/B variant in Vercel Edge Config with an even traffic split and creates a Notion experiment record capturing the hypothesis, owner, and start date…

CategoryMarketing
Enginesim
Difficultybeginner
Triggermanual
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOperator runs the launch with experiment details
  • LogicValidate inputs and compute even traffic split
  • ActionWrite new experiment block to Vercel Edge ConfigVercelVercel
  • ActionCreate Notion experiment record with hypothesis and ownerNotionNotion
  • OutputPost launch confirmation to SlackSlack

What it does

Standardizes how experiments get started. Instead of an engineer hand-editing Edge Config and the result living only in someone's head, this flow takes the experiment name, hypothesis, and variant list, writes a clean split into Vercel Edge Config, and opens a matching Notion record. It guarantees every live experiment has a documented hypothesis and owner before it ever serves traffic.

When to use it

Use it whenever a marketer or PM wants to kick off a test without filing a ticket. It removes the setup friction that causes undocumented, orphaned experiments.

How it works

  1. 1An operator runs the flow with the experiment name, hypothesis, owner, and variant labels.
  2. 2Validate the inputs and compute an even traffic split across the variants.
  3. 3Write the new experiment block into Vercel Edge Config so it goes live.
  4. 4Create a Notion experiment record with hypothesis, owner, start date, and the configured split.
  5. 5Post a launch confirmation with the experiment link to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect VercelDeploys, runtime logs, analytics.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.