Webhooks

Send real-time event data from Volume Reach to any external system the moment something happens.

Overview

Webhooks are automatic notifications that Volume Reach sends to a URL you provide whenever a specific event occurs — a call completes, a contact replies to a text, a text fails to deliver, and more. External tools like your CRM, Zapier, Make, or custom applications receive this data instantly, keeping everything in sync without manual exports.

Webhooks require the CRM add-on ($50/mo).

Setting Up a Webhook

Step 1: Open Webhook Settings

1. Go to Automation in the left sidebar.
2. Select Webhooks.
3. Click Add Webhook.

Step 2: Enter Your Webhook URL

Paste the destination URL where Volume Reach should send event data. This is typically provided by your external tool (for example, Zapier gives you a "Webhook URL" when you create a Zap).

Step 3: Choose What to Send (on the Triggers page)

A webhook doesn't send anything until a trigger points at it. Go to Automation, then Triggers, and click Add Trigger. Under When this happens, pick an event, then pick this webhook. Make one trigger per event you want, for example one for Reply Received and one for Text Failed.

Only Call Completed supports narrowing by outcome — the other events fire on every match with no filter.

Step 4: Save and Test

Click Save, then use the Send Test Event button to fire a sample payload to your URL. Check your external system to confirm it received the data correctly.

Preview payloads

Before wiring up your CRM, you usually want to see the exact JSON shape Volume Reach will send. Click Preview payloads in the Webhooks page header to open the payload viewer — a side-sheet with one tab per event type.

Available event types in the preview:

• call.completed
• sms.received
• sms.delivered
• sms.failed
• lead.qualified

Each tab shows a synthetic JSON payload with the same envelope and field shape Volume Reach uses in production. IDs and timestamps are placeholders; real deliveries include your tenant's actual lead and call data. Click Copy in the viewer header to grab the JSON for your CRM development environment.

Use this when:

• Setting up a new CRM integration and you need to map fields without firing a real delivery
• Onboarding a developer who needs the schema reference
• Sanity-checking the shape before flipping a webhook to active

Recent deliveries

Each webhook endpoint card has a Recent deliveries icon (the scroll-text icon, next to Test and Edit). Click it to see the last 50 delivery attempts for that endpoint in a side-sheet.

The deliveries panel shows:

• Status icon — ✓ delivered (HTTP 2xx) / ⏱ pending or retrying / ⚠ failed
• Event type badge (e.g., lead.qualified, call.completed)
• HTTP status code (e.g., 200, 404, 500)
• Attempt count — how many retries Volume Reach has made
• Last attempt timestamp in mono font for quick comparison
• Error message preview — for failed deliveries. Long errors (e.g., stack traces) collapse with a "Show full error" toggle so one bloated row can't dominate the panel.

A date filter at the top lets you scope to 1 day, 7 days, 30 days, or all time. Default is 7 days.

Use this when:

• A tenant asks "did my webhook arrive?" — open the sheet, scope to the last 24h, scan the status icons
• Triaging an integration that suddenly stopped working — failed deliveries surface immediately
• Confirming your endpoint is returning 2xx on Volume Reach's side after deploying a fix to your end

The data is also available in the broader Delivery Logs view across all endpoints; the per-endpoint sheet is the fastest path when you already know which webhook you're debugging.

Managing Webhooks

• Pause a webhook: Toggle the active switch off. Events will not be sent while paused, but the configuration is saved.
• Edit a webhook: Click the webhook name to modify the URL or selected events.
• Delete a webhook: Click the trash icon. Deletion is permanent — any in-flight deliveries may still complete.

Delivery and Retries

Volume Reach expects your endpoint to respond with an HTTP 2xx status within 10 seconds. If the delivery fails or times out, Volume Reach retries automatically with increasing delays — up to 6 attempts spread out over about a day — before giving up and marking the delivery failed.

You can review the status of every delivery attempt in the per-endpoint Recent deliveries sheet (above) or the broader Delivery Logs view. Two messages you may see there:

• "Waiting: more updates arrived in one minute than we send at once. Sending in a few minutes." — a lot of events landed for your account at once (for example, a large text blast). Nothing is wrong; these are queued and sent within a few minutes.
• "Not sent: your endpoint wasn't responding a moment ago. We'll retry automatically." — your endpoint timed out, refused the connection, or returned an error a moment ago, so Volume Reach is giving it a short break before trying again. If this keeps happening, check that your endpoint is online and responding within 10 seconds.

Tips for Reliable Webhooks

• Use a stable URL: Changing your destination URL requires updating the webhook configuration. Use a URL you control long-term.
• Respond quickly: Your endpoint should acknowledge receipt immediately, then process the data asynchronously. Slow responses increase retry risk.
• Test before going live: Always use the test button after setting up or modifying a webhook to catch configuration issues early.
• Check delivery logs regularly: If your external system stops receiving data, delivery logs will show exactly where the failure occurred.