# Pipedream Integration for Email Validation

URL: https://email-validation.org/integrations/pipedream/
Updated: 2026-11-06

> Documentation index: https://email-validation.org/llms.txt

Validate an address in any Pipedream workflow with Pipedream’s own HTTP / Webhook app, and use the status, reason and action in the next step. Your key sits in a secret environment variable, and the same app can send whole lists as bulk jobs and start a workflow when one finishes.

[Read the full setup guide](https://email-validation.org/docs/guides/pipedream/) [Get an API key](https://email-validation.org/signin/)

- Status: Setup guide
- The HTTP / Webhook app, nothing to install

**Send any HTTP Request** One step

Step settings

```text
Method   POST
URL      https://api.email-validation.org/v1/validate
Headers  Authorization: Bearer {{process.env.EV_API_KEY}}
         Content-Type: application/json
Body     {"email": "<the address from an earlier step>"}
```

## At a glance.

- **Status**: **Setup guide.** Not listed on a marketplace yet: you set it up yourself in a few steps, below and in the full guide.
- **For**: Developers and automation builders on Pipedream who want sign-ups, leads or imports checked inside a workflow, and long lists handed off as bulk jobs.
- **You need**: A Pipedream workflow with a step that gives you an email address, and an [API key](https://email-validation.org/app/api-keys/) made for it, with a [daily credit cap](https://email-validation.org/docs/authentication/#limits), stored as the secret environment variable `EV_API_KEY`.
- **Costs**: 1 credit = 1 validated address, as with any API request. Free: unknown results, API errors, malformed addresses and test addresses on sandbox.email-validation.org.
- **Full guide**: [Read the full setup guide](https://email-validation.org/docs/guides/pipedream/)

## Typical uses.

- **Check each new address**: Send the address from a trigger or an earlier step, then continue with a Filter step, for example only when the action is send.
- **Send a whole list**: One request to the bulk endpoint creates a job from a list of addresses; read the job until its status is completed, then download its results.
- **React when a list is done**: A workflow with the HTTP / Webhook trigger New Requests can receive our Bulk list completed webhook, then read the finished job from the API.

## Set it up. 4 steps.

The short version of the [full setup guide](https://email-validation.org/docs/guides/pipedream/), which stays the reference when a step does not match what you see.

1. **Store your key**: Create an API key with a daily credit cap. In Pipedream, open Settings, Environment Variables, New Variable, name it `EV_API_KEY` and keep it secret, the default.
2. **Add an HTTP request step**: From the HTTP / Webhook app, choose Send any HTTP Request: method POST, URL `https://api.email-validation.org/v1/validate`, or `https://api-eu.email-validation.org/v1/validate` for [EU data residency](https://email-validation.org/docs/eu-data-residency/).
3. **Add the headers and body**: Headers `Authorization` with `Bearer {{process.env.EV_API_KEY}}` and `Content-Type` with `application/json`; body `{"email": "…"}` with the address from an earlier step.
4. **Test and filter**: Test the step with `accepted@sandbox.email-validation.org`, which returns `valid` and costs nothing, then add a Filter step on `status` or `action`.

## Good to know.

- Map `status`, `reason`, `action` and `did_you_mean` into later steps; [statuses and reasons](https://email-validation.org/docs/statuses/) explains each value.
- Our own Pipedream app, with actions such as Validate Email and Create Bulk Job and a trigger when a bulk list finishes, is not listed on Pipedream yet: Pipedream has to add it first. Until then, these steps do the work.
- Never put the key in the URL: such requests are refused. If a step fails with 429, run it again after the seconds in the Retry-After header; an unknown result and an error cost nothing.
- A bulk create request sent twice is two lists: leave automatic retries off for that step, and check the bulk page of the dashboard before running a failed one again.
- Without code, a workflow cannot check a webhook’s signature, so treat a delivery as a hint: read the job from the API with the job\_id it carries and act on that answer.

## Related

- [The full Pipedream setup guide](https://email-validation.org/docs/guides/pipedream/)
- [Bulk lists from a Pipedream workflow](https://email-validation.org/docs/guides/pipedream/#bulk)
- [Webhooks: the Bulk list completed event](https://email-validation.org/docs/webhooks/)
- [The validate endpoint](https://email-validation.org/docs/api/validate/)
- [n8n integration](https://email-validation.org/integrations/n8n/)
- [All integrations](https://email-validation.org/integrations/)