ActionAbstract Email ValidationUpdated September 2026
What is the reputation score for this email address?
Short answer: You can email reputation check in Abstract Email Validation by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Abstract Email Validation Email Reputation Check 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 | Email address to check reputation for |
Sample request
{"email": "e.g. user@example.com"}
Returns
{"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.
Triggered by
Apps that pair well as the trigger for Email Reputation Check.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Email Reputation Check.
What does the Email Reputation Check action do in Abstract Email Validation?
Returns a 0-1 reputation score indicating how likely the email belongs to a real, active human inbox versus a throwaway, role, or abuse-prone address. Higher scores correlate with deliverability and engagement; use 0.3 as a soft pre-flight threshold before adding to outbound sequences.
What inputs does Email Reputation Check 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 Email Reputation Check support batch operations?
Run Email Reputation Check 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