Skip to content

Send new enquiries to Zapier or your own tools

Estimator Studio can post every new or updated enquiry to an address you choose. That's called a webhook. Zapier, Make and many CRMs can receive webhooks and pass the details on to the rest of your tools.

Good to know: this is a webhook you connect yourself, not a built-in Zapier app. Zapier's webhook trigger (“Webhooks by Zapier”) may need a paid Zapier plan; check Zapier's current plans. Only the business owner can set up integrations.

1. Get a receiving address from Zapier

  1. In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger.
  2. Pick the Catch Hook event and continue.
  3. Copy the webhook URL Zapier shows you (it starts with https://hooks.zapier.com/).

Using another tool? Look for an “incoming webhook” or “catch hook” and copy its https address.

2. Add it in Estimator Studio

  1. Sign in and open Integrations.
  2. Paste the address, give it a name (for example “Zapier to CRM”) and select Add.
  3. Copy the signing secret shown once and keep it somewhere safe. Zapier's Catch Hook doesn't check it, but your own systems can.
  4. Select Send test. In Zapier, use “Test trigger” to pull in the test event.

3. Use the enquiry details

Each event is JSON. The fields you'll use most are under data.lead:

FieldWhat it is
referenceThe enquiry reference, e.g. ES-7K3M9Q2B
contact.name, contact.email, contact.phoneWhat the customer gave you (fields you didn't ask for are empty)
intentassessment (asked you to follow up) or summary (asked for a copy only)
selectedPackage.nameThe option they're interested in, if they chose one
result.packagesThe prices they saw, with result.currency
answersEach question and their answer
statusYour inbox status: New, Contacted, AssessmentBooked, Won or Lost

The top level also has type (lead.created, lead.updated or test.ping), an event id, and testMode, which is true when you tried your own estimator while signed in. In Zapier you can add a Filter step to skip test events or updates.

What to expect

  • New enquiries send lead.created. A customer who first asks for a copy and later asks for an assessment, or a status change in your inbox, sends lead.updated for the same lead.
  • Retries: if the receiver is down or slow, we try again over the next day. The same event id is used, so a receiver can ignore repeats.
  • History: Integrations shows each delivery, whether it succeeded, and lets you send one again.
  • Privacy: the receiving address can be used by anyone who knows it, so treat it like a password, and only connect tools you're allowed to share customer details with.

For developers: checking the signature

Each request has an X-EstimatorStudio-Signature header like t=1760400000,v1=5f2b…. Compute HMAC-SHA256 over {t}.{raw request body} with the endpoint's signing secret, compare the hex result with v1 in constant time, and reject requests where t is more than 5 minutes old. Answer with any 2xx status to confirm receipt; 410 turns the endpoint off.

Related help

Last reviewed October 2026 against the current version of Estimator Studio.

Stuck? Email mail@estimatorstudio.com with your website address and what you see.