Select Google Ads in workflow
Pick Google Ads app in the workflow builder [4] - just one click to select the app.
Triggers can detect changes in Google Ads and run actions that can create, search or modify data inside Google Ads automatically [3] — exactly how you set them.
3 simple steps to make your Google Ads connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
Pick Google Ads app in the workflow builder [4] - just one click to select the app.
When prompted, authorize access to Google Ads in WEXTL once. Google Ads credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your Google Ads account. Approve?
Build your workflow with Google Ads yourself or with WEXTL® AI Builder. Connect Google Ads to any available integrations [5], or use HTTP node to go beyond them.
Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever Google Ads app is called in workflows. That allows your marketing automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that Google Ads supports.
The following table illustrates what fields Google Ads integration require during authorization flow inside our workflow builder [4].
Demonstration of Google Ads connection step inside WEXTL Workflow Builder [4].
| Field | Type | Help |
|---|---|---|
Client IDRequired | text | OAuth 2.0 Client ID from Google Cloud Console → Credentials. Enable the API on the project. |
Client SecretRequired | password | Client secret for the same OAuth client. |
Developer TokenRequired | password | API Center of a Google Ads manager account. Sent as the developer-token header on every call. Explorer Access allows 2,880 production operations per day; Basic Access allows 15,000. |
| Login Customer ID | text | Manager customer ID used when the OAuth user accesses a client through an MCC. Digits only, no dashes. Sent as login-customer-id. Leave empty for a direct account. |
| Additional Scopes | array | Optional. Extra Google OAuth scopes to request on top of the default ones, one full scope URL per item (for example https://www.googleapis.com/auth/drive). Duplicates of the default scopes are ignored. Use this with your own Client ID, and enable the same scopes on its OAuth consent screen. |
Enter a name of the other app you want to sync with Google Ads below. Click on selected app to explore integration options with Google Ads. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.
Select Watch New Campaigns trigger from Google Ads - this will be a starting point in your automation. Whenever event happens in Google Ads, workflow will start [7] from Watch New Campaigns node.
Search for Create Campaign Bid Modifier, connect it as the next step of integration sequence. You can use filters between Watch New Campaigns and Create Campaign Bid Modifier, so only important data pass from Watch New Campaigns to the next step. WEXTL gives you full control over the process of Google Ads automation. All parts of workflow are visible on the canvas [4].
Google Ads on WEXTL has 129 modules for combining marketing automations. Explore Google Ads documentation for more.
Demonstration of how visual Google Ads automation [6] looks in WEXTL.
Common questions about automating Google Ads in your workflows.
List of sources used to gather information about the Google Ads integration.