Short answer: Drop the "Shopify → Update Customer" 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 | Shopify customer ID — numeric. Find via List Customers. |
Email email | string | Optional | Email. e.g. "customer@example.com" |
First Name first_name | string | Optional | Contact's first (given) name. |
Last Name last_name | string | Optional | Contact's last (family) name. |
Phone phone | string | Optional | Phone. e.g. "+15551234567" |
Tags tags | string | Optional | Comma-separated tags (replaces existing) |
Note note | string | Optional | Internal note about the customer |
{"customer_id": "e.g. 456789012","email": "customer@example.com","first_name": "e.g. Jane","last_name": "e.g. Doe","phone": "+15551234567"}
{"customer": {"id": 456,"tags": "VIP, wholesale","email": "customer@example.com","last_name": "Doe","first_name": "John"}}
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.