Skip to content

How do I set up my Make integration?

View as Markdown Download .md

Create a custom webhook in a Make scenario, then paste its URL into a new Make integration in Evaboot. Once connected, Evaboot sends your export and email results straight into your Make scenario.

Before you start

Section titled “Before you start”

In Make: create the webhook

Section titled “In Make: create the webhook”
  1. Create a new scenario in Make. A new empty scenario in Make
  2. Add a Webhooks module and choose Custom webhook. Click Add next to the Webhook dropdown and give the webhook a name. Adding the Webhooks module and selecting Custom webhook
  3. Copy the webhook URL Make generates. Copying the generated webhook URL to the clipboard
  4. Save the scenario and turn it on. Keep the tab open — you’ll come back to map fields after the first delivery. Saving the scenario and setting it live

In Evaboot: connect it

Section titled “In Evaboot: connect it”
  1. Open Integrations. Stay on the Integrations tab, click New integration, and choose Make.
  2. Name the integration and paste the webhook URL. The New Make integration form with the webhook URL and optional API key fields
  3. Optional — API key. If you restrict your Make webhook with API key authentication (Make stores the keys in a keychain), enter the same key here. Evaboot sends it as the x-make-apikey header. Leave it empty otherwise.
  4. Pick what to send.
    • Data types: Exports, Lists (URL Enrichment), Email Finder jobs, Email Verifier jobs.
    • Scope: all folders, or specific ones.
  5. Pick the trigger.
    • Automatic — sends results as soon as a job completes and is paid. One automatic integration per data type.
    • Manual — sends nothing on its own. It delivers when you send a test, or when you click Push this export on a finished export.
  6. Click Request sample to see the exact JSON Evaboot will post — useful for building the rest of your scenario. The Make integration form with the Request sample payload expanded
  7. Click Create webhook.

Test it

Section titled “Test it”
  1. In Make: click Run once on the scenario so the webhook is listening.
  2. In Evaboot: open the webhook’s actions menu and click Send test. Evaboot posts a sample payload — fake data, never your real leads.
  3. In Make: the delivery appears in View logs with a TEST tag and the HTTP response code, and Make shows the received bundle. Use it to map fields in the modules you add after the webhook.

If it didn’t work

Section titled “If it didn’t work”
  • “Non-2xx response or transport failure” — check the logged response code. Confirm the URL is the one Make generated for this webhook.
  • Make receives nothing — the scenario must be on (or listening via Run once). The webhook URL must be current — Make regenerates it if you recreate the webhook module.
  • 401/403 in the logs — the API key in Evaboot doesn’t match the key configured on the Make webhook.

Another way: the Evaboot Make app

Section titled “Another way: the Evaboot Make app”

Instead of a webhook, you can add Evaboot modules to your Make scenarios directly.

  1. Open Integrations and switch to the Automations tab. The Automations tab of the Integrations page with the Make app, Zapier app, and n8n community node
  2. Click Install the Make app and install it in your Make organization.
  3. In a scenario, add an Evaboot module — for example Verify an Email. Make asks for your Evaboot API key when you create the connection. Copy it from the API key page. Make's module search showing the Evaboot app with Verify an Email, List Exports, and Find an Email The Evaboot app in Make marked Invited, with its triggers listed

The Evaboot app is not listed in Make’s public app catalog yet, so Make’s AI assistant can’t find it. Install it from the link in step 2 and build the scenario by hand.

Section titled “Related articles”