What Is Evaboot Integration and How Does It Work?
Webhook integrations send your Evaboot results to Make, Zapier, n8n, Clay, or any custom endpoint — automatically or on demand. You don’t have to download and re-upload files by hand. Everything lives on the Integrations page of the dashboard, under the Webhooks tab.
What you can connect
Section titled “What you can connect”Click New integration and pick a destination:
- Make, Zapier, n8n — automation platforms. Evaboot posts to a webhook URL you create there.
- Clay — enrichment tables fed by a Clay webhook source.
- Custom — your own endpoint. Any HTTPS URL, with optional Bearer token, Basic auth, or API key header authentication.
Each destination has its own setup guide — see Related articles below.
A native HubSpot integration is being worked on by our engineering team as a priority. Until it ships, send data to HubSpot through Make, Zapier, or n8n, or import your files directly.
What gets sent
Section titled “What gets sent”A webhook can carry any combination of your Evaboot outputs:
- Exports — Sales Navigator exports
- Lists — URL Enrichment results
- Email Finder jobs
- Email Verifier jobs
You can scope a webhook to all folders or specific ones. Request sample in the setup form shows the exact JSON payload each type sends. Use it to build the receiving side before any real data flows.
Automatic or manual
Section titled “Automatic or manual”Every webhook has a trigger mode:
- Automatic — Evaboot sends the results as soon as a job completes and is paid.
- One automatic integration per data type.
- This is the mode to use to receive your results in your other tools.
- Manual — Evaboot does not send results on its own. Use Send test from the webhook’s actions menu to deliver a sample payload and check your endpoint.
After you create it
Section titled “After you create it”Your webhooks are listed on the Integrations page with their type, status, trigger mode, last run, and run count.
From the actions menu on each row:
- Edit the configuration.
- View logs.
- Send test — a sample payload delivery to check your endpoint.
- Delete the webhook.
Every delivery appears in the logs as Completed, Failed, or Pending. Test deliveries can be shown or hidden.
Prefer to pull instead of push?
Section titled “Prefer to pull instead of push?”If you would rather call Evaboot from your own code, use the API instead. The key lives in the API tab of the same page — see How Does the Evaboot API Work?.