# How do I send Evaboot results to a webhook?

**Create a Custom integration with your HTTPS URL, and Evaboot posts your results to it as JSON.** Use it for your own server or any tool that gives you a webhook URL.

## Before you start

- An endpoint that accepts a `POST` with a JSON body. The URL must start with `https://`.
- Optional: the credentials your endpoint checks. Evaboot supports a Bearer token, Basic auth, or an API key header.

## Create the webhook

1. **Open [Integrations](https://dash.evaboot.com/dash/integrations/)** and click **New integration**. If you have no integration yet, the tool cards show on the page directly.
   ![The Integrations page of the Evaboot dashboard with a card for each tool](https://help.evaboot.com/images/flows/manual-integrations/00-integrations.png)
2. **Click the Custom card** (Your own endpoint).
   ![The Custom webhook page in the Evaboot dashboard](https://help.evaboot.com/images/flows/manual-integrations/webhook-connect.png)
3. **Name the integration** and paste your **Webhook URL**.
4. **Pick the Authentication.**
   - **None**: a plain POST.
   - **Bearer token**: sent as `Authorization: Bearer <your token>`.
   - **Basic auth**: enter a **Username** and **Password**.
   - **API key header**: pick the **Header name** (`x-api-key`, `x-api-token` or `api-key`) and enter the **Header value**.
5. **Pick what to send** under **Send data from**: Sales Navigator exports, URL enrichment, Email finder or Email verifier. Exports and email jobs send different payloads, so one webhook takes one or the other, not both.
6. **For email jobs, set the filters**: **Email filter** and **Qualification filter**.
7. **Pick the trigger.**
   - **Automatic: send when a job completes**: each finished, unlocked job is sent. Under **Send leads from**, choose all exports, all recurring exports, specific recurring exports, or specific folders.
   - **Manual: only send when you trigger it**: nothing is sent until you push a job yourself or send a test.
8. **Open Request sample** to see the exact JSON for the first data type you checked.
9. **Click Create webhook.**
10. **Send a test.** Open the webhook's actions menu on the Integrations page and click **Send test**. Evaboot posts a sample with fake data, never your real leads.

## What Evaboot posts

Each delivery is one `POST` with `Content-Type: application/json`. One delivery carries the whole job, with the leads in a `prospects` array.

For exports and URL enrichment:

- `search_id`, `search_name`, `status` (`EXECUTED`), `extraction_type` (`search`, `list` or `upload`), `total_prospects`, `progress`, `created_at`, `completed_at`.
- `prospects`: one object per lead, keyed by the same column names as your CSV download, such as `First Name`, `Email` or `Linkedin URL Public`. Every key is always present; an empty value is `""`.

For email finder and email verifier jobs:

- `search_id`, `search_name`, `status` (`complete`), `job_type` (`email_finder` or `email_validation`), `total_prospects`, `progress`, `created_at`, `updated_at`.
- `prospects`: snake_case keys, such as `found_email` and `email_validity`.

Evaboot does not deduplicate for you: every push sends the full job again. Use `search_id` and each lead's LinkedIn URL to skip records you already have.

## Send a job by hand

On the export list, click **+** in the **Push** column of a finished export (**Push this export**) and pick your webhook. The export must be unlocked first. The email finder and verifier lists have the same **+** button.

To send every run of a recurring export, pick the webhook under **Send new leads to** when you set the schedule up.

## How deliveries are checked

- Your endpoint must answer within 10 seconds.
- A `2xx` or `3xx` answer counts as delivered. A `4xx` or `5xx` answer is a failure.
- A network error or timeout is retried up to 3 times.
- Every delivery appears in **View logs** with its status and HTTP code. Tests carry a `TEST` tag.

## If it didn't work

- **"Webhook URL must use https://."**: use an HTTPS URL. Plain `http://` is refused.
- **"Create one webhook per data category"**: you checked exports and email jobs together. Create two webhooks.
- **"non-2xx response or transport failure"** in the logs: your endpoint did not answer in time, or could not be reached. Check the URL and that the server is up.
- **"HTTP 401" or "HTTP 403"** in the logs: your endpoint refused the credentials. Check the **Authentication** settings.
- **The webhook shows Down**: it failed 5 times in a row, or your endpoint answered `410`. Fix the endpoint, then click **Send test** or **Reactivate** in the actions menu.

## Related articles

- [How Do I Send My Evaboot Results to Other Tools?](https://help.evaboot.com/public/integrations/what-is-evaboot-integration-and-how-does-it-work/)
- [How Does the Evaboot API Work?](https://help.evaboot.com/public/integrations/how-does-the-evaboot-api-work/)
- [How Do I Send Evaboot Results to Make?](https://help.evaboot.com/public/integrations/how-do-i-set-up-my-make-integration/)