Get API key

Automation platforms

Check email domains, phone numbers and links in Zapier

Check the email domain on every new lead that passes through a Zap, and carry the result into the next step so your sheet, CRM or inbox rule can act on it.

Why the data matters in Zapier

A Zap runs on whatever the trigger hands it, so one throwaway signup address becomes a CRM contact, a welcome email and a Slack ping before anyone looks at it. Every action downstream of the bad record multiplies the cleanup.

What LookValid checks

ProductWhat it does hereCredits
Email Domain CheckReads the domain behind an address: mail records, SPF, DMARC, throwaway domains, free providers and role mailboxes. It never contacts the mail server, so it cannot confirm that a mailbox exists.1 credit per address checked
Phone Numbering-Plan ValidationChecks a phone number against its country numbering plan and returns E.164 and the number type. It cannot tell whether the line is active.1 credit per valid number
Link Safety CheckChecks the domain of a submitted web address against a public list of reported malicious domains. A domain on no list is not proof it is safe.1 credit per URL checked (a check that cannot run is free)

Connect it in four steps

  1. Create a LookValid account and generate an API key from the dashboard, which a person does once.
  2. Add the key as an Authorization entry in the Headers section of the Webhooks by Zapier step with a Bearer value.
  3. Send a POST to the email-domain-check endpoint with the trigger's email in the JSON body; if the answer says found is false, route the Zap to a review path, and if the call returns an error, stop the Zap and read the error code and fix.
  4. Use the signal, throwaway and role mailbox values from the step's output in the fields of the steps that follow, and gate those steps on the signal so a bad address stops the Zap.

A Webhooks by Zapier action step, set to the Custom Request event, placed right after the trigger of a Zap and before any step that creates a record. The call is POST https://YOUR_API_HOST/v1/email-domain-check and costs 1 credit per address checked.

HTTP request step
POST https://YOUR_API_HOST/v1/email-domain-check
Authorization: Bearer {{LOOKVALID_API_KEY}}
Content-Type: application/json
​
{
  "email": "{{value}}"
}
Response fieldGoes into
data.deliverability_signalEmail signal
data.disposableThrowaway domain
data.role_accountRole mailbox

The recipe returns nothing when the lookup finds nothing, which costs no credits for this product, and stops with the error code and fix on a failed request.

Without code

Zapier needs no dedicated LookValid app for this. Add the Webhooks by Zapier action after your trigger and pick Custom Request, which lets you type the JSON body yourself and set your own headers. Enter the endpoint shown above in the URL field, add the Authorization header, and put the trigger's email in the body.

REST and MCPOne shared credit balance

Questions

What does a check cost in credits?

Each call uses the credits listed for the product on the pricing page. A Zap that runs on every new lead uses one check per run, so the monthly credit use follows your lead volume.

What does the email check not do?

It looks at the domain only. It does not contact the mail server and cannot say whether a particular mailbox exists, so treat a good signal as a domain that can receive mail.

Where does the API key go in a Zap?

In the Headers section of the Webhooks by Zapier step, as an Authorization entry with a Bearer value. Keep the Zap editable only by the people who build it.

Sources

LookValid is run by Meralume Labs. It is not connected to, endorsed by or a partner of any company or product named on this page, and every product name belongs to its owner.

LookValid bills every lookup in credits from one shared balance, so the same key works for each check above.

See Email Domain Check