MARKETING

Bulk-cleanse UTM links from a Drive upload

When a campaign link CSV is dropped in a Google Drive folder, it validates every row against the UTM taxonomy and writes back two files.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew CSV appears in watched Drive folderGoogle DriveGoogle Drive
  • ActionDownload and parse all URL rowsGoogle DriveGoogle Drive
  • LogicValidate each row against the taxonomy
  • LogicSplit into clean and quarantine sets with annotations
  • ActionWrite clean and quarantine files back to DriveGoogle DriveGoogle Drive
  • OutputSend batch summary to SlackSlack

What it does

This workflow handles bulk link imports. An agency or media team drops a CSV of campaign URLs into a watched Google Drive folder; the flow reads every row, validates the UTM parameters against your taxonomy, and splits the file into a clean set and a quarantine set. The quarantine file annotates each failed row with the precise violation so the sender can correct and resubmit.

When to use it

Use it for large batches — a quarter of paid campaigns, a partner's link list, or a migration — where validating links one at a time is impractical and you need a single round-trip cleanse.

How it works

  1. 1A new CSV appears in the watched Drive folder.
  2. 2The flow downloads and parses every row's URL.
  3. 3Each row is validated against approved vocabularies and formatting rules.
  4. 4Rows split into clean and quarantine sets, with violations annotated per failed row.
  5. 5Two result files are written back to Drive and a summary is sent to Slack.

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.