Stream real-time contact, deal, SMS, call, AI agent, booking, and task events from Revamp365 to Zapier, Make, your CRM, or any URL that accepts POST requests. A destination is a single endpoint plus the events you want it to receive.
Open the Send Data tab
- Go to Integrations & Apps from the main navigation.
- Open the Webhooks card ("Send CRM events to HTTPS endpoints").
- You land on the Send Data tab, which lists every destination you have configured.
Webhooks are a paid feature, so a Free plan is redirected away from this page.
Add a destination
- Click Add destination in the top right.
- Enter the URL that should receive the events (for example
https://hooks.zapier.com/...). It must be a valid, publicly reachable HTTPS address. - Enter an optional Label (such as "My Zapier Hook") so you can recognize it later.
- Select at least one event. See choosing which events to send for the full catalog and filters.
- Click Create.
Save your signing secret
When the destination is created, Revamp365 shows a signing secret once. Copy it immediately with the Copy button.
- Every delivery includes an
X-Webhook-Signatureheader, an HMAC-SHA256 hash of the JSON body keyed with this secret. - Your receiver uses the secret to confirm the request genuinely came from Revamp365. See verify outbound webhook HMAC signatures.
- You can reveal the secret again later with the eye icon on the destination card.
Limits and behavior
| Detail | Value |
|---|---|
| Destinations per account | 10 maximum |
| URL length | Up to 2,048 characters |
| Events per destination | 1 to 50 |
| Request method | POST with Content-Type: application/json |
| Signature header | X-Webhook-Signature (HMAC-SHA256) |
| Delivery timeout | 15 seconds |
| Retries | None — each event is attempted once |
Because there are no automatic retries, your endpoint should return a 2xx status quickly. Private, internal, and reserved IP addresses are rejected for security, so localhost and LAN URLs will not deliver.
Manage existing destinations
Each card on the Send Data tab gives you controls to:
- Toggle Active/Inactive — a new destination is Active by default; an Inactive one stops receiving events without being deleted.
- Edit — change the URL, label, selected events, or payload options.
- Delete — remove the destination. Existing delivery logs are kept.
After your first events fire, open the delivery logs to confirm each POST returned a success status and to inspect the exact payload your endpoint received.