Resources · Make integration

RepairShopr Make integrationAutomate RepairShopr with Make.

What if every new repair ticket, payment or lead in your shop could move on its own? The RepairShopr Make integration gives you 24 modules: 9 triggers, 12 actions and 3 searches. This page shows how to link your account and build a first working scenario, step by step.

Try the RepairShopr integration on MakeSee the 24 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the RepairShopr Make integration automate for you?

The RepairShopr Make integration links your repair shop account to Make, a visual tool where you chain apps together without writing code. Each automation you build there is called a scenario: something happens in RepairShopr, such as a ticket being resolved, and Make carries out the next steps for you, in RepairShopr or in any other app you use.

Tickets that open themselves. A request arrives through a form or an email tool, and Create a Ticket files it in RepairShopr right away. Put Search a Customer in front so the ticket lands on the existing client instead of a duplicate.

A clean handoff when the job is done. Watch Resolved Tickets reacts the moment a technician closes a repair. From there, a scenario can pull the client with Get a Customer and pass the details to your messaging or review tool.

Payments that reach your books. Watch Payments and Watch Invoices send each new record to a spreadsheet or an accounting app, so nobody retypes amounts at the end of the day.

Know the limits before you start: the listed modules cover customers, leads, tickets, invoices and payments. For anything else in the RepairShopr API, Make an API Call reuses the same connection. Make's help page for RepairShopr is AI-generated and may contain mistakes, so check important details with RepairShopr. If you are weighing tools, the n8n vs Make comparison lays out the criteria, the Make review covers the editor in depth, and Make pricing explains how operations are counted.

Connect

How do you connect RepairShopr to Make?

  1. 01

    Copy your API key and subdomain

    Log in to RepairShopr and open your user profile page. The API key is displayed there: copy it. Then note your subdomain, which you can read in your account URL or on the dashboard. Make needs both to reach your shop.

  2. 02

    Add a RepairShopr module in Make

    In your Make account, open a scenario, add any RepairShopr module and click Create a connection. A connection is your RepairShopr account linked to Make once and reused by every RepairShopr module afterward.

  3. 03

    Name it and paste the credentials

    The Connection name field is optional, but a clear name helps if you run several shops. Paste the API key and subdomain you copied, or follow the on-screen instructions, then save.

First scenario

Build your first scenario: web requests become RepairShopr tickets

GoalWhen a customer submits a repair request in your form app, Make finds the client in RepairShopr and opens a ticket on their record.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big +. The first module is the trigger: pick the form or email app where repair requests arrive and connect it.

  2. 02

    Add Search a Customer

    Click the + on the right of the trigger, search RepairShopr and choose Search a Customer. Create your connection, then map the email or name from the form so Make looks up the right client.

  3. 03

    Add Create a Ticket

    Add Create a Ticket after the search. Map the customer returned by the search and the problem described in the form. Each bundle, one request here, becomes one ticket.

  4. 04

    Test with Run once

    Submit a test request, then click Run once. Open the bubbles above each module to read the bundles they received and check the new ticket in RepairShopr.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on, and requests start turning into tickets without anyone copying them.

Triggers

Which RepairShopr triggers can start a scenario?

9 modules start a scenario when something happens in RepairShopr. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by RepairShopr as soon as it happens.

RepairShopr1Watch Customers

Watch Customers

Scheduled trigger

In Make“Triggers when a new customer is created.”

Hands every newly created customer to your scenario, so a welcome message or a CRM record follows each signup without manual export. It suits setups where a small delay is fine and you prefer to control when Make looks.

How it fires
scheduled, Make checks RepairShopr on the scenario's schedule, every 15 minutes by default and never under 15 minutes on the Free plan.
When to use it
syncing new clients to a mailing tool where a few minutes of lag changes nothing.
Watch out
an instant twin exists; pick only one of the two in the same flow or you will process each customer twice.
RepairShopr2Watch Customers (Instant)

Watch Customers (Instant)

