Create a RepairShopr Ticket
This guide explains how to use the Arigato action to create a new repair ticket in RepairShopr, linked to an existing customer. This action is the typical final step in a Shopify-to-RepairShopr workflow: once you have a RepairShopr customer ID (from Find or Create a RepairShopr Customer, for example), this action opens a ticket on that customer’s record with subject, ticket type, problem type, status, an initial comment, and any custom ticket fields configured in your RepairShopr account.
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 |
|---|---|---|
| Customer ID | Required. RepairShopr customer ID. Use the response.customer_id output token from a Find or Create Customer action. |
{{ response.customer_id }} |
| Subject (Ticket Title) | Required. Brief description of the repair issue. Supports Twig tokens. RepairShopr’s intake form calls this Subject; the admin ticket detail view calls it Ticket Title — same field. | {{ object.name }} — repair line item |
| Ticket Type | Optional. Configure ticket types in your RepairShopr account under Admin → Tickets → Ticket Types. The dropdown loads from your account configuration. | Repair Job |
| Problem Type | Optional. Configure problem types in your RepairShopr account under Admin → Tickets → Problem Types. | Hardware |
| Status | Ticket status. Defaults to New. Configure statuses in your RepairShopr account under Admin → Tickets → Workflows. | New |
| Custom Ticket Fields | Optional. A repeater of field-name / value pairs. The field-name dropdown is populated from Admin → Tickets → Ticket Types in RepairShopr. Each value supports Twig tokens. Field types popup and scribble are not supported and are hidden from the dropdown. |
Field Order URL = {{ object.order_status_url }} |
| Initial Comment | Optional. Becomes the initial comment on the ticket — same field as Complete issue details in the RepairShopr intake form. Supports Twig tokens. Authored as “Arigato Automation” in the comments view. | Repair requested from Shopify order {{ object.name }} ({{ object.line_items[0].title }}). |
Output Tokens
| Token | Description |
|---|---|
response.ticket_id |
The new ticket’s RepairShopr ID. |
response.ticket_url |
Direct link to the ticket in RepairShopr (https://<subdomain>.repairshopr.com/tickets/<id>). |
Example Configuration
Open a repair ticket whenever a Shopify order contains a “repair” line item, chained off a Find or Create Customer step earlier in the workflow:
- Customer ID:
{{ response.customer_id }} - Subject (Ticket Title):
{{ object.name }} — {{ object.line_items[0].title }} - Ticket Type: Repair Job
- Status: New
- Custom Ticket Fields: Order URL =
{{ object.order_status_url }} - Initial Comment:
Repair requested via Shopify order {{ object.name }}. Customer notes: {{ object.note }}.
Troubleshooting & Usage Tips
Dropdowns (Ticket Type, Problem Type, Status, Custom Fields) are empty. These dropdowns load from your RepairShopr account configuration. Empty dropdowns usually mean Arigato can’t reach RepairShopr — verify the API token is still valid. The form still saves with empty dropdowns; you just can’t pick configured options.
A previously-selected option shows “(not in current list)”. The option was deleted in RepairShopr after the 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 it.
Changes I made in RepairShopr aren’t showing up. Ticket Type, Problem Type, Status, and Custom Field options are cached for one hour after they first load. Wait up to an hour for the dropdowns to refresh.
The initial comment isn’t appearing on the ticket in RepairShopr. Confirm the Initial Comment field has rendered content (an empty field produces no comment). The comment is authored as “Arigato Automation” in the RepairShopr comments view — check for it under that author.
I can’t find my custom field in the dropdown. Field types popup and scribble are unsupported and intentionally hidden. popup’s UX doesn’t fit a workflow value, and scribble captures a freehand signature that can’t be produced from tokens. Reconfigure the field as text_field or text_area in RepairShopr if you need to write to it from a workflow.
The customer_id is invalid (status code 422 or 404). The Customer ID field expects the numeric ID from RepairShopr, not a Shopify customer ID or email. Chain this action after a Find or Create Customer step and use its response.customer_id output token.
Credit Cost
Create a RepairShopr Ticket incurs a cost of one Action Credit on Lite plans and is unlimited on Unlimited plans.
Custom Actions
This action is the typical final step in any Shopify-to-RepairShopr handoff, such as:
- Auto-creating a repair ticket whenever a Shopify order contains a specific product (a repair SKU, an extended-warranty add-on, etc.).
- Opening an internal ticket when a customer hits a return or complaint flag in Shopify, with the order details copied into the initial comment for technician context.
- Populating SLA or priority data into custom ticket fields so your RepairShopr workflow can prioritize tickets by Shopify subscription tier or B2B status.