Skip to content
For LLMsView as Markdown·

Google Ads ​

undefined

DetailValue
CategoryMarketing
Base URLhttps://googleads.googleapis.com/v20
AuthenticationOAuth2
Endpoints6
Connector keygoogle-ads

Using Google Ads in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick Google Ads from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints ​

EndpointSummary
GET Campaigns
GET Ad Groups
GET Ads
GET Keywords
GET Budgets
GET Reporting

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET ​

Campaigns

DetailValue
Operation IDcampaigns_0
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Google Ads connection from the Connection dropdown.
  3. In the Operation dropdown, select campaigns_0.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Ads API reference.

GET ​

Ad Groups

DetailValue
Operation IDad_groups_1
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Google Ads connection from the Connection dropdown.
  3. In the Operation dropdown, select ad_groups_1.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Ads API reference.

GET ​

Ads

DetailValue
Operation IDads_2
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Google Ads connection from the Connection dropdown.
  3. In the Operation dropdown, select ads_2.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Ads API reference.

GET ​

Keywords

DetailValue
Operation IDkeywords_3
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Google Ads connection from the Connection dropdown.
  3. In the Operation dropdown, select keywords_3.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Ads API reference.

GET ​

Budgets

DetailValue
Operation IDbudgets_4
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Google Ads connection from the Connection dropdown.
  3. In the Operation dropdown, select budgets_4.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Ads API reference.

GET ​

Reporting

DetailValue
Operation IDreporting_5
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Google Ads connection from the Connection dropdown.
  3. In the Operation dropdown, select reporting_5.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Ads API reference.