ActionMailgunUpdated September 2026

How do I validate an email via Mailgun?

Short answer: You can mailgun validate email in Mailgun by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Mailgun Mailgun Validate Email 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.

Mailgun Validate Email in Mailgun — start free All 3 Mailgun actions

Mailgun Validate Email in Mailgun — start free

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 Address address	string	Required	Email Address. Example: user@example.com

Sample request

{
  "address": "e.g. user@example.com"
}

Returns

{
  "risk": "low",
  "result": "deliverable",
  "address": "user@example.com",
  "is_role_address": false,
  "is_disposable_address": false
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Mailgun Validate Email.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Mailgun

2 Google Sheets triggers

HubSpot → Mailgun

18 HubSpot triggers

FAQ

Questions about Mailgun Validate Email.

What does the Mailgun Validate Email action do in Mailgun?

SMTP-handshake + DNS + Mailgun-heuristic validation. Returns deliverable/undeliverable/risky/unknown. Useful for in-flow validation before adding to sequences.

What inputs does Mailgun Validate Email require?

Required: Email Address. 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 Mailgun returns an error?

The run history shows the failed step with its input and the error message Mailgun 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 Mailgun Validate Email support batch operations?

Run Mailgun Validate Email 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 Mailgun's rate limits.

More actions

Other Mailgun actions.

Action

Get Mailgun Events

Paginated event log (delivered, opened, clicked, bounced, failed, complained) with filters by date, message-id, recipient. For "did this email actually deliver?" forensics or bulk-export to warehouse.

Action

Mailgun Send Email

Sends transactional or bulk email with HTML/text body, attachments, per-recipient variables for batched personalised sends. The standard hook for "external event → transactional email" patterns.

Mailgun Validate Email in Mailgun — start free