MARKETING

UTM link gatekeeper API for your link-builder tool

Exposes a webhook that any internal tool or form can POST a candidate URL to; it returns a structured verdict (valid or not.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHTTP webhook receives candidate URLHTTP webhook
  • ActionParse UTM parameters from the payload URL
  • LogicValidate source/medium pairs, campaign slug, required fields
  • ActionAssemble verdict with per-field errors
  • OutputRespond with JSON valid/invalid verdictHTTP webhook

What it does

This turns your UTM convention into a callable validation service. Your link-builder UI, marketing form, or campaign launch script POSTs a URL to the webhook, and the workflow returns a JSON verdict listing whether the link is compliant and exactly which parameters failed. It lets you block bad links inline rather than catching them after launch.

When to use it

Use it when you want UTM enforcement embedded directly in the tool where links are created — a CMS plugin, an internal microsite, or a Slack slash command — instead of a separate review step. One canonical rule set, called from anywhere.

How it works

  1. 1An inbound HTTP webhook receives a POST with the candidate URL (and optional channel context).
  2. 2The workflow parses the query string into utm_* fields.
  3. 3Validation logic enforces the convention: known source/medium pairs, lowercase normalization, slug-formatted campaign, and required content for paid channels.
  4. 4A verdict object is assembled with an overall boolean and an array of per-field errors.
  5. 5The webhook responds with that JSON so the calling tool can approve or block the link in real time.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  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.