N8N WORKFLOW SETUP
Add Search Ads 360 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 Search Ads 360 to Adzviser
Sign in to Search Ads 360, allow Adzviser to read its reporting data, then select one customer. Selecting a manager customer reports across its queryable child customers.
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 Search Ads 360 request. Check the selected account, dates, and output before turning on its trigger.
AUTOMATION BLUEPRINT
Build a repeatable Search Ads 360 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 Search Ads 360 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 Search Ads 360 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 Search Ads 360 promptN8N AI AGENT INSTRUCTION
Use a structured Search Ads 360 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 Search Ads 360 accounts and ask me which one to use. Then complete this analysis: Analyze weekly Search Ads 360 trends across engines from the workspace I choose for the last 30 complete days. Show: Engine, Weekly Spend, CPA, and ROAS Trends. Are engines trending in the same direction? What's driving differences? Recommend strategic adjustments. Return valid JSON with keys summary, evidence, alerts, and next_steps so the following n8n node can route the result reliably.
