Check email in Zapier, Make or n8n.

Before you connect

Create a LookupDock workspace, verify your email and create a private API key. Live requests require an active plan or trial with available credits. Email-only checks use one LookupDock credit; retries with the same event ID and input reuse the result.

These recipes use each platform's HTTP step. They are not native marketplace apps. Zapier's API by Zapier action and custom error handling require premium access; its free account alone is not enough. Make HTTP v4 and self-hosted n8n were tested without a paid platform upgrade.

Start with your own authorized test input. The check does not prove that a mailbox exists. Review the email coverage and uncertainty before attaching a business decision.

POST https://lookupdock.com/api/v1/signup-check
Authorization: Bearer <private API key>
Content-Type: application/json
Idempotency-Key: <stable source event ID>

{"email":"[email protected]"}

Keep the key in the platform's private credential store. Never put it in a URL, exported template or notification. Create one stable event ID per source event and reuse it only with the same input.

Zapier

1. Choose your existing signup or lead trigger. Its record must supply an email and a stable, unique event ID.
2. Add Code by Zapier → Run Javascript. Map Input Data email and event_id from that record. Paste the request serializer. It creates the whole JSON body safely, including quotes and backslashes.
3. Add API by Zapier → API Request. Create a Static Headers connection restricted to lookupdock.com, with Authorization: Bearer <key>. Set POST and the URL above. Add Content-Type: application/json and map Idempotency-Key from the serializer's event_id. Map its entire body output into Body; do not insert raw email text into handwritten JSON. Leave Succeed on Error? set to False.
4. After the API step, add another Javascript Code step. Map Input Data envelope to the API step's Step Output and paste the result classifier. Only a completed live HTTP200 allow result with a completed email check and no skipped checks reaches allow. Review, block, pending and malformed results reach human_review.
5. On the API step, open its menu and choose Add error handler. Add a Code step with the fixed error label, then connect your internal review or alert destination. Send only the fixed labels and a link to the platform run; omit email, key and raw errors.

A custom error handler disables this Zap's Autoreplay and suppresses Zapier's usual error email. Add and test your own notification step in that handler. If you instead use Autoreplay, it is a separate account-level setting: keep the stable event ID and verify alerts after the final attempt. Do not turn on both approaches expecting the same behavior.

Zapier HTTP setup · Error-handler behavior

Make

1. After your existing source module, add HTTP Version 4 → Make a request.
2. Choose API key authentication. Create a private connection restricted to https://lookupdock.com, placed in the header named Authorization, with value Bearer <key>.
3. Set POST and the URL above. Set Body content type to application/json, input method Data structure, with one text field named email. Map that field from your source. Add Idempotency-Key from its stable event ID.
4. Enable Parse response and Return error if HTTP request fails. Set a 10-second timeout. Disable redirects and cookie sharing; keep TLS verification enabled.
5. Add Tools → Set variable, named route. Paste the routing formula. Its HTTP module is numbered 4; replace those references with your HTTP module's actual number. The formula uses Make's & logical operator. Connect human_review to your internal review destination.
6. Add an error-handling route to the HTTP module. Send a fixed human_review / request_failed notification to your own operations destination. A failed request must not resume with an invented allow result.

Make can report HTTP429, HTTP503 and timeouts as warnings while stopping the affected bundle. A warning is not an allow result. If you use the Retry error handler, enable incomplete executions, set a bounded attempt count and delay, and keep the same event ID. Check storage and retention because incomplete executions retain the source input.

Make HTTP v4 · Incomplete-execution retries

n8n

Download the n8n workflow

1. Import the JSON into your n8n instance. The workflow starts inactive and contains no key or credential ID.
2. In LookupDock request, select a private Header Auth credential named Authorization, with value Bearer <key>.
3. Replace Source event with your authorized source and map email and event_id. Replace the example event ID before any real execution.
4. Run a manual test. Result label emits only route and reason. Error label emits human_review / request_failed. Connect both outputs to your own review or operations destination before enabling a source trigger.
5. Keep response status enabled, redirects disabled and the 10-second timeout. Automatic retries start off. If you enable a bounded retry policy, preserve the same event ID and test both recovery and exhaustion.

The HTTP node handles request errors inline. An n8n Error Trigger does not run for manual tests: use a separate error workflow for other failures, select it in workflow settings and verify it with an automatic execution. The download disables saved successful, failed and manual execution data; also review instance-wide retention and alert content.

n8n HTTP Request · Error Trigger

Verify your workflow, then activate it

Test an allow result, review and block signals, an unavailable or pending check, expired credentials and a timeout. Confirm that errors cannot reach the allow branch and that your own alert destination receives a sanitized notification. Check that a retry uses the same event ID and input, without duplicate downstream actions.

Inspect the platform's run history and retention before using personal data. These downloadable recipes have passed controlled platform tests; your own source, credentials, subscription and destination still need verification in your account. A configured credential or a successful sample is not proof of a live workflow.

Full API and policy reference · LookupDock pricing