Short answer: Drop the "BigCommerce → Create 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 |
|---|---|---|---|
First Name first_name | string | Required | Contact's first (given) name. |
Last Name last_name | string | Required | Contact's last (family) name. |
Email email | string | Required | The email address. Used as the recipient or identifier depending on context. |
Phone phone | string | Optional | Phone number in E.164 format (with country code, no spaces). |
Company company | string | Optional | — |
{"first_name": "e.g. Jane","last_name": "e.g. Doe","email": "e.g. user@example.com","phone": "e.g. +14155551234","company": "{{trigger.company}}"}
{"data": [{"id": 42,"email": "jane@acme.com","last_name": "Doe","first_name": "Jane"}]}
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.