Getting Started
Welcome to MyEmailVerifier's Zapier integration! This guide will help you automate email verification across thousands of apps.
What You'll Need
- MyEmailVerifier Account: Sign up here if you don't have one
- Zapier Account: Free or paid plan (depending on your usage)
- API Key: Available in your MyEmailVerifier dashboard
How It Works
The MyEmailVerifier Zapier integration allows you to verify email addresses in real-time as part of your automated workflows. Here's the basic flow:
- Trigger: An event happens in another app (e.g., new form submission)
- Action: MyEmailVerifier validates the email address
- Result: You receive verification data (status, diagnosis, flags, etc.)
- Next Steps: Use filters or paths to route data based on verification results
Note: Each email verification via Zapier counts as one task in Zapier and consumes one credit from your MyEmailVerifier account.
Authentication
Finding Your API Key
Your API key is required to connect MyEmailVerifier to Zapier:
- Log in to your MyEmailVerifier Dashboard
- Navigate to Settings → API Keys
- Click "Generate New Key" if you don't have one
- Copy your API key (it looks like:
mev_1234567890abcdef)
Security Warning: Keep your API key secret! Don't share it publicly or commit it to version control. If compromised, regenerate it immediately from your dashboard.
Connecting to Zapier
When setting up your first Zap with MyEmailVerifier:
- Add MyEmailVerifier as an action step
- Click "Sign in to MyEmailVerifier"
- Paste your API key in the authentication field
- Click "Yes, Continue"
- Zapier will test the connection automatically
Success! Once authenticated, you can use MyEmailVerifier in any Zap without re-entering your API key.
Complete Setup Guide
1Create a New Zap
From your Zapier dashboard:
2Set Up Trigger
Choose the app and event that will start your workflow:
- Example: Google Forms → New Response
- Example: Facebook Lead Ads → New Lead
- Example: Shopify → New Customer
Configure and test your trigger to ensure it pulls sample data correctly.
3Add MyEmailVerifier Action
- Click the + button to add an action
- Search for "MyEmailVerifier"
- Select "Verify Single Email" as the action event
- Connect your account (see Authentication section)
4Configure Email Field
In the action configuration:
- Click the "Email" field
- Select the email address from your trigger step
- You can also type a static email for testing
Example Field Mapping:
Email: {{1. Email Address}}
(Where "1" is your trigger step number)
5Test the Action
Click "Test action" to verify an email. You should see results like:
{
"Address": "
[email protected]",
"Status": "Valid",
"Diagnosis": "Mailbox exists and active. Safe to send (D2)",
"catch_all": 0,
"Free_Domain": 0,
"Disposable_Domain": 0,
"Role_Based": 0,
"Greylisted": 0
}
6Add Next Steps
Use the verification results in subsequent actions:
- Add a Filter to only continue if status is "valid"
- Use Paths to route different statuses differently
- Send data to your CRM, email marketing platform, or spreadsheet
7Turn On Your Zap
Once testing is complete:
- Click "Publish" or toggle the Zap ON
- Monitor the first few runs to ensure accuracy
- Check your MyEmailVerifier Dashboard to track usage
Field Mapping Guide
Input Field
| Field Name |
Required |
Description |
Email |
Yes |
The email address to verify. Map this from your trigger step. |
Output Fields
MyEmailVerifier returns the following data that you can use in subsequent steps:
| Field Name |
Type |
Description |
Example Values |
email |
String |
The email address that was verified |
[email protected] |
status |
String |
Overall verification status |
valid, invalid, disposable, catchall, unknown |
reason |
String |
Detailed explanation of the status |
"Accepted email", "Invalid domain", "Disposable email detected" |
Diagnosis |
String |
Detailed mailbox validation explanation |
"Mailbox exists and active. Safe to send (D2)" |
free_email |
Boolean |
Is this a free email provider? |
true (Gmail, Yahoo), false (corporate) |
disposable |
Boolean |
Is this a temporary/disposable email? |
true, false |
role_account |
Boolean |
Is this a role-based email? |
true (info@, support@), false |
catch_all |
Boolean |
Does the domain accept all emails? |
true, false |
mx_records |
Boolean |
Does the domain have MX records? |
true, false |
smtp_check |
Boolean |
Did SMTP verification succeed? |
true, false |
Using Filters & Paths
Basic Filtering
Add a "Filter by Zapier" step after MyEmailVerifier to only continue for certain results:
Example: Only Continue for Valid Emails
Condition: Status (exactly matches) valid
Advanced Filtering
Use multiple conditions to create sophisticated filters:
Condition 1: Status (is in) "valid,catchall"
Condition 2: Disposable (is false)
Condition 3: Free_Domain (is) 0
Logic: ALL conditions must be true
Using Paths
Create different workflows based on verification results:
- Path A - Valid Emails: Add to Mailchimp + Send welcome email
- Path B - Catch-all Emails: Add to "Review" list + Alert team
- Path C - Invalid Emails: Log to spreadsheet + Mark as rejected
Common Filter Scenarios
| Use Case |
Filter Condition |
| Only accept valid emails |
Status exactly matches valid |
| Block disposable emails |
Disposable is false |
| Only corporate emails |
Free Email is false |
| High-quality leads only |
Status exactly matches valid |
| Exclude role accounts |
Role Account is false |
| Accept valid or catch-all |
Status is in valid,catchall |
Understanding Verification Results
Status Values Explained
valid
Meaning: The email address exists and can receive emails.
Recommendation: Safe to add to your list and send emails.
Example: [email protected] (verified inbox)
invalid
Meaning: The email address doesn't exist or has syntax errors.
Recommendation: Don't add to your list. Will cause bounces.
Example: [email protected], [email protected]
catchall
Meaning: The domain accepts all emails, even if mailbox doesn't exist.
Recommendation: Use with caution. May or may not be deliverable.
Example: [email protected]
unknown
Meaning: Unable to verify (server timeout, greylisting, etc.).
Recommendation: Add to review queue for manual check.
Example: [email protected]
Status Interpretation
| Status |
Meaning |
Recommendation |
| valid |
Mailbox exists |
Safe to add to your list. |
| catchall |
Accept-all domain |
Use caution and monitor engagement/bounces. |
| disposable |
Temporary inbox |
Block from core lists. |
| invalid |
Mailbox not deliverable |
Do not send. |
| unknown |
Temporary issue |
Retry later or review manually. |
Best Practices
1. Use Filters Wisely
- Always filter out
invalid and disposable emails
- Consider your use case when handling
catchall emails
- Set status/diagnosis rules based on your quality requirements
2. Monitor Your Credit Usage
- Set up low-balance alerts in your MyEmailVerifier dashboard
- Monitor Zapier task consumption to optimize costs
- Use Zapier's built-in filters to avoid unnecessary verifications
3. Handle Different Email Types
- Free emails (Gmail, Yahoo): Valid for B2C, lower quality for B2B
- Role accounts (info@, support@): Valid but not personal contacts
- Disposable emails: Always block these
- Corporate emails: Highest quality for B2B use cases
4. Implement Multi-Path Workflows
Don't just accept or reject - create intelligent routing:
- Valid + Safe Diagnosis: Add to main list + trigger welcome sequence
- Valid + Caution Diagnosis: Add to secondary list for monitoring
- Catch-all: Add to review queue for manual verification
- Invalid: Log to rejected list for analysis
5. Test Before Going Live
- Test your Zap with various email types (valid, invalid, disposable)
- Verify that filters work as expected
- Check that data flows to the correct destinations
- Monitor the first 10-20 live runs closely
6. Optimize for Speed
- Email verification typically takes 2-5 seconds
- Keep your Zaps simple to minimize total execution time
- Use parallel paths instead of sequential steps when possible
Pro Tip: Create separate Zaps for high-priority vs. bulk processing. This allows you to allocate resources efficiently and ensures critical verifications happen quickly.
Troubleshooting
Common Issues & Solutions
Error: "Invalid API Key"
Cause: API key is incorrect or has been regenerated.
Solution:
- Check your MyEmailVerifier Dashboard for the correct API key
- In Zapier, disconnect and reconnect your MyEmailVerifier account
- Enter the correct API key when prompted
Error: "Insufficient Credits"
Cause: Your MyEmailVerifier account is out of verification credits.
Solution:
- Add credits to your account or upgrade your plan
- Your Zap will resume automatically once credits are available
- Set up low-balance alerts to prevent this in the future
Zap is Skipping Some Emails
Cause: Filter conditions are too restrictive.
Solution:
- Check your Zapier filter settings
- Review the Zap history to see why emails were filtered out
- Adjust filter conditions or use Paths instead of Filters
Slow Verification Times
Cause: Some email servers take longer to respond.
Solution:
- This is normal for certain domains with strict security
- Most verifications complete in 2-5 seconds
- If consistently slow (>15 seconds), contact support
Getting "Unknown" Status Frequently
Cause: Email servers using greylisting or blocking verification attempts.
Solution:
- Create a separate path for "unknown" statuses
- Add these to a review queue for manual verification
- Consider re-verifying after 24-48 hours
Getting Support
If you need additional help:
When Contacting Support, Please Include:
- Your MyEmailVerifier account email
- Zap ID or link to your Zap
- Screenshot of the error message
- Sample email that failed verification (if applicable)
Frequently Asked Questions
You pay separately for both services:
- MyEmailVerifier: Based on your subscription plan. Each verification consumes one credit.
- Zapier: Based on your Zapier plan. Each Zap run counts as a task (free plans include 100 tasks/month).
There are no additional integration fees.
Yes! Add multiple MyEmailVerifier action steps - one for each email field you want to verify. Each verification will consume one credit and count as a separate action in your Zap.
Your Zaps will stop working and you'll receive error notifications. To fix: disconnect and reconnect your MyEmailVerifier account in Zapier with the new API key. All your existing Zaps will automatically use the new key.
The Zapier integration is designed for real-time, one-by-one verification. For bulk verification of existing lists (thousands of emails), use our web dashboard or bulk API instead. However, you can use Zapier's "Looping" feature to verify multiple emails from a spreadsheet sequentially.
MyEmailVerifier uses multiple verification methods including syntax validation, domain verification, MX record checks, and SMTP validation. Our accuracy rate is 99%+ for most emails. Some emails may return "unknown" status due to server restrictions or greylisting.
Yes! MyEmailVerifier supports international email addresses and domains from all countries. We handle international characters, country-specific TLDs, and various email formats globally.