Setting up With Make
Create a new scenario in Make.
Add a Webhooks module.
Select Custom webhook.
Copy the webhook URL generated by Make.
Keep the scenario open so Make can receive the test request.
Connecting Make Webhook
1. Come back to Evaboot and connect Make through the integration portal.
2. Paste the webhook URL generated by the Custom webhook module in Make.
Evaboot will validate the format and show an error if the URL does not match Make’s webhook pattern.
x-make-apikey (optional)
If your scenario in Make requires an API key, enter it here.
EvaBoot will include it as an x-make-apikey header when sending data to your webhook.
Some Make scenarios are locked so they only accept requests that include your secret key. Adding it here lets Make verify that the webhook call truly comes from your EvaBoot account.
3. Choose which data Evaboot will send.
Select the job type you want this integration to receive. The four available job types are:
Sales Navigator Export
URL Enrichment
Email Finder
Email Verifier
Each job type has its own data structure. You can click View sample webhook data to see an example data.
Filters (Sales Navigator data only)
If you select Sales Navigator Export, additional filters appear:
Lead filter: All leads or only filtered leads.
Email filter:
Safe Only
Safe + Risky
Safe + Risky +Empty
These filters determine which leads will be included in the webhook data.
4. Choose the execution mode.
Two modes are available:
Automatic
Evaboot triggers the webhook automatically whenever a job of the selected type completes and is paid.
You can only have one automatic integration per data type.
Manual
You manually select completed jobs from the dashboard and send them to your webhook.
5. Test your webhook.
Before saving, you must test the integration.
Ensure your Make Webhook node is in listening mode.
Click Listen for Test Event or Execute Workflow.
In Evaboot, click Test Webhook.
Evaboot sends a sample payload to your webhook and waits for a success response.
Success
Evaboot shows a green success log.
The Create Integration button becomes active.
Failure
Evaboot shows the error returned by Make.
Common causes:
Make was not listening
Wrong URL (using the test URL instead of production)
Wrong HTTP method
Authentication rejected
Fix the issue, then run the test again.
6. Save your integration.
Once the test succeeds:
Click Create Integration.
The integration appears in your list, with its status and logs visible.
Your Make workflow is now connected. Evaboot will send data to it according to your selected execution mode.