Skip to content

How Do I Set Up My n8n Integration?

Create a Webhook trigger in n8n, publish the workflow, then paste its Production URL into a new n8n integration in Evaboot. Once connected, Evaboot sends your export and email results straight into your n8n workflow.

  1. Create a new workflow in n8n and click Add first step. An empty n8n workflow with the Add first step placeholder
  2. Search for “webhook” and pick the Webhook trigger — “Starts the workflow when a webhook is called”. The n8n trigger panel filtered to the Webhook trigger
  3. Set HTTP Method to POST. Evaboot delivers data as a JSON POST request.
  4. Copy the Production URL from the Webhook URLs box. The Webhook node with HTTP method POST and the Production URL tab selected
  5. Publish the workflow. The Production URL only accepts calls once the workflow is published. The Test URL only works while the node is listening for a test event. The n8n canvas with the Webhook node and the Publish button
  1. Open Integrations. Stay on the Webhooks tab, click New integration, and choose n8n.
  2. Name the integration and paste the Production URL. The New n8n integration form with the webhook URL and optional header fields
  3. Optional — header authentication. If your n8n Webhook node uses Header Auth, enter the same header name and value here. Evaboot pre-fills x-n8n-apikey as the header name. Leave both fields empty if your webhook has no authentication.
  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 — keeps the webhook quiet. It only delivers when you send a test.
  1. Click Request sample to see the exact JSON Evaboot will post, so you can map fields in n8n before any real data arrives.
  2. Click Create webhook.

From the webhook’s row on the Integrations page, open the actions menu and click Send test. Evaboot posts a sample payload — fake data, never your real leads — to your n8n workflow. In View logs the delivery appears with a TEST tag and the HTTP response code — 200 means n8n received it.

  • “Non-2xx response or transport failure” — check the logged response code. A 404 usually means the workflow is not published or the URL is the Test URL — republish and paste the Production URL.
  • n8n receives nothing — make sure the workflow is published, the method is POST, and the URL was copied from the Production tab.
  • 401/403 in the logs — the header name or value in Evaboot does not match the Header Auth configured on the n8n Webhook node.