Webhooks & Integrations

Webhooks allow you to integrate REV23 with other software and services. You can subscribe to specific events in REV23, such as when a customer is created or a release form is generated, and take that data and put it into another app or service.

Examples of things you can do with webhooks include:

• Storing a copy of the signed release form PDF in your preferred cloud storage such as OneDrive, Google Drive, or Dropbox as a backup.

• Send a customer a welcome text message with Twilio when they are created.

• Adding a service to QuickBooks or Square to take a payment.

• Adding a customer email to MailChimp or Constant Contact to automate birthday emails.

Webhooks also allow you to supplement features that aren’t implemented yet, such as emailing aftercare instructions to a customer.

In addition to notifying other apps about events in REV23, you can also respond to events from other apps. Such as:

• Create a customer when a Google Form is filled out

• Create a customer record when a customer books an appointment in a separate online booking app and send them a text message to fill out the online release form.

The possibilities are broad — you could even trigger a robotic mop to clean your station when a session ends.

Zapier (Recommended)

The easiest way to get started with webhooks is through our Zapier integration. Zapier is a no-code automation tool that connects REV23 to thousands of other apps — no programming required. Just pick a REV23 trigger, choose a destination app, and map your fields.

Zapier handles all of the technical details for you: creating and managing webhook subscriptions, receiving payloads, and formatting data for the destination app.

Common Zaps:

• Save release form PDFs to Google Drive or Dropbox
• Add new customers to a MailChimp mailing list
• Send a Slack notification when a session ends
• Create a QuickBooks invoice when a service is completed

Get started with REV23 on Zapier

Custom Webhook Subscriptions

For developers who need more control, you can create webhook subscriptions directly and build your own integrations. This requires writing code to receive and process webhook payloads.

See the Webhooks Technical Guide for full details on creating subscriptions, available events, payload format, signature verification, and delivery behavior.

Note

Custom webhooks are an advanced feature. While we support them, our support team cannot help you design or troubleshoot custom integrations. If you are not sure whether you need custom webhooks, start with Zapier.

Security Considerations

To use webhooks, users require the subscribe:webhook permission (located in Users). Be thoughtful about who has this permission — webhooks can send data to external services whenever events occur in REV23, regardless of the user’s other permissions.

For example, a user with webhook access could set up a webhook that copies customer data to an external spreadsheet or another service whenever a new customer is created. Only grant webhook permissions to users you trust with this level of data access.

Two-way Synchronization Warning

Do not create webhooks that sync data in both directions between REV23 and another app. For example, if you have a webhook that creates a QuickBooks customer when a REV23 customer is created, do not also set up a webhook that creates a REV23 customer when a QuickBooks customer is created. Each app will keep triggering the other in an endless loop, potentially creating thousands of duplicate records and getting your accounts suspended.

Your integrations should be one-way only — REV23 pushes data out, but should not receive data back from the same workflow.