Short answer: You can add google ads conversion in Google Ads by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Google Ads Add Google Ads Conversion action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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.