RepairShopr Integration

The RepairShopr integration allows you to create and look up customers, and create repair tickets, directly from your Arigato workflows. This is ideal for repair shops, electronics retailers, and service businesses that fulfill Shopify orders through a RepairShopr ticket system — automate the handoff from Shopify checkout to your repair queue without manual data entry.

Configuring the Integration

  1. Navigate to the Integrations page in the Arigato app.
  2. Click the RepairShopr card.
  3. Enter your RepairShopr subdomain. If your RepairShopr URL is https://yourshop.repairshopr.com, enter yourshop.
  4. Enter your RepairShopr API key. Generate one in your RepairShopr admin under Admin → API → Add a New API Token. The token needs read + write access to customers and tickets.
  5. Click Save Credentials.
  6. Click Test Connection to verify Arigato can reach RepairShopr with the credentials you provided.

Once connected, you’ll be able to use RepairShopr actions in your Arigato automations.

Available Actions

Action Description
Get Customer by Email in RepairShopr Look up a customer in RepairShopr by email address. Returns the customer’s ID, name, and a found flag your downstream actions can branch on. Does not create a customer when none is found — “not found” is a successful outcome.
Create Customer in RepairShopr Create a new customer record in RepairShopr directly, without first checking for an existing customer. Recommended only when you’ve already confirmed the customer doesn’t exist (RepairShopr enforces email uniqueness, so a duplicate email will fail).
Find or Create a RepairShopr Customer Look up a customer by email, phone, mobile, or business name + first/last name, falling back to creating a new customer when no match exists. The recommended customer action for most workflows.
Create a RepairShopr Ticket Create a new repair ticket linked to an existing RepairShopr customer. Supports ticket type, problem type, status, an initial comment, and custom ticket fields configured in your RepairShopr account.

Credit Costs

Each RepairShopr action costs one Action Credit on Lite plans. Unlimited plan users can use RepairShopr actions without any credit limits.

Limitations

  • Customers are matched by email using a case-insensitive exact match — substring hits like jane@example.com against a stored jane@example.com.au are rejected. For the Find or Create action, phone, mobile, and business name are used as fallback match signals when email doesn’t hit.
  • Initial ticket comments are authored by “Arigato Automation” in the RepairShopr comments view, not the merchant’s RepairShopr user account.
  • Custom ticket field types popup and scribble are not supported and are hidden from the Custom Field dropdown on the Create Ticket action.
  • The Ticket Type, Problem Type, Status, and Custom Field options on the Create Ticket action are cached for one hour after they first load. Changes made in RepairShopr (adding a new ticket type, renaming a status, etc.) can take up to an hour to appear in Arigato.

Troubleshooting

The integration won’t connect. Verify the subdomain matches your RepairShopr URL — for https://yourshop.repairshopr.com, the subdomain is yourshop (no https://, no .repairshopr.com). Confirm your API token is active in RepairShopr and has read + write access to both customers and tickets.

Dropdowns are empty on the Create a RepairShopr Ticket action. The Ticket Type, Problem Type, Status, and Custom Field dropdowns load from your RepairShopr account configuration. If they’re empty, Arigato likely can’t reach RepairShopr — check that your API key is still valid and hasn’t been revoked. The form will still save with empty dropdowns; you just won’t see the configured options.

An action log shows “Failed to authenticate account” with status code 401. Your RepairShopr API token has been revoked or rotated. Regenerate the token in RepairShopr and update it on the Arigato integration page.

The Create Customer action fails with “Email has already been taken” (status code 422). RepairShopr enforces email uniqueness server-side. Switch to the Find or Create a RepairShopr Customer action — it handles the lookup-then-create pattern automatically and won’t fail on duplicate emails.

A previously-selected Ticket Type, Problem Type, or Status shows “(not in current list)”. The option was deleted in RepairShopr after your workflow was saved. The form preserves the stored value with that suffix so edits don’t silently drop it. Pick a new option from the current list if you want to update.

Example Use Cases

  • Auto-create a RepairShopr ticket whenever a Shopify order contains a “repair” line item, with the order details copied into the initial ticket comment so your technician has the context they need.
  • When a Shopify customer is created or placed on a B2B account, ensure they exist in RepairShopr ahead of time — Find or Create a RepairShopr Customer can run on the customer-created trigger so the record is ready before they walk in with a device.
  • For service-contract workflows: tag the ticket with the customer’s Shopify subscription tier via the Custom Fields repeater, so your team can prioritize SLA-bound customers in the RepairShopr ticket queue.