# Verify emails in Zapier

Source: https://docs.rocketverifier.com/integrations/zapier

> Add the RocketVerifier app in Zapier and connect it with an API key. Use Verify Email to check one address in any Zap, Verify Email Batch to submit up to 100,000 addresses, and the Job Completed and Credits Low triggers to react to your account. Each verification uses 1 credit and unknown results are free.

The RocketVerifier app for Zapier verifies addresses inside any Zap and starts Zaps from your RocketVerifier account. It has two triggers, four actions and one search.

## Connect your account

**Step 1. Create an API key**

Open [API keys](https://app.rocketverifier.com/dashboard/api-keys) in the dashboard and create a key. A live key (`rv_live_`) verifies any address. A sandbox key (`rv_test_`) only accepts `@sandbox.rocketverifier.com` addresses and is free, which makes it ideal while you build the Zap.

**Step 2. Add RocketVerifier to a Zap**

In Zapier, add a step, search for [RocketVerifier](https://zapier.com/apps/rocketverifier) and choose an event. When Zapier asks for an account, paste the API key.

**Step 3. Test the connection**

Zapier tests the key with `GET /v1/credits` and labels the connection with the key's last four characters. A revoked key marks the connection as expired, and Zapier asks you to reconnect.

## Verify an email in a Zap

**Verify Email** checks one address in real time. Map the email field from the previous step, such as a form answer or a new CRM contact.

- `Email Address` (string, required):

The address to verify.

- `Timeout (seconds)` (integer):

Optional, 5 to 60. Caps how long the API spends on the address. See [`timeout`](https://docs.rocketverifier.com/api/verify#request) for how the API applies it.

| Output field | Type | What it holds |
| --- | --- | --- |
| `email` | string | The address as verified. |
| `status` | string | `deliverable`, `undeliverable`, `risky` or `unknown`. |
| `recommendation` | string | `send`, `review` or `remove`. |
| `sub_status` | string | The reason behind the status, such as `mailbox_not_found` or `possible_typo`. See [sub-status values](https://docs.rocketverifier.com/results). |
| `reason` | string | The legacy reason code, such as `accepted_email`. |
| `score` | integer | Confidence from 0 to 100. |
| `is_valid`, `is_invalid`, `is_risky`, `is_unknown` | boolean | One flag per status. |
| `is_disposable`, `is_free_provider`, `is_catch_all`, `is_role`, `is_disabled`, `is_full_mailbox`, `is_toxic` | boolean | Address and domain flags. |
| `accept_all` | string | The raw catch-all flag: `yes`, `no` or `unknown`. |
| `catch_all_verdict` | string | `send_safe`, `send_with_caution` or `avoid` on catch-all domains, empty otherwise. |
| `did_you_mean` | string | A corrected address when the input looks like a typo. |
| `provider`, `domain_name` | string | The mailbox provider and the domain. |
| `verified_at` | datetime | When the result was produced. |

## Verify a list in one step

**Verify Email Batch** submits a list as one bulk job and returns right away. Use it when a Zap collects many addresses at once, such as a spreadsheet export.

- **Email Addresses** (required): addresses separated by commas, semicolons or new lines, up to 100,000. Entries without an `@` are dropped before the job is created.
- **Job Name** (optional): a name to find the job later. Defaults to `Zapier Batch <date>`.

The output has `job_id`, `total_emails`, `estimated_time_seconds`, `credits_used`, `credits_remaining`, `status` and `message`. Read the results with the **Job Completed** trigger or the **Get Job Results** action. Bulk pricing is the same as single checks: duplicates are counted once and `unknown` results are refunded. See [bulk verification](https://docs.rocketverifier.com/api/batch).

## Read the results of a job

**Get Job Results** returns a job's status, counts and up to 1,000 result rows.

- **Job ID** (required): pick a recent job from the dropdown, or map `job_id` from Verify Email Batch or Job Completed.
- **Filter by Classification** (optional): `valid`, `invalid`, `risky`, `catch_all`, `disposable` or `unknown`.

Each row in `results` has `email`, `status` (the classification), `recommendation`, `is_valid`, `is_invalid`, `is_risky`, `is_catch_all`, `is_disposable`, `score`, `sub_status` and `verified_at`. The job fields are the same as the Job Completed trigger below, plus `results_count` and `has_more_results`.

## Check your credit balance

**Check Credits** returns `credits` (available), `used_today`, `used_this_month` and `timestamp`. Put it before a large batch to stop the Zap when the balance is too low.

## Find a job

**Find Verification Job** is the app's search. It looks a job up by **Job ID** or by exact **Job Name** (case insensitive, newest first, across your 500 most recent jobs), with an optional **Status** filter: `pending`, `processing`, `completed`, `failed` or `cancelled`. It returns the job fields below, or nothing when no job matches.

## Start a Zap when a job completes

**Job Completed** fires the moment a bulk job finishes. Turning the Zap on creates a RocketVerifier webhook for `job.completed`, and turning it off deletes it.

| Output field | What it holds |
| --- | --- |
| `job_id`, `job_name`, `status` | The job. |
| `total_emails`, `processed_emails` | Addresses in the job and addresses processed. |
| `valid_count`, `invalid_count`, `risky_count`, `catch_all_count`, `disposable_count`, `unknown_count` | Results by classification. |
| `progress_percent`, `is_completed` | 100 and true for a completed job. |
| `download_url` | The CSV export of every result. |
| `created_at`, `completed_at` | Timestamps. |

The `unknown_count` is empty in the live trigger because the `job.completed` event does not carry it. Use Get Job Results when you need it.

## Start a Zap when credits run low

**Credits Low** fires on the `credits.low` event (a charge left the balance at 100 credits or fewer) and on `credits.depleted` (the balance reached zero). Set **Only When Below** to fire only under a lower number; depleted alerts always fire. The output has `event`, `credits_remaining`, `threshold`, `is_depleted`, `timestamp` and `message`.

Both triggers check the `X-RocketVerifier-Signature` header against the webhook secret when it is present, and stop on a mismatch. See [webhook signatures](https://docs.rocketverifier.com/api/webhooks).

## Example Zaps

- **Form to CRM, clean addresses only:** form submission, then Verify Email, then a Filter on `recommendation` equals `send`, then create the CRM contact.
- **Flag typos:** Verify Email, then Paths on `sub_status` equals `possible_typo`, then email the person with `did_you_mean`.
- **Nightly list clean:** Schedule, then a spreadsheet lookup, then Verify Email Batch. A second Zap starts on Job Completed and sends `download_url` to Slack.
- **Top-up reminder:** Credits Low, then a Slack or email alert to the account owner.

## Frequently asked questions

### Which field should my Zap filter on?

Use `recommendation`. It is `send`, `review` or `remove`, so one Filter or Paths step covers every case. Use `status` and `sub_status` when you need the detail.

### Are the yes and no fields booleans in Zapier?

Yes. The app converts the API's `"yes"` and `"no"` strings into real booleans such as `is_disposable` and `is_role`. The raw tri-state `accept_all` (`yes`, `no` or `unknown`) is also returned.

### How do I get every result of a large batch?

Get Job Results returns up to 1,000 rows per call and sets `has_more_results` when there are more. For larger jobs, use the `download_url` from the Job Completed trigger to fetch the full CSV.

### Why did my Zap stop with an expired connection?

The API key was revoked or deleted. Create a new key in the dashboard and reconnect the RocketVerifier account in Zapier.
