Outbound webhooks
Get lead, contact, call, email, proposal, contract and invoice events at your own endpoint as they happen. Each one is signed, retried if it fails, and kept in a delivery history you can replay.
From invoice paid to your server
When something happens in Pitch2Sale, it posts a small signed message to your HTTPS endpoint. If your server is down, it tries again, and every attempt is kept.
INV-0042
hooks.acmesales.co
- 01Helios Energy pays INV-0042 and the invoice moves to Paid.
- 02Pitch2Sale posts an invoice.paid event to your endpoint, signed with your secret.
- 03Your server checks the signature and fetches the full invoice from the API.
- 04If it does not answer in time, Pitch2Sale retries with growing gaps.
- 05Every attempt, with payload and response, is kept in Delivery history.
What it does in Pitch2Sale
Pick what you need
Leads, contacts, activities, tasks, calls, emails, texts, form submissions, proposals, contracts and invoices.
Prove it came from us
Each request carries an HMAC-SHA256 signature of the body, made with your secret.
Down for a minute is fine
Three attempts with growing gaps, and a 15-second timeout per try.
See and replay
Every delivery's payload, response and error, with one-click replay and an on/off switch.
Set it up
- Create the webhook with the API.
POST to
/api/v1/webhookswith a name, your HTTPS URL, the events you want and a secret of 16 or more characters. - Verify signatures on your server.
Compare
X-CRM-Signaturewith an HMAC-SHA256 of the raw body using your secret. - Fetch details as needed.
Events carry IDs; call the REST API for the full record.
- Watch it in Settings → Developer → Webhooks.
Open Deliveries to see each attempt.
- Replay or pause.
Replay a failed delivery, or switch the webhook off while you fix your endpoint.
What syncs, and what does not
| Direction | What | When |
|---|---|---|
| Pitch2Sale → you | Lead and contact created, updated, deleted, and lead status changes | As they happen |
| Pitch2Sale → you | Calls completed, emails and texts sent or received, tasks and activities | As they happen |
| Pitch2Sale → you | Form submitted, proposal sent, accepted or declined, contract signed | As they happen |
| Pitch2Sale → you | Invoice created, sent, paid or overdue | As they happen |
| Not synced | Full records (events carry IDs; use the API), and records brought in by a Close migration | — |
Common questions
Can I create a webhook in Settings?
Create it with the API for now. Settings shows its deliveries and lets you replay, switch it off or delete it.
Why is the payload so small?
Events carry IDs so nothing sensitive sits in your logs. Fetch the record from the API.
How do I know it came from Pitch2Sale?
Check the X-CRM-Signature header against your secret.
Can I post to Slack?
Yes, through a small relay that turns the event into a Slack message. A native Slack connector is planned.
Your systems hear it when the deal moves.
Create a webhook with the API and watch the first delivery land.