Webhooks send enquiry details to another system the moment a family submits their contact details. Think of it as an instant alert — the information arrives in whichever tool you use to manage enquiries, without you needing to check your email. Common uses:Documentation Index
Fetch the complete documentation index at: https://help.funeralestimatorpro.com/llms.txt
Use this file to discover all available pages before exploring further.
- Get a notification in your Microsoft Teams channel
- Send enquiry details to Slack
- Trigger a workflow in Zapier or Make to create a CRM record
- Feed enquiry data directly into your practice management system
Setting up your webhook
Get a webhook URL from your receiving tool
See the guides below for Microsoft Teams, Slack, or Zapier.
Paste your webhook URL
Enter the URL from your receiving tool and click Save Changes. A webhook secret is generated automatically.
Microsoft Teams
Add an incoming webhook connector
Click the ··· menu next to the channel name, then Connectors (or Manage channel → Connectors). Find Incoming Webhook and click Configure.
Slack
Create a Slack app
Go to api.slack.com/apps and click Create New App.
Add to a channel
Click Add New Webhook to Workspace and select the channel where notifications should appear.
Zapier
Testing your webhook
Click Test Webhook in Settings → Integrations. This sends a sample notification with:- Name: “Test from Funeral Estimator Pro”
- Notes: A message confirming the integration is working
- No real customer data is sent
What the webhook sends
Each webhook delivers a JSON payload containing:| Field | Description |
|---|---|
lead.name | Family member’s name |
lead.email | Email address |
lead.phone | Phone number (if provided) |
lead.preferred_contact | Email or phone |
lead.notes | Any message from the family |
estimate.total | Estimate total amount |
estimate.service_type | e.g. Cremation, Burial |
estimate.estimate_url | Link to the branded estimate page |
estimate.selections | Every selected item with category, name, price, and quantity |
branch.name | Branch name (if applicable) |
Webhook secret (for developers)
Each webhook includes anX-Webhook-Signature header containing an HMAC-SHA256 signature of the request body. If you’re building a custom integration, you can verify the signature to confirm the webhook came from Funeral Estimator Pro:
- Get the raw request body (before parsing JSON)
- Compute HMAC-SHA256 using your webhook secret
- Compare with the value after
sha256=in the header
Most tools (Teams, Slack, Zapier) don’t need the webhook secret — it’s only relevant if you’re building a custom integration and want to verify the sender.
Troubleshooting
Webhook not arriving?- Check the URL is correct — try clicking Test Webhook to see what happens
- Make sure your receiving tool is set up to accept POST requests
- Check if a firewall or security tool is blocking incoming requests from external services
- Status 0 means we couldn’t reach the URL at all — double-check it’s correct and publicly accessible
- Status 4xx or 5xx means your endpoint returned an error — check the receiving tool’s configuration