Monitor ad campaign health daily with Spendict, Google Sheets, and Slack
Ready for 3.0What this workflow does
This workflow has 9 nodes and runs on a schedule (every day at 08:00). Along the way it connects Google Sheets. It also calls spendict.com and hooks.slack.com over HTTP.
How it runs
Trigger: On a schedule (every day at 08:00).
- Google Sheets: uses Google Sheets
- Build diagnosis payload (Code): runs custom JavaScript code
- Spendict: analyze_campaign_performance (HTTP Request): calls spendict.com (POST)
- Route on health (Switch): routes items into 3 branches
- Row: healthy / no data (Code): runs custom JavaScript code
- Row: needs attention (Code): runs custom JavaScript code
- Google Sheets: append
- Slack: alert (HTTP Request): calls hooks.slack.com (POST)
Services it uses
HTTP calls to: spendict.com, hooks.slack.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (5)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Google Sheets
n8n-nodes-base.googleSheets - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Switch
n8n-nodes-base.switch
From the author
Quick overview This workflow runs every morning to read ad campaign metrics from Google Sheets, send each campaign to Spendict for performance diagnosis against benchmarks, log the verdicts back to Google Sheets, and post Slack alerts when a campaign needs…