Instant trigger

In Make“Triggers when a new customer is created.”

Gets you the new customer the second RepairShopr saves it, which matters when the next step is a greeting or a phone call from the front desk. It also spares your team from refreshing the customer list to spot newcomers.

How it fires
instant, RepairShopr calls Make through a webhook as soon as the customer is created.
When to use it
sending a confirmation SMS while the client is still standing at the counter.
Watch out
click Create a webhook before Create a connection, otherwise the module never receives the call.
RepairShopr3Watch Invoices

Watch Invoices

Instant trigger

In Make“Triggers when a new invoice is created.”

Sends each new invoice to your scenario, which is the cleanest way to feed a spreadsheet, a finance app or a team channel without exporting reports. You work from the invoice as it is created, not from a later summary.

How it fires
instant, RepairShopr calls Make through a webhook as soon as the invoice exists.
When to use it
copying every invoice line into the accounting tool your bookkeeper already uses.
Watch out
it reacts to creation only; a paid invoice is a different event, covered by Watch Payments.
RepairShopr4Watch Leads

Watch Leads

Scheduled trigger

In Make“Triggers when a new lead is created.”

Collects the leads created in RepairShopr so your sales follow-up starts without anyone checking the list. Each new lead becomes one bundle, meaning one item passed to the next module, ready to route to a salesperson or a nurture sequence.

How it fires
scheduled, Make checks RepairShopr on the scenario's schedule and picks up leads added since the previous check.
When to use it
assigning incoming quote requests to whoever handles business accounts.
Watch out
there is no instant version for leads, so plan the schedule around how fast you need to reply.
RepairShopr5Watch Payments

Watch Payments

Instant trigger

In Make“Triggers when a payment is made.”

Tells your scenario the moment a payment is made, so the receipt, the thank-you note or the ledger entry happens while the customer is still in the shop. It is the trigger to choose whenever money received should start something.

How it fires
instant, RepairShopr calls Make through a webhook as soon as the payment is recorded.
When to use it
logging each payment in a shared sheet the owner checks.
Watch out
run a real test payment during Run once; without an event, the webhook sends nothing to inspect.
RepairShopr6Watch Resolved Tickets

Watch Resolved Tickets

Instant trigger

In Make“Triggers when a ticket is marked as "resolved".”

Fires when a ticket is marked as resolved, which turns the end of a repair into the start of your follow-up: pickup notice, satisfaction survey, review request. You react to the finished job itself rather than to any status change.

How it fires
instant, RepairShopr calls Make through a webhook as soon as the ticket switches to resolved.
When to use it
texting the client that their laptop is ready for pickup.
Watch out
if you need other statuses too, Watch Ticket Status covers every change, so avoid stacking both in one flow.
RepairShopr7Watch Tickets

Watch Tickets

Scheduled trigger

In Make“Triggers when a new ticket is created.”

Brings every new ticket into your scenario on a schedule, which keeps a dashboard, a planning sheet or a team channel in step with the workshop. Each ticket arrives as its own bundle, so later modules handle them one at a time.

How it fires
scheduled, Make checks RepairShopr on the scenario's schedule, every 15 minutes by default.
When to use it
building a daily list of open jobs for the technicians where a short lag is acceptable.
Watch out
the instant version fires faster; keep this one when you want each check to count as a predictable run.
RepairShopr8Watch Tickets (Instant)

Watch Tickets (Instant)

Instant trigger

In Make“Triggers when a ticket is created.”

Delivers the new ticket to Make the instant it is created, so the right technician is alerted before the device even reaches the bench. The alert reaches your team without anyone watching the queue.

How it fires
instant, RepairShopr calls Make through a webhook as soon as the ticket is opened.
When to use it
posting urgent repairs to a team chat so someone picks them up right away.
Watch out
do not combine it with the scheduled Watch Tickets on the same data, or each ticket travels through your flow twice.
RepairShopr9Watch Ticket Status

Watch Ticket Status

