N8N WORKFLOW SETUP
Add Spotify Ads reporting to an n8n workflow
Connect Adzviser to an AI Agent, test one request, and only then add the schedule, alert, or delivery step.
Connect Spotify Ads to Adzviser
In Adzviser, sign in to Spotify Ads and allow Adzviser to read its reporting data.
Configure the MCP Client Tool
Add n8n's MCP Client Tool to an AI Agent, enter Adzviser's server address and credentials, and test the tool before activating the workflow.
https://mcp.adzviser.com/httpTest before activating
Run the workflow manually with one Spotify Ads request. Check the selected account, dates, and output before turning on its trigger.
AUTOMATION BLUEPRINT
Build a repeatable Spotify Ads reporting workflow
Keep the automation easy to audit: one trigger, one clearly scoped analysis, and one useful destination for the result.
Decide when it runs
Use a schedule, webhook, or manual trigger and calculate a complete reporting period before requesting data.
See a related Spotify Ads promptGive the AI Agent a stable instruction
Fix the account-selection rule, metrics, breakdowns, comparison, and output format so each run is consistent.
See a related Spotify Ads promptSend a result people can use
Route the takeaway and evidence table to email, Slack, a database, or the next approved step in your workflow.
See a related Spotify Ads promptN8N AI AGENT INSTRUCTION
Use a structured Spotify Ads instruction in every run
A predictable output makes the automation easier to test, route, and monitor.
Compare recent results with the previous period and call out the largest changes.
First show my connected Spotify Ads accounts and ask me which one to use. Then complete this analysis: Compare Spotify Ads performance this week vs last week for the workspace I choose during the last 30 complete days. Show changes for: Impressions, Reach, Frequency, Completion Rate, CTR, Conversions, CPA, and Spend. Flag metrics that changed by more than 15% with ⚠️. Provide explanations. Return valid JSON with keys summary, evidence, alerts, and next_steps so the following n8n node can route the result reliably.
