Short answer: Drop the "Abstract Email Validation → Email Reputation Check" 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 | Email address to check reputation for |
{"email": "e.g. user@example.com"}
{"email_domain": {"domain": "gmail.com","registrar": "MarkMonitor Inc.","domain_age": 11229,"is_live_site": true},"email_sender": {"last_name": null,"first_name": null,"organization_name": "Gmail","organization_type": "commercial","email_provider_name": "Google"},"email_address": "ok@gmail.com","email_deliverability": {"status": "deliverable","mx_records": ["gmail-smtp-in.l.google.com"],"is_mx_valid": true,"is_smtp_valid": true,"status_detail": "valid_mailbox","is_format_valid": true}}
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.