MARKETING

Validate new campaign links against your UTM naming convention

Whenever a marketer adds a campaign URL to your Airtable tracker, it parses the UTM parameters, checks them against your naming rules.

CategoryMarketing
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew/updated row in Airtable campaign-links tableAirtableAirtable
  • ActionParse UTM parameters from the link URL
  • LogicCheck source, medium, campaign, content against naming rules
  • LogicBranch on pass vs. fail
  • OutputWrite Approved or Rejected + reasons back to the rowAirtableAirtable

What it does

This workflow enforces your UTM naming convention at the moment a link is created. When someone adds a row to your campaign-link Airtable, it pulls the URL apart, checks every UTM parameter against your rules (allowed sources, lowercase mediums, slug format for campaign names), and writes a clear pass/fail verdict back to the record before anyone shares the link.

When to use it

Use it when your team builds tracking links in a shared Airtable and you keep finding `Source=Email`, `medium=CPC `, or freeform campaign names polluting your analytics. It catches mistakes at entry instead of three weeks later in a messy attribution report.

How it works

  1. 1A new or edited row in the Airtable campaign-links table triggers the run.
  2. 2The link's query string is parsed into individual utm_* parameters.
  3. 3Validation logic checks each parameter: source against an allowlist, medium against lowercase-only rules, campaign against your slug pattern, and content/term for required presence.
  4. 4If any check fails, the row is updated with a Rejected status and a per-field reason list.
  5. 5If everything passes, the row is marked Approved and stamped with a validated-at timestamp.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  3. 3
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  4. 4
    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.