IntegracionesIncluido en todos los planesMejorado en la v3.1.1

Connect to thousands
of apps.

Send booking data to Zapier, Pabbly Connect, Make, or any automation platform, automatically, the moment something happens.

Get started Book a demo

trigger events

platforms documented

data sections per event

Webhook deliveries · today

4 of 8 triggers active

Live

MethodEndpointTriggerStatus

POST

hooks.zapier.com/hooks/catch/8…

09:14:18

appointment.created200

POST

connect.pabbly.com/workflow/2…

09:13:02

quote.created200

POST

hook.eu1.make.com/abx9p2…

09:08:41

appointment.updated200

POST

hooks.zapier.com/hooks/catch/8…

09:02:11

appointment.cancelled202

Zapier

2 hooks

Pabbly

1 hook

Make

1 hook

Last delivery

200 OK

142 ms

Why repair shops choose it

One feature. Unlimited automations.

Webhooks turn RepairPlugin into the trigger for everything else: CRMs, accounting, SMS, spreadsheets, anything that listens on an HTTP endpoint.

8 triggers

appointment.created

appointment.updated

appointment.cancelled

appointment.deleted

quote.created

quote.updated

quote.cancelled

quote.deleted

12triggers

Every important event covered

Choose from 12 triggers covering the full lifecycle: scheduled appointments, ship-device appointments, and PDF offers, each with created, updated, cancelled, and deleted events. Each trigger sends a complete data package the moment the event happens.

payload · 11 sections

{

"action": {…},

"timing": {…},

"service & payment": {…},

"appointment": {…},

"customer": {…},

"location": {…},

"device": {…},

"items": {…},

"financials": {…},

"payment": {…},

"action_links": {…},

}

11data sections

Complete booking data in every payload

Every webhook sends 11 data sections: action, timing, service & payment, appointment details, customer information, location, device, items, financials, payment, and action links for rescheduling, approving, finalizing, or cancelling.

Documented platforms

ZZapier5,000+ apps

PPabbly Connect1,000+ apps

MMake1,500+ apps

+ any HTTP POST endpoint

3platforms

Works with any automation platform

Step-by-step setup guides for Zapier, Pabbly Connect, and Make are included. Any platform that accepts an HTTP POST with a JSON body and Content-Type: application/json header works, connect to your CRM, accounting software, SMS service, or spreadsheets.

Scope per location

Amsterdamappointment.createdactive

Rotterdamquote.createdactive

All locationsappointment.cancelledactive

Utrechtquote.updateddisabled

Per locationscoping

Location-scoped webhooks

With Enhanced Locations, scope webhooks to a specific location so each shop triggers its own automations. Webhooks set to 'All' fire for events at any location. If Enhanced Locations is deactivated, location-specific webhooks show a 'Disabled' badge.

Example payload

"booking_id": "RP-8421",

"customer": {…}

ExamplePayload button

Preview the data before you build

Click the Example Payload button next to any webhook to view the full JSON data structure that would be sent for that trigger. Use this preview to map fields in your automation platform without having to fire a real test event first.

Supplier fieldsGrowth+

supplier_namePartsHub

product_codeIP14P-SCR-A

cost_price€118.95

Per item · ideal for purchase orders

Supplier fieldson Growth & Scale

Dynamic Pricing supplier data

On Dynamic Pricing Growth or Scale plans, each item in the payload also includes supplier name, product code, and supplier cost price, ideal for syncing purchase orders or reseller workflows. On the Essentials plan, these fields aren't included.

How it works

Four steps to your first automation.

Create a webhook in RepairPlugin, set up the matching trigger in your automation platform, verify the payload, then build out your actions.

Step 1 · create

Trigger

appointment.created

URL

hooks.zapier.com/…

Location

Amsterdam

Create a webhook

Go to Settings > Webhooks & Integrations > Webhooks. Click Create New, select a trigger event, paste your automation platform's webhook URL, and (with Enhanced Locations) optionally pick a location.

Step 2 · platform

Zapierwebhook URL

Pabbly Connect

Make

Set up your automation platform

In Zapier, Pabbly, or Make, create a workflow with a Webhook trigger and copy the generated URL into the RepairPlugin webhook. The receiving platform's setup is your responsibility, RepairPlugin handles the sending side.

Step 3 · inspect

POST /webhook

200 OK · 142 ms

Payload received

Test and inspect the payload

Trigger a real booking to fire the webhook, then verify the data was received. Click Example Payload in RepairPlugin to compare the structure, or use a service like webhook.site to inspect exactly what your endpoint receives.

Step 4 · build

Come by storeConfirm SMS

Ship deviceShipping label

PickupSchedule courier

On-locationAlert tech

Build your actions

Use the received data to create invoices, send SMS notifications, update your CRM, or assign tasks. Route actions by service method (come by store, ship, pickup, on-location) using Filters in Zapier, Router steps in Pabbly, or Router modules in Make.

Plan availability

Included on every plan.

Webhooks ship with Essentials. Location scoping unlocks with Enhanced Locations on Scale. Supplier fields require Dynamic Pricing on Growth or Scale.

EssentialsIncluido

All 12 triggers, single location stream

GrowthIncluido

+ supplier fields per item

ScaleIncluido

+ per-location scoping

FAQ

Preguntas frecuentes.

Can I create multiple webhooks for the same trigger?

Yes. You can create as many webhooks as you need. For example, send 'Scheduled Appointment Created' to both Zapier (for your CRM) and Pabbly (for SMS notifications) at the same time.

Does RepairPlugin retry failed webhook deliveries?

No. Each webhook is sent once with a 4-second timeout. If the receiving server is unreachable or returns an error, the delivery is lost. Use a middleware service like Zapier or Make that handles retries on your behalf.

What format does the webhook use?

RepairPlugin sends webhooks as an HTTP POST request with a JSON body and a Content-Type: application/json header. This format works with virtually every automation platform and custom endpoint.

Can I send a test webhook?

There is no 'test send' button. You can view an example payload for each trigger in the admin panel, but to test actual delivery you need to create a real booking. Tip: use a service like webhook.site to inspect the payload your endpoint receives.

Does RepairPlugin help me set up Zapier, Pabbly, or Make?

RepairPlugin handles the webhook side, creating webhooks, selecting triggers, and sending data. Setting up the receiving side in your automation platform is your responsibility, and RepairPlugin doesn't provide support for configuring third-party platforms.

Can I scope webhooks to a single shop location?

Yes, with Enhanced Locations active. The Location dropdown lets you pick a specific location or leave it as 'All'. If Enhanced Locations is deactivated after location-specific webhooks were created, those webhooks show a 'Disabled' badge until it's reactivated.

What customer data is included in the payload?

Customer Information includes first name, last name, full name, email, phone, full address (house number, street, city, zipcode, country), customer type (private or business), business name, and notes, everything you need to populate a CRM record.

Can I use webhooks to route actions by service method?

Yes. The payload includes the service method, so you can branch your automation: send a store visit confirmation for 'Come by our store', generate a shipping label for 'Ship device', schedule logistics for 'Pickup service', or alert a field tech for 'Repair on your location'.

Documentación

Lea la guía completa.

Setup, the full trigger reference, every field in the payload, and platform-specific guides for Zapier, Pabbly, and Make, straight from the help centre.

Ver la documentación

Temas populares