ActionBigCommerceUpdated September 2026

How do I create a BigCommerce customer?

Short answer: You can create customer in BigCommerce by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the BigCommerce Create Customer 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.

Create Customer in BigCommerce — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
First Name
first_name
stringRequiredContact's first (given) name.
Last Name
last_name
stringRequiredContact's last (family) name.
Email
email
stringRequiredThe email address. Used as the recipient or identifier depending on context.
Phone
phone
stringOptionalPhone number in E.164 format (with country code, no spaces).
Company
company
stringOptional
Sample request
{
"first_name": "e.g. Jane",
"last_name": "e.g. Doe",
"email": "e.g. user@example.com",
"phone": "e.g. +14155551234",
"company": "{{trigger.company}}"
}
Returns
{
"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.

Triggered by

Apps that pair well as the trigger for Create Customer.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Create Customer.

What does the Create Customer action do in BigCommerce?
Creates a new customer in BigCommerce with email (dedupe key), name, addresses, customer group. Useful for "B2B account provisioning from CRM → BigCommerce" workflows where pre-creating customers gates self-serve checkout.
What inputs does Create Customer require?
Required: First Name, Last Name, Email. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if BigCommerce returns an error?
The run history shows the failed step with its input and the error message BigCommerce returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Create Customer support batch operations?
Run Create Customer inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within BigCommerce's rate limits.
More actions

Other BigCommerce actions.

Create Customer in BigCommerce — start free