MARKETING

New-Campaign UTM Pre-Launch Validation in HubSpot

When a campaign is created in HubSpot, validates every UTM-tagged link it contains against the taxonomy and blocks the launch with a corrective Slack alert if any link is…

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHubSpot campaign createdHubSpotHubSpot
  • ActionPull campaign's tracked linksHubSpotHubSpot
  • LogicValidate each link's UTMs vs taxonomy
  • LogicBranch: all pass vs violations found
  • ActionMark campaign not-launch-ready in HubSpotHubSpotHubSpot
  • OutputAlert owner with offending links in SlackSlack

What it does

Catches bad UTMs at the moment a campaign is born. When a new campaign record is created in HubSpot, the workflow extracts each tracked link, validates its UTM parameters against your taxonomy, and if anything is malformed it flags the campaign as not-ready and alerts the owner in Slack with the exact links and rules to fix before launch.

When to use it

Use it when campaigns are assembled in HubSpot and you want a hard pre-launch checkpoint. It prevents a launch from going out with untracked or mislabeled links rather than discovering the problem in next week's attribution report.

How it works

  1. 1A HubSpot campaign-created event triggers the workflow.
  2. 2An action pulls the campaign's tracked links and metadata.
  3. 3A validation step checks each link's UTM parameters against the taxonomy.
  4. 4A branch ends quietly when all links pass.
  5. 5When violations exist, an action marks the campaign as not-launch-ready in HubSpot.
  6. 6A Slack alert notifies the owner with each offending link and the rule it broke.

Set it up

What you configure once, before turning it on.

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