ActionBigCommerceUpdated September 2026
How do I find a BigCommerce customer?
Short answer: You can search customers in BigCommerce by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the BigCommerce Search Customers action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Email (exact) email_in | string | Optional | – |
Limit limit | string | Optional | – |
Sample request
{"email_in": "{{trigger.email_in}}","limit": "{{trigger.limit}}"}
Returns
{"data": [{"id": 42,"email": "jane@acme.com","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 Search Customers.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Search Customers.
What does the Search Customers action do in BigCommerce?
Lookup by partial name, email, company, or customer group. The standard "find before update" pattern for upsert workflows that don't want to create duplicates.
What inputs does Search Customers require?
Search Customers has no required inputs. Sensible defaults are applied if you leave fields blank.
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 Search Customers support batch operations?
Run Search Customers 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.
Action
Create Customer
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.
ActionCreate Product
Creates a new product with name, SKU, price, description, categories, weight, dimensions. For high-volume catalog management, prefer the batch endpoint via HTTP action. Optional variants array for products with size/colour options.
ActionGet Order
Returns the order by ID with customer, line items, totals, status, shipping/billing addresses. The standard lookup for workflows that received an order ID via webhook and need richer detail before fulfilment.
ActionGet Product
Returns a product by ID with all configured fields, current inventory, categories, custom attributes. Useful for "sync product changes to external CDN" or "validate product exists before linking from another tool" workflows.
ActionList Categories
Returns the category tree — each category's name, parent, child count, visibility. Useful for resolving category IDs in product-create workflows or for "audit which categories have stale activity" maintenance.
ActionList Orders
Paginated orders with filters by status, customer, date range, total. The base query for "this morning, list yesterday's orders" daily-summary digests and for backfill workflows that catch orders missed during webhook downtime.