Short answer: Drop the "Google Ads → Add User to Customer List" 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) |
User List ID user_list_id | string | Required | ID of the customer match user list |
Hashed Email hashed_email | string | Optional | SHA-256 hashed, lowercase email |
Hashed Phone hashed_phone | string | Optional | SHA-256 hashed phone in E.164 format |
Manager Account ID login_customer_id | string | Optional | MCC manager account ID (optional) |
{"customer_id": "{{trigger.customer_id}}","user_list_id": "{{trigger.user_list_id}}","hashed_email": "{{trigger.hashed_email}}","hashed_phone": "{{trigger.hashed_phone}}","login_customer_id": "{{trigger.login_customer_id}}"}
{"resourceName": "customers/1234567890/offlineUserDataJobs/444"}
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.