# Send events to another tool

> Configure an event destination, test delivery, and handle retries without duplicating work.

Canonical page: https://getleadsource.io/docs/webhooks/

Lead Source documentation

## Send events to another tool

Configure an event destination, test delivery, and handle retries without duplicating work.

Documentation

[Overview](https://getleadsource.io/docs/)
[Getting started](https://getleadsource.io/docs/getting-started/)[Tracking numbers](https://getleadsource.io/docs/tracking-numbers/)[Call routing setup](https://getleadsource.io/docs/call-routing/)[Website number swapping](https://getleadsource.io/docs/website-attribution/)[Call review and reporting](https://getleadsource.io/docs/call-review/)[Send events to another tool](https://getleadsource.io/docs/webhooks/)[API access](https://getleadsource.io/docs/api/)[Publisher ping and handoff](https://getleadsource.io/docs/publisher-ping-post/)[A pay-per-call example](https://getleadsource.io/docs/pay-per-call-workflow/)[An agency reporting example](https://getleadsource.io/docs/agency-reporting-example/)[Troubleshooting](https://getleadsource.io/docs/support/)

Reviewed October 15, 2026

### Prepare a receiving service

A webhook sends an event to a server you control. It is a custom connection, not a promise of a native connector to every CRM or ad platform. Use the event format and security settings shown in your account.

-

#### Choose only needed events

Open the account’s integration settings and choose which available events the receiver needs.

-

#### Configure a secure destination

Use the approved HTTPS receiver and the authentication method supported by the integration. Keep secrets on the server and out of public web pages.

-

#### Test and inspect delivery

Send an intentional test using the application’s testing controls. Check the delivery history and the receiver’s response before enabling business actions.

### Make retries safe

A receiver may see the same event more than once. Store the event reference before applying a business change, return a successful response only after durable receipt, and avoid repeating a charge, email, or CRM update on replay. Do not assume a delivery order unless the documented event contract provides one.

[API access and errors](https://getleadsource.io/docs/api/)[Supported integrations](https://getleadsource.io/integrations/)

[Explore the walkthrough](https://getleadsource.io/demo/)[Review product availability](https://getleadsource.io/integrations/)