MARKETING

Scheduled UTM Sweep of Campaign Spreadsheets in Drive

Runs on a schedule, scans campaign-link spreadsheets in a Google Drive folder, audits every URL's UTM parameters.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule before the send window
  • ActionList and read campaign spreadsheets in Drive folderGoogle DriveGoogle Drive
  • LogicExtract URLs and parse UTM parameters
  • LogicFlag malformed, missing, or duplicate tracking
  • OutputPost grouped issue digest to SlackSlack

What it does

On a recurring schedule, this workflow opens each campaign spreadsheet in a designated Google Drive folder, reads every URL, and audits its UTM parameters. It produces a consolidated report of every offending link grouped by file.

When to use it

Use it when campaign links live in shared spreadsheets that many people edit and no single tool owns. A nightly or pre-send sweep catches drift across all of them at once instead of relying on per-row checks.

How it works

  1. 1Schedule trigger fires daily before the morning send window.
  2. 2A Google Drive action lists and reads the spreadsheet files in the target campaign folder.
  3. 3A logic step extracts all URLs and parses their UTM parameters.
  4. 4A logic step flags rows with missing required params, spaces, mixed case, or duplicate utm_campaign values across sheets.
  5. 5A Slack output posts a digest naming each file, the row, and the exact issue, with a clean-vs-flagged count summary.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  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.