Google Ads Campaigns

The Google Ads Campaigns input node lets the runner pick a Google Ads customer and one or several campaigns when launching the workflow.

What does the Google Ads Campaigns node do?

The Google Ads Campaigns input node lets the person running the workflow select a Google Ads customer and one or several campaigns at runtime. Instead of hardcoding a customer ID and campaign IDs in the Google Ads tool node settings, this node creates a runtime selector — the runner picks which account and campaigns to query each time the workflow is launched.

Common use cases:

• Build reusable Google Ads reporting workflows where each runner targets their own MCC sub-account.
• Run the same campaign analysis on multiple campaigns without duplicating workflows.
• Let team members report on their own accounts and campaigns through a single shared workflow.
• Map customer IDs and campaign IDs from CSV columns to run a batch of reports in one go.

Quick setup

Follow these steps to add and configure the Google Ads Campaigns input node in your workflow:

Configuration parameters

The node has no required text fields — the runtime selection (customer + campaign) is what fills its outputs. Settings only control the runtime UI behavior.

Required fields

Optional fields

What does the node output?

The node exposes three string outputs that connect into the Google Ads Campaign Reports tool node.

How to use the output

In Draft & Goal you don’t need to look up a complex system-generated variable name. To use the result:

1. Draw a connection from each Google Ads Campaigns output handle (customer_id, campaign_ids, integration_id).
2. Connect each one to the matching input on the Google Ads Campaign Reports node.
3. Toggle Use variables for customer ID and campaign IDs on the receiving node so it reads from the connected inputs instead of its own settings.

Usage examples

Example 1: Single-campaign report at runtime

The runner picks an integration, a customer, and a single campaign. The Google Ads Campaign Reports tool produces a JSON report for that campaign.

Configuration:

• Allow Multiple = false
• required = true
• Fixed integration = (empty — runner picks at runtime)

Workflow shape:

[Google Ads Campaigns input]  →  [Google Ads Campaign Reports]  →  [LLM Insights]

Example 2: Multi-campaign report in batch mode

A CSV ships one row per (customer, campaign) pair. In step 3 (Mapping) you map the Customer ID column and the Campaign IDs column to the input node. Each row triggers a Google Ads Campaign Reports call against the corresponding customer + campaign(s).

Configuration:

• Allow Multiple = true
• Fixed integration = <a specific Google Ads integration> (required in batch mode)

Mapping:

• CSV column customer_id → node output customer_id
• CSV column campaign_ids → node output campaign_ids (comma-separated when several IDs per row)

Common issues

The runner sees a 'Select a customer' dropdown but the list is empty

Cause: The Google Ads integration the runner picked has no accessible customer.

Solution: Verify the OAuth scopes and that the integration owner is granted access to at least one Google Ads MCC or sub-account.

Campaign list stays empty after picking a customer

Cause: The selected customer has no campaigns matching the API filter.

Solution: Pick another customer, or check directly in the Google Ads UI that the account has active campaigns.

Validation error 'Customer ID is required' when launching a run

Cause: The runner picked a customer but didn’t pick any campaign. Both are required — the form value is only complete once at least one campaign is selected.

Solution: Pick at least one campaign, or disable Required in the node settings if downstream nodes can handle a missing value.

Batch run fails to authenticate against Google Ads

Cause: No fixed integration set on the input node while running in CSV/batch mode. Without it, the runner cannot determine which Google Ads account owns the customer ID read from the column.

Solution: Open the node settings, enable Fixed integration, and select the Google Ads integration to use for the whole batch.

Best practices and pitfalls

How does it fit into a workflow?

Google Ads Campaigns acts as the runtime entry point that feeds the Google Ads Campaign Reports tool — turning a hardcoded report into a parametrized one the runner controls.

graph LR
    Input[Google Ads Campaigns input] --> Reports[Google Ads Campaign Reports]
    Reports --> LLM[LLM Insights]
    LLM --> Output[Sheets / Slides / Email]

Related nodes