⚡ Campaign Link Sheet Changelog
Turns a public campaign-tracking spreadsheet CSV into a Thursday changelog of destination links that appeared or left since the last activated run, grouped by channel when that column exists.
What it does
Ops and growth teams often keep landing destinations in a Sheet with columns like destination_url, channel, campaign, and owner. Export that Sheet to a CSV on HTTPS and this workflow writes a readable changelog for whoever reviews link hygiene on Thursdays.
It is intentionally not a crawler, not an XML sitemap reader, and not an uptime ping. It only re-reads the spreadsheet export you already publish.
Steps after import
- Schedule Trigger — Thursdays 07:15 in the n8n timezone.
- Sheet export config — set
sheet_csv_url,destination_column(defaultdestination_url), and optionalchannel_column(defaultchannel). - HTTP Request — downloads the CSV text.
- Code — collects destination links, remembers last week’s set in workflow static data, and writes Markdown sections for newcomers and retirees. When a channel column is present, newcomers are listed under their channel heading.
- Convert to File — attaches
campaign-link-changelog.mdto the execution.
credentials in the catalog entry stay empty. Add Slack/email yourself if you want delivery.
Practical notes
- First activated run only stores the baseline inventory from the Sheet.
- Rows without an http(s) destination are ignored.
- If the channel cell is blank, newcomers land under
uncategorized. - Keep the export small enough that static data stays manageable.
Required nodes
- Schedule Trigger
- Edit Fields (Set)
- HTTP Request
- Code
- Convert to File
Credentials
None. This flow runs without any credentials.
Our JSON never contains credentials, credential IDs or webhook URLs. You connect your own after import.
Import steps
- Download the JSON file above.
- In n8n, open a new workflow, then open the Workflow menu in the canvas header and choose Import from File…. You can also paste the JSON straight into the editor.
- Check the settings in each node (URLs, schedules, recipients) and change them to your own.
- Click Execute workflow once to test, then click Publish so schedules and webhooks run in production. Full guide.
Test log
No recorded test runs yet. We only list a tool under “Tested on” after a real run passes, with the date and model.