ravn
Integrations · Zapier

Ravn in Zapier, with Webhooks by Zapier

Add a Webhooks by Zapier action with the POST event, send the email as JSON to https://api.askravn.com/v1/tools/validate_email with an Authorization header, then add a Filter so only valid addresses continue. This needs a Zapier plan that includes Webhooks.

Start free: 1,000 lookups Read the docs

Setup

Build the webhook step

  1. / 01

    Add the action

    After your trigger, add an action and choose Webhooks by Zapier, event POST.

  2. / 02

    Set URL and payload type

    URL https://api.askravn.com/v1/tools/validate_email. Payload Type json.

  3. / 03

    Map the data

    Under Data, add the key email and map the email field from your trigger as the value.

  4. / 04

    Add headers

    Under Headers add Authorization = Bearer rw_live_… and Content-Type = application/json.

  5. / 05

    Test and filter

    Test the step. Then add a Filter: continue only if the result Status is ok and the result Results Status is valid.

Config

What the step sends and gets back

Zapier flattens the response, so nested fields show up as separate values you can map in later steps.

POST https://api.askravn.com/v1/tools/validate_email
Authorization: Bearer rw_live_…
Content-Type: application/json

{ "email": "jane@acme.com" }

→ 200
{
  "status": "ok",
  "results": {
    "email": "jane@acme.com",
    "status": "valid",
    "risk_score": "A",
    "reason": "mailbox_exists",
    "disposable": false,
    "role_account": false,
    "catch_all": false
  },
  "metadata": { "lookups_used": 1 }
}
Recipes

Zaps worth building

  1. / 01

    Stop junk form fills

    Form submission → Ravn verify → Filter on valid → add to your email tool. Disposable and mistyped addresses never reach your list.

  2. / 02

    Find the email for a new deal

    New CRM deal with a contact name and company domain → POST to search_business_email_by_name with keys name and company → update the contact. See the email finder API.

  3. / 03

    Route by company size

    New lead → POST to domain_to_company → Paths by employee_count. It runs on your own provider key (People Data Labs), one lookup per company found; see pricing.

Good to know

Keeping Zaps cheap and predictable

Put the Ravn step after any Filter that already drops rows you don’t care about, so you only spend lookups on records that matter. Every tool is one lookup, and a miss is free. Our own checks (verify, find email, website, phone validation, IP) need no key; people and company lookups run on your own provider key (People Data Labs), which bills you for the records.

Use the free get_usage tool in a scheduled Zap if you want a daily note of what was used. If a Zap starts returning 429, you have hit a rate limit or your monthly spending cap (429 spend_cap_reached); see how fair use works. To try a verdict before building anything, use the free email verifier.

FAQ

Common questions.

All questions →

Can I use Ravn on a free Zapier plan?

Webhooks by Zapier is only available on Zapier plans that include it. On other plans, run list jobs with the CSV command or use Make or n8n instead.

Is there a Ravn app in the Zapier directory?

No. Webhooks by Zapier calls our REST API directly, which gives you every tool rather than a fixed list of actions.

What happens in the Zap when no email is found?

The step still succeeds with HTTP 200 and status: not_found, and the lookup is given back. Your Filter stops the run there, so nothing downstream gets an empty value.

My Zap step errors with 403 provider_key_required. What does it mean?

You called a people, company or carrier tool without your own provider key connected. Add one with ravn keys add pdl (or twilio), or on the account page, then retry. Our own checks such as verification need no key; details are on the pricing page.

More in integrations

Every page uses the same account, plan and tools. See pricing →