I just don’t know what I could be doing wrong. I configured everything the way I thought it would work, but it still isn’t working. I don’t know what I could be doing wrong. And when I see from the node documentation, this happens:
Hi @Linecker, thanks so much for reporting this broken link! I’ve added it to the documentation backlog.
You can find the page here, but tbh it doesn’t exactly explain the individual operations: Google Ads node - n8n Documentation
I tried using the Google Ads node myself but tbh am a bit lost with the service. It seems they don’t allow sign ups without actually creating a campaign. I’ll ask for help internally and see if anyone know more about this node.
Could you confirm whether you have configured the developer token in your Google Ads credentials? It’s used by the node from the looks of it but is not marked as required in the credentials.
Getting a working credential is a bit annoying - have you followed all steps mentioned here Uzyskiwanie tokena programisty | Google Ads API | Google Developers ?
When creating a manager account you can create a test account (that would give you test access only as far as I know) but you should rather create a regular manager account and then apply for a production token on that “production” account if you want to work on a real account.
I would also recommend linking this new production manager account to you existing google ads account before applying so you can justify you request for an API access.
I hope these steps can help you solve. Otherwise please add some more details about what you have done so far so I can help.
Thanks for the reply, my friend. And yes, I filled in all the information, including the developer token. I believe everything is ok, but I don’t know how to make this node work
Thanks for your help, my dear. So does that mean I should request basic access after getting the token?
Exactly @Linecker after getting the test token you should request a basic token.
With this in hand, all you need are the manager and managed account ids, which can easily be obtained from your google ads console.
I am having the same problem as @Linecker but the authentication and the token work (used by another application too)
"httpCode": "400", "description": "Request contains an invalid argument."
Did you get the chance to test the google ads node on your end?
And should we provide Manager Customer ID and Client Customer ID with dashes or without?
My workflow only contains the google ads node, so not receiving input from anywhere - I just want to list the available campaigns.
Thanks and best regards!
Hi @Boris_Idesman, I am afraid I still don’t have access to a fully working Google Ads account as Google doesn’t let me add my test account to my “management” account for some reason. That said, the placeholder values in these fields suggest not to use any dashes:
I see the google ads node got updated with the new release of n8n: Release notes - n8n Documentation
However I still get error, when I try to pull the campaigns - do you know what the issue might be?
NodeApiError: Failed to extend syntax at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:112:23) at processTicksAndRejections (node:internal/process/task_queues:96:5) at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:695:23) at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:585:53