Skip to main content
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:
  • 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
To configure webhooks, go to Settings → Integrations.

​
Setting up your webhook

1

Get a webhook URL from your receiving tool

See the guides below for Microsoft Teams, Slack, or Zapier.
2

Go to Settings → Integrations

You’ll see the Webhook Notifications section.
3

Paste your webhook URL

Enter the URL from your receiving tool and click Save Changes. A webhook secret is generated automatically.
4

Test it

Click Test Webhook to send a sample notification. You should see it appear in your connected tool within a few seconds.

​
Microsoft Teams

1

Choose a channel

In Teams, go to the channel where you want enquiry notifications to appear.
2

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.
3

Name it and create

Give it a name like “Funeral Estimator” and click Create.
4

Copy the URL

Copy the webhook URL that appears.
5

Paste in your dashboard

Go to Settings → Integrations, paste the URL, and click Save Changes.

​
Slack

1

Create a Slack app

Go to api.slack.com/apps and click Create New App.
2

Enable incoming webhooks

Under Incoming Webhooks, toggle it on.
3

Add to a channel

Click Add New Webhook to Workspace and select the channel where notifications should appear.
4

Copy the URL

Copy the webhook URL that Slack generates.
5

Paste in your dashboard

Go to Settings → Integrations, paste the URL, and click Save Changes.

​
Zapier

1

Create a new Zap

In Zapier, start a new Zap.
2

Choose the webhook trigger

Select Webhooks by Zapier as the trigger and choose Catch Hook.
3

Copy the URL

Zapier gives you a unique webhook URL. Copy it.
4

Paste and test

Go to Settings → Integrations, paste the URL, click Save Changes, then click Test Webhook. Zapier will pick up the test data for mapping to your next step (CRM, spreadsheet, email, etc.).

​
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
You should see it appear in your connected tool within a few seconds. If it doesn’t arrive, check the troubleshooting section below.

​
What the webhook sends

Each webhook delivers a JSON payload containing:
The webhook includes the full estimate breakdown — every category, option, and price the family selected. This means your CRM or practice management system can have the complete picture without anyone re-entering data.

​
Webhook secret (for developers)

Each webhook includes an X-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:
  1. Get the raw request body (before parsing JSON)
  2. Compute HMAC-SHA256 using your webhook secret
  3. Compare with the value after sha256= in the header
Your webhook secret is shown in Settings → Integrations. You can copy it, reveal it, or regenerate it at any time.
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
The Test button shows an error?
  • 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
If you’re still stuck, contact us at support@funeralestimatorpro.com and we’ll help you get connected.