Short answer: Drop the "Google Ads → Add Google Ads Conversion" 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) |
Name name | string | Required | Conversion action name |
Category category | select | Optional | Conversion category |
Default Value value | number | Optional | Default conversion value |
Manager Account ID login_customer_id | string | Optional | MCC manager account ID (optional) |
{"customer_id": "{{trigger.customer_id}}","name": "e.g. Purchase","category": "{{trigger.category}}","value": "{{trigger.value}}","login_customer_id": "{{trigger.login_customer_id}}"}
{"results": [{"resourceName": "customers/1234567890/conversionActions/333"}]}
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.