Short answer: Drop the "ZeroBounce → Validate Email" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Email email | Required | The email address. Used as the recipient or identifier depending on context. |
{"email": "e.g. user@example.com"}
{"domain": "example.com","status": "valid","account": "john","address": "john@example.com","free_email": false,"sub_status": "","did_you_mean": "","smtp_provider": "google"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.