Inbound Webhooks
Leads from Your Other Tools, Straight into Your CRM.CRM webhooks that take in leads and events from the tools you already use.
Give each lead source its own webhook address. Adoptiv checks the signature, ignores repeat deliveries, logs every request, and hands what arrives to the automation you built, including creating the lead. If a source should stop sending, generate a new address and the old one stops working.
- One address per source
- Signed and deduplicated
- Every delivery logged
How it works
- A tool sends dataA web form, a lead vendor, your own app
- Checked on arrivalSignature or token, size and rate limits
- A repeat deliveryMarked duplicate, starts nothingA new deliveryRuns your automation, like creating a lead
- Every request loggedAccepted, refused or duplicate
Leads Arrive Once, from Sources You Trust.
A repeat delivery within 24 hours gets the same success reply and starts nothing new.
Set a signing secret or a token, and requests that don’t match are refused.
Generate a new address for that source, and the old one stops working.
Accepted, refused or duplicate, each delivery is logged, with sensitive headers blanked.
Connect a Source in Three Steps.
Create an Address
Adoptiv generates a unique address for the source. Set a signing secret or a token on it.
Choose What Happens
Point the address at the automation that should run, such as creating a lead.
Paste It into the Sender
Add the address to your form, lead vendor or app. Every delivery appears in the log.
Two Ways to Verify Each Sender.
Set one on every address. With neither, the address accepts any request.
Adoptiv checks the signature header against a hash of the exact body received. The one to use when the sender supports it.
Adoptiv reads a token from a header, a bearer line or the query string. Used only when no signing secret is set.
What Are CRM Webhooks, and How Do Inbound Ones Work?
CRM webhooks let your other tools send data into the CRM the moment something happens. An inbound webhook is a web address you give to a sender, like a web form or your own app, and Adoptiv acts on whatever arrives.
Each source gets its own generated address, 32 characters long, which works as its first secret. On top of that, webhook signature verification checks an HMAC signature against the exact body received, or a shared token if the sender can’t sign. Bodies over the size limit, 1 MB unless you raise it, are refused before they are read, and you can cap requests per minute.
Duplicate webhook deliveries are caught for 24 hours, using the sender’s delivery key, or a fingerprint of the body when there is none. A repeat gets the same success reply, is marked duplicate in the log, and starts nothing. Webhook logs keep every request, accepted or refused, with sensitive headers blanked, until you delete the address.
Use a webhook to create a lead, then let automatic adding start its sequence: that is how you send form leads to a CRM and follow up at once. To read or update records from outside, use the REST API. To send data out when a rule fires, use workflow actions.
Everything a Safe Webhook Needs, Built In.
A generated address for each sender, so you can cut one off alone.
HMAC signatures checked against the exact body received.
A shared token in a header, a bearer line or the query string.
Repeats within 24 hours are recognized and start nothing.
1 MB by default, adjustable up to 50 MB.
Cap requests per minute for any sender. Off until you set a number.
Every request kept, accepted or refused, with sensitive headers blanked.
Generate a new address, and the old one stops working.
For Teams with Leads Coming from Everywhere.
Signed Webhooks vs a Plain Catch-All URL.
| What | A basic webhook URL | With Adoptiv |
|---|---|---|
| Who can send | A basic webhook URL: Anyone with the URL | With Adoptiv: Only senders with the right signature or token, once set |
| Retries | A basic webhook URL: Can create the same lead twice | With Adoptiv: Repeats within 24 hours start nothing |
| Oversized requests | A basic webhook URL: Read in full | With Adoptiv: Refused before they are read |
| When something goes wrong | A basic webhook URL: Nothing to look at | With Adoptiv: Every request logged, refused ones too |
| Revoking a sender | A basic webhook URL: Change it everywhere | With Adoptiv: Generate a new address for that source only |
A signing secret and a token are both optional. Set one on every address: with neither, the address accepts any request.
Inbound Webhooks Questions, Answered.
What is an inbound webhook?
A web address another app sends data to when something happens, like a form being filled in. Adoptiv receives it and runs the automation you chose.
Can a webhook create a lead?
Yes. Point the webhook at automation that writes a lead. Deals and tasks aren’t created directly from a webhook.
How does Adoptiv verify webhooks?
With a signing secret, it checks the signature header against the exact body received. Without one, it can check a shared token. Set neither and the address accepts any request, so set one on every address.
What happens if a sender retries?
Repeats are recognized for 24 hours, from the delivery key the sender includes or, if there is none, from the body itself. A repeat gets the same success reply and starts nothing new.
How do I stop a source sending to me?
Generate a new address for it. The old address stops working, and every other source carries on.
What is HMAC webhook verification?
The sender signs each request with a secret you share. Adoptiv works out the signature again from the exact body it received, and only accepts the request if the two match.
How long are webhook logs kept?
Until you delete the address. Deleting the address deletes its log too.
What is the maximum webhook size?
1 MB by default. You can raise it to as much as 50 MB.
Is there a rate limit?
Only if you set one. You can cap requests per source per minute; until you name a number, there is no cap.
Still have a question? A real person replies in under 60 seconds in US business hours. Talk to our team →
14-day free trial
Plug Your Lead Sources into Adoptiv.
Create your first webhook address in the free trial. Free for 14 days, no credit card.
14-day trial · no card · migration included