Webhooks & Integrations

Webhooks push REV23 events to other software. Subscribe to an event, like a customer being created or a release form being generated, and REV23 sends the data to your endpoint as the event happens.

A few things studios do with webhooks:

• Store a copy of every signed release form PDF in OneDrive, Google Drive, or Dropbox as a backup.

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

• Create a bookkeeping entry in QuickBooks when a service is completed.

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

• Post a Slack message when a booking is approved or a no-show is recorded.

Webhooks also extend REV23 into tools you already run your business on — like tracking loyalty points in your own spreadsheet.

In addition to notifying other apps about events in REV23, a supported API-key integration can submit custom intake into REV23. For example:

• Create a customer and Idea when a consultation form on your website is submitted.

After intake, continue booking, appointment, release-form, payment, and other operational workflows on REV23-provided pages. API keys are not intended to recreate those workflows on another website. See API Keys for the supported boundary.

For other data, prefer one-way automation that sends changes from REV23 to the connected app.

Zapier

The REV23 Zapier integration is the recommended starting point. Zapier is a no-code automation tool that connects REV23 to thousands of other apps: pick a REV23 trigger, choose a destination app, and map your fields. Zapier creates and manages the webhook subscription, receives the payloads, and formats the 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. They are supported, but REV23 Support cannot help design or troubleshoot custom integrations. If you are not sure whether you need custom webhooks, start with Zapier.

Keep integrations one-way

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.

Permissions

Creating webhook subscriptions takes Webhooks → Subscribe — no role includes it; the owner grants it deliberately. A user with this permission can send data to external services whenever events occur in REV23, regardless of their other permissions — for example, copying customer data to an external spreadsheet whenever a customer is created. Grant it only to users you trust with that level of data access. See Roles & Permissions.