Webhooks
Send workspace contact and email events to external services with reusable destinations, signed requests, delivery monitoring, and retry support.
Webhooks let Leadpush notify another system when contact or outbound email events happen in a workspace. A destination stores the endpoint configuration, and an event subscription decides which events should be sent there.
What webhooks can do
Use webhooks to send contact changes and message activity to systems such as:
- a CRM or sales tool
- a customer data platform
- an internal notification service
- a product database
- an analytics or enrichment pipeline
Webhook destinations are reusable and can receive contact and message events through the same subscription.
Campaign webhook nodes are configured separately. Use these guides for reusable destinations, workspace event subscriptions, delivery monitoring, and signed webhook requests.
Setup flow
Create a destination
Create a webhook destination with a name, method, URL template, optional headers, optional query parameters, optional body template, timeout, and enabled state.
Copy the signing secret
When the destination is created, copy the signing secret immediately. Leadpush only shows it after creation or rotation.
Subscribe to events
Create an event subscription and choose the contact and message events that should be delivered to the destination.
Send a test delivery
Use the destination row action to send a generic test or a synthetic sample of any subscribable event. Confirm the receiver records the request.
Monitor delivery history
Review delivery status, response status, response excerpts, and attempts. Retry failed deliveries after fixing the receiver.
Supported events
| Event | When it is sent |
|---|---|
contact.created | A contact is created in the workspace. |
contact.updated | A contact profile or attributes are updated. |
contact.deleted | A contact is deleted. |
contact.subscribed | A contact becomes subscribed. |
contact.unsubscribed | A contact becomes unsubscribed. |
message.sent | Leadpush records that a message was sent. |
message.delivered | The receiving provider reports successful delivery. |
message.deferred | A provider reports a temporary or soft-bounce failure. |
message.bounced | A provider reports a permanent or hard-bounce failure. |
message.rejected | Leadpush rejects the message before successful delivery. |
message.opened | An open is tracked. Every occurrence is delivered. |
message.clicked | A link click is tracked. Every occurrence is delivered. |
message.complained | A spam complaint is reported. |
message.unsubscribed | An unsubscribe is attributed to a message. |
webhook.test | A manual test delivery is sent from a destination. |
Delivery security
Leadpush signs every webhook delivery with a destination signing secret. Receivers should verify the X-Leadpush-Signature header before trusting the payload.
Read Verify webhook signatures before sending webhook data into production systems.
Guides in this section
- Create webhook destinations
- Contact and message event subscriptions
- Template variables and payloads
- Verify webhook signatures
- Test, monitor, and retry deliveries