ActionAbstract Email ValidationUpdated September 2026
Is this email address deliverable?
Short answer: You can validate email address in Abstract Email Validation by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Abstract Email Validation Validate Email Address action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
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. |
Sample request
{"email": "e.g. user@example.com"}
Returns
{"email": "john@example.com","is_free_email": {"value": false},"quality_score": 0.95,"deliverability": "DELIVERABLE","is_valid_format": {"value": true},"is_disposable_email": {"value": false}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Validate Email Address.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Validate Email Address.
What does the Validate Email Address action do in Abstract Email Validation?
Real-time syntax + MX + SMTP-handshake validation. Returns deliverable/undeliverable/risky/unknown plus per-check booleans (free email, disposable, role address, catch-all, SMTP valid). Latency 100-300ms — fast enough to validate inside signup forms.
What inputs does Validate Email Address require?
Required: Email. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Abstract Email Validation returns an error?
The run history shows the failed step with its input and the error message Abstract Email Validation returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Validate Email Address support batch operations?
Run Validate Email Address inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Abstract Email Validation's rate limits.
More actions