# How do I send Evaboot results to Make?

**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

- A [Make](https://www.make.com/) account where you can create scenarios.

## In Make: create the webhook

1. **Create a new scenario** in Make.
   ![A new empty scenario in Make](https://help.evaboot.com/images/12907410/img-1.png)
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](https://help.evaboot.com/images/12907410/img-2.gif)
3. **Copy the webhook URL** Make generates.
   ![Copying the generated webhook URL to the clipboard](https://help.evaboot.com/images/12907410/img-3.gif)
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](https://help.evaboot.com/images/12907410/img-4.png)

## In Evaboot: connect it

5. **Open [Integrations](https://dash.evaboot.com/dash/integrations/)**. Stay on the **Integrations** tab, click **New integration**, and choose **Make**.

   ![The New integration page with the Make card highlighted](https://help.evaboot.com/images/flows/manual-annotated-integrations/01-pick-make.png)
6. **Name the integration and paste the webhook URL.**
   ![The New Make integration form with the name, webhook URL, optional API key, data types, trigger and Create webhook button numbered](https://help.evaboot.com/images/flows/manual-annotated-integrations/02-make-form.png)
7. **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.
8. **Pick what to send.**
   - Send data from: Sales Navigator exports, URL enrichment, Email finder, Email verifier.
   - Send leads from: all exports, all recurring exports, specific recurring exports, or specific folders.
9. **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.
10. **Open Request sample** and pick a data type to see the exact JSON Evaboot will post — useful for building the rest of your scenario.
   ![The Request sample section of the integration form expanded, showing the JSON payload](https://help.evaboot.com/images/flows/manual-annotated-integrations/03-make-request-sample.png)
11. **Click Create webhook.**

## Test it

12. **In Make:** click **Run once** on the scenario so the webhook is listening.
13. **In Evaboot:** open the webhook's actions menu and click **Send test**. Evaboot posts a sample payload — fake data, never your real leads.

   ![The actions menu of a webhook on the Integrations page, with Send test and View logs highlighted](https://help.evaboot.com/images/flows/manual-annotated-integrations/04-send-test.png)
14. **In Evaboot:** click **View logs** in the same actions menu. The test delivery shows a `TEST` tag and the HTTP response code.
15. **In Make:** the received bundle appears. Use it to map fields in the modules you add after the webhook.

## 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

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

1. **Open [Integrations](https://dash.evaboot.com/dash/integrations/)** and switch to the **Automations** tab.
   ![The Automations tab of the Integrations page with the Install the Make app, Install the Zapier app and Install the n8n node buttons](https://help.evaboot.com/images/flows/manual-annotated-integrations/05-automations-tab.png)
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](https://dash.evaboot.com/dash/api/) page.
   ![Make's module search showing the Evaboot app with Verify an Email, List Exports, and Find an Email](https://help.evaboot.com/images/flows/manual-make/01-search-app.png)
   ![The Evaboot app in Make marked Invited, with its triggers listed](https://help.evaboot.com/images/flows/manual-make/02-modules.png)

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.

## 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 Do I Set Up My Zapier Integration?](https://help.evaboot.com/public/integrations/how-do-i-set-up-my-zapier-integration/)
- [How Do I Set Up My n8n Integration?](https://help.evaboot.com/public/integrations/how-do-i-set-up-my-n8n-integration/)
- [How Do I Set Up My Clay Integration?](https://help.evaboot.com/public/integrations/how-do-i-set-up-my-clay-integration/)