Short answer: Drop the "Google Ads → Pause Google Ads Campaign" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 | Required | Campaign ID to pause |
Manager Account ID login_customer_id | string | Optional | MCC manager account ID if accessing via manager (optional) |
{"customer_id": "e.g. 1234567890","campaign_id": "{{trigger.campaign_id}}","login_customer_id": "{{trigger.login_customer_id}}"}
{"results": [{"resourceName": "customers/1234567890/campaigns/111"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.