ActionAbstract Email ValidationUpdated May 2026

Is this email address deliverable?

Short answer: Drop the "Abstract Email Validation → Validate Email Address" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 2 Abstract Email Validation actions

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	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.

Gmail → Abstract Email Validation

1 Gmail triggers

Slack → Abstract Email Validation

13 Slack triggers

Google Sheets → Abstract Email Validation

2 Google Sheets triggers

HubSpot → Abstract Email Validation

18 HubSpot triggers

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Validate Email Address support batch operations?

Yes. Run Validate Email Address inside a Loop node to process arrays. Tiny Command handles Abstract Email Validation's rate limits automatically so you don't have to throttle manually.

More actions