List Ad Groups: Google Ads action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Customer ID customer_id	string	Required	Google Ads customer ID (no dashes)
Campaign ID campaign_id	string	Optional	Filter ad groups by campaign ID (optional)
Manager Account ID login_customer_id	string	Optional	MCC manager account ID (optional)

Sample request

{
  "customer_id": "{{trigger.customer_id}}",
  "campaign_id": "{{trigger.campaign_id}}",
  "login_customer_id": "{{trigger.login_customer_id}}"
}

Returns

{
  "results": [
    {
      "adGroup": {
        "id": "222",
        "name": "Brand Keywords",
        "status": "ENABLED",
        "resourceName": "customers/1234567890/adGroups/222"
      }
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Ad Groups.

What does the List Ad Groups action do in Google Ads?

Returns paginated ad groups within a campaign with status and performance. For granular performance reporting and for "find underperforming ad groups to pause" optimisation workflows.

What inputs does List Ad Groups require?

Required: Customer ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Google Ads returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Ad Groups support batch operations?

Yes. Run List Ad Groups inside a Loop node to process arrays. Tiny Command handles Google Ads's rate limits automatically so you don't have to throttle manually.

More actions