Instant trigger

In Make“Triggers when a ticket status is changed.”

Follows a ticket through its whole life: every time the status changes, your scenario receives it. That is how you keep a client informed at each stage, waiting for parts, in progress or ready, without writing each update by hand.

How it fires
instant, RepairShopr calls Make through a webhook as soon as the status changes.
When to use it
sending a short update to the customer each time the repair moves forward.
Watch out
it fires on every change, so add a filter after it if only one or two statuses matter to you.
Modules

What can the RepairShopr modules do in a scenario?

RepairShopr gives you 15 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

RepairShopr1

Create a Customer

Action

In Make“Creates a new customer.”

Adds a client to RepairShopr from data captured elsewhere, so a booking form or an online store feeds your customer list directly.

When to use it
a new buyer checks out in your e-shop and should exist in RepairShopr before the device comes in.
Watch out
run Search a Customer first, otherwise returning clients get a second record.
RepairShopr2

Create a Lead

Action

In Make“Creates a new lead.”

Records a prospect in RepairShopr so quote requests from ads, chat or social inboxes land where your team already follows them up.

When to use it
a business asks for a fleet repair quote on your website and you want it tracked as a lead, not a customer yet.
Watch out
leads and customers are separate records; converting one is not done by this module.
RepairShopr3

Create a Ticket

Action

In Make“Creates a new ticket.”

Opens a repair ticket automatically, which removes the retyping step between the channel where the request arrives and your workshop.

When to use it
a form, an email parser or a booking tool captures the problem and the ticket should exist before the client walks in.
Watch out
attach it to the right customer by mapping the result of Search a Customer or Create a Customer placed just before.
RepairShopr4

Delete a Customer

Action

In Make“Deletes an existing customer.”

Removes a customer record from RepairShopr, useful for cleaning up test entries or honoring a deletion request coming from another system.

When to use it
a privacy request is approved in your helpdesk and the client must disappear from the shop's database as well.
Watch out
a deletion cannot be undone from Make, so test it on a dummy record with Run once first.
RepairShopr5

Delete a Ticket

Action

In Make“Deletes an existing ticket.”

Erases a ticket, which keeps the job board clean when requests were opened by mistake or duplicated by another automation.

When to use it
a booking is cancelled in your scheduling tool and the matching ticket should not stay in the queue.
Watch out
nothing brings the ticket back, so feed it the exact ID from Search a Ticket rather than a guess.
RepairShopr6

Get a Customer

Action

In Make“Retrieves information about a customer.”

Fetches the full details of one customer when you already know which one, so later modules can use the phone, email or address stored in RepairShopr.

When to use it
a trigger hands you a ticket and you need the client's contact data to send a pickup message.
Watch out
it needs the customer ID; if you only have a name or an email, use Search a Customer.
RepairShopr7

Get a Lead

Action

In Make“Retrieves information about a lead.”

Reads a single lead in full, handy when a scenario must decide what to do next based on what the prospect asked for.

When to use it
Watch Leads passes an ID and you want every detail before routing the prospect to a salesperson or a nurture tool.
Watch out
without a known ID, Search a Lead is the right module.
RepairShopr8

Get a Ticket

Action

In Make“Retrieves information about a ticket.”

Pulls one ticket with all its information, which lets a message or a report quote exactly what is on the repair order.

When to use it
after Watch Ticket Status fires, you want the complete ticket to write a clear update to the customer.
Watch out
it returns a single ticket by ID; to go through several, use Search a Ticket instead.
RepairShopr9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any part of the RepairShopr API that the listed modules leave out, using the connection you already set up, so you are not stuck when a need falls outside customers, leads and tickets.

When to use it
you need an object or an operation that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the RepairShopr API documentation open beside the editor.
RepairShopr10

Update a Customer

Action

In Make“Updates an existing customer by ID.”

Changes an existing customer by ID, so contact details corrected in another tool stay consistent in RepairShopr without anyone editing twice.

