Search Customers: BigCommerce action

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Search Customers support batch operations?

Yes. Run Search Customers inside a Loop node to process arrays. Tiny Command handles BigCommerce's rate limits automatically so you don't have to throttle manually.

More actions