Get Customer by Email in RepairShopr
This guide explains how to use the Arigato action to look up a customer in RepairShopr by email address. This action is helpful when you only need to confirm whether a customer already exists in RepairShopr — for example, to gate downstream actions on whether the customer is new or returning. It does not create a customer when none is found; for the lookup-then-create pattern, use Find or Create a RepairShopr Customer.
Configuring the Action
Before using this action, you must connect your RepairShopr account through the Arigato Integrations page. See the RepairShopr Integration guide for setup.
| Field Name | Description | Example |
|---|---|---|
| Email address to look up in RepairShopr. Required. Supports Twig tokens. | {{ customer.email }} |
Output Tokens
The action populates these tokens for use in downstream actions:
| Token | Description |
|---|---|
response.customer_id |
The matched customer’s RepairShopr ID, or null when no customer was found. |
response.customer_name |
The matched customer’s full name, or null when not found. |
response.found |
true when a customer with the exact email exists; false otherwise. |
Example Configuration
Look up the customer attached to the triggering Shopify order:
- Email:
{{ object.customer.email }}
You can then branch on {{ response.found }} in a downstream condition — for example, only run a welcome workflow when the customer is new to RepairShopr.
Troubleshooting & Usage Tips
The action reports “not found” for a customer you know exists. Email matching is case-insensitive but requires an exact match after trimming. A substring hit like jane@example.com against a stored jane@example.com.au is intentionally rejected, because matching by substring would put the wrong customer’s ID into downstream actions.
The action errors with “Email cannot be blank.” The rendered email value is empty. Check the Twig token you’re using — on some triggers (e.g. cart abandonment for a guest checkout), object.customer.email can be null.
I want to create the customer if none exists. Use Find or Create a RepairShopr Customer instead — it runs the same email lookup and falls back to creating the customer when none is found.
Credit Cost
Get Customer by Email in RepairShopr incurs a cost of one Action Credit on Lite plans and is unlimited on Unlimited plans.
Custom Actions
This action can be used in any custom workflow where branching on customer existence matters, such as:
- Skipping a “welcome to repair services” comms blast when the customer already has a RepairShopr record.
- Tagging Shopify customers with their RepairShopr status (existing / new) for segmentation.
- Routing a ticket-creation step to use the existing customer’s ID instead of always creating fresh.
Use the response.found token in a downstream condition to fork your workflow on the lookup result.