When to use it
a client updates their phone number in your booking app and the shop record should follow.
Watch out
it targets one ID; get it from a trigger or from Search a Customer, never from a name.
RepairShopr11

Update a Lead

Action

In Make“Updates an existing lead.”

Edits a lead already in RepairShopr, keeping the prospect's record current as the conversation moves on in your other tools.

When to use it
a prospect replies to your quote by email and the lead should reflect the new information.
Watch out
find the lead first with Search a Lead, so the change lands on the right person.
RepairShopr12

Update a Ticket

Action

In Make“Updates an existing ticket.”

Modifies an open ticket from outside RepairShopr, which lets parts suppliers, forms or internal tools move a repair along without a technician logging in.

When to use it
a parts order is confirmed in another system and the ticket should show it.
Watch out
changing the status can wake Watch Ticket Status in another scenario, so check you are not creating a loop.
RepairShopr13

Search a Customer

Search

In Make“Finds a customer.”

Looks up clients matching your criteria and returns zero, one or several of them, which is how a scenario checks whether someone already exists before creating anything.

When to use it
just before Create a Customer or Create a Ticket, to reuse the existing record.
Watch out
several matches mean several bundles, and every module after it runs once per result.
RepairShopr14

Search a Lead

Search

In Make“Finds a lead.”

Finds the leads that match what you already know about a prospect and gives back each hit so the scenario can decide between updating and creating.

When to use it
a web form arrives and you want to know if this prospect already asked for a quote.
Watch out
an empty result is normal; plan a route for the case where nothing is found.
RepairShopr15

Search a Ticket

Search

In Make“Finds a ticket.”

Retrieves the tickets that fit your search, which is the way to act on repairs when you do not have their ID at hand.

When to use it
a customer writes about their repair and you want to attach the message to the matching open ticket.
Watch out
it can return many tickets; narrow the search or add a filter before any update or delete.
Need help

Need help automating RepairShopr with Make?

A person reads every message.

FAQ

RepairShopr and Make: frequent questions

01Is the RepairShopr Make integration free?
Yes, on the Make side. RepairShopr is a standard app, available on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution; usage is counted in operations per month. You still need an active RepairShopr subscription, which is priced by RepairShopr itself.
02What do you need to connect RepairShopr to Make?
An active RepairShopr account, your API key and your subdomain. The API key sits on your user profile page once you log in, and the subdomain appears in your account URL or on the dashboard. In Make, add a RepairShopr module, click Create a connection, optionally name it, and paste those two values. For modules tagged instant, click Create a webhook first, then Create a connection. The same connection then serves every RepairShopr module in your scenarios.
03Do RepairShopr triggers in Make react in real time?
It depends on the trigger. Six of them are instant: Watch Customers (Instant), Watch Invoices, Watch Payments, Watch Resolved Tickets, Watch Tickets (Instant) and Watch Ticket Status. RepairShopr calls Make through a webhook as soon as the event happens. Three are scheduled: Watch Customers, Watch Leads and Watch Tickets. Make checks RepairShopr on the scenario's schedule, every 15 minutes by default, with 15 minutes as the minimum on the Free plan and 1 minute on paid plans.
04What if a RepairShopr module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the RepairShopr API with the connection you already created, so you can cover objects the 24 listed modules leave out. You write the request yourself, with the RepairShopr API documentation as a guide. Keep in mind that Make's help page for this app is AI-generated and may contain mistakes, so verify important details directly with the vendor before relying on a scenario in production.
05Should you use Make or n8n for RepairShopr?
It depends on what your team already runs. On Make, RepairShopr comes with 24 ready modules, including 6 instant triggers and Make an API Call for the rest, and it works on the Free plan. The same app often has an n8n node too, so check which tool already hosts your other automations and whether its node covers the tickets, customers or payments you need. Compare the modules available on each side for your exact flow rather than the tool in general.
Same platform

Other docs you might need on this stack.

Browse all integrations