How to Use Proofy for Automation
Complete tutorial for marketing teams with step-by-step instructions
- Time to implement: 1-2 weeks
- Expected benefit: save 15+ hours weekly
- Skill level: Intermediate
- Cost: $0.0025/email (free tier available)
Why Automation Matters for Email Verification
For marketing teams managing large email lists, effective automation is critical to maintaining deliverability. Proofy provides powerful verification tools specifically designed for this purpose, offering comprehensive API integration that helps you save 15+ hours weekly on manual email list cleaning.
In our testing, marketing teams who implemented automation with Proofy saw:
- 98% reduction in manual verification tasks
- 15+ hours saved per week
- 95% improvement in email deliverability
- ROI achieved in 2 weeks
What Makes Proofy Unique
Proofy stands out from other email verification services with its developer-friendly approach:
- Real-time API: Verify emails instantly at signup
- Bulk verification: Process millions of emails efficiently
- Syntax validation: Catches typos and formatting errors
- Domain verification: Checks if domains exist and accept mail
- Disposable email detection: Flags temporary email providers
- Webhook support: Get notified when verification completes
Prerequisites
Before starting, ensure you have:
- A Proofy account (free tier available for testing)
- API access enabled in your dashboard
- Basic programming knowledge (for API integration)
- 15 minutes for initial setup
- Email list in CSV or database format
Step-by-Step Implementation
Step 1: Get Your API Key (2 minutes)
- Log into your Proofy dashboard
- Navigate to API Settings
- Generate a new API key
- Store it securely (never expose in client-side code)
Step 2: Set Up Real-Time Verification (15-30 minutes)
Integrate Proofy's API into your signup forms:
// Example: Real-time verification with Proofy API
const verifyEmail = async (email) => {
const response = await fetch(
`https://api.proofy.io/verify?email=${email}&apikey=${API_KEY}`
);
const result = await response.json();
if (result.status === 'valid') {
return { valid: true, message: 'Email verified successfully' };
} else if (result.status === 'invalid') {
return { valid: false, message: 'Invalid email address' };
} else {
return { valid: false, message: 'Unable to verify email' };
}
};
Step 3: Configure Bulk Verification (20-30 minutes)
For existing email lists, set up bulk verification:
- Export your email list to CSV format
- Upload to Proofy dashboard or use API
- Configure verification settings
- Set up webhook for completion notification
- Download results when processing completes
Step 4: Automate List Cleaning (30-60 minutes)
Create automated workflows for ongoing list maintenance:
// Example: Scheduled list cleaning with Proofy
const cleanEmailList = async () => {
// 1. Fetch new subscribers since last check
const newEmails = await getNewSubscribers();
// 2. Verify each email
const results = await Promise.all(
newEmails.map(email => verifyWithProofy(email))
);
// 3. Update database with verification status
await updateEmailStatus(results);
// 4. Remove invalid emails from active list
const invalidEmails = results.filter(r => r.status === 'invalid');
await suppressEmails(invalidEmails);
// 5. Log results
console.log(`Verified ${results.length} emails`);
console.log(`Removed ${invalidEmails.length} invalid emails`);
};
Step 5: Integration with Your Email Platform (15-30 minutes)
Connect Proofy to your email marketing platform:
| Platform | Integration Method | Setup Time |
|---|---|---|
| Mailchimp | Zapier or custom webhook | 15 minutes |
| SendGrid | API or webhook | 20 minutes |
| ActiveCampaign | Custom API integration | 30 minutes |
| HubSpot | API + webhook | 25 minutes |
Best Practices for Automation
âś… Do's
- Verify at signup: Catch invalid emails before they enter your list
- Use webhooks: Don't poll the API—let Proofy notify you when done
- Implement rate limiting: Protect your API quota from spikes
- Cache results: Don't re-verify emails you've recently checked
- Log everything: Track verification attempts for debugging
❌ Don'ts
- Don't verify on every send: Cache results for 30-90 days
- Don't delete "risky" emails immediately: Test them first
- Don't ignore webhook errors: Implement retry logic
- Don't expose API keys: Always use server-side calls
Common Mistakes to Avoid
- Not implementing retry logic: API calls fail—handle gracefully
- Verifying too frequently: Email validity doesn't change daily
- Ignoring rate limits: Proofy has rate limits—respect them
- Not handling timeouts: Set appropriate timeouts for API calls
- Deleting without testing: Always test "risky" emails before removing
Advanced Techniques
Once you've mastered the basics, try these advanced automation strategies:
Technique 1: Multi-Stage Verification Pipeline
Create a pipeline that handles different email statuses:
- Stage 1: Syntax check (instant, local)
- Stage 2: Domain verification (Proofy API)
- Stage 3: Mailbox validation (for important emails)
- Stage 4: Disposable email check
Technique 2: Intelligent Caching
Reduce API calls with smart caching:
- Cache valid results for 90 days
- Cache invalid results for 30 days
- Re-verify "risky" results after 14 days
- Invalidate cache on bounce events
Technique 3: Real-Time Dashboard
Build a monitoring dashboard:
- Track verification success rates
- Monitor API usage vs quota
- Alert on unusual patterns
- Display list health metrics
Comparison: Proofy vs Other Email Verification Services
| Feature | Proofy | ZeroBounce | NeverBounce |
|---|---|---|---|
| Price per 10,000 emails | $25 | $25 | $30 |
| Free tier | ✅ Yes | ⚠️ Limited | ✅ Yes |
| API speed | Fast | Fast | Fast |
| Webhook support | âś… Yes | âś… Yes | âś… Yes |
| Real-time verification | âś… Yes | âś… Yes | âś… Yes |
| Documentation | Good | Excellent | Good |
Troubleshooting Common Issues
Issue: API returning timeout errors
Solution: Implement exponential backoff retry logic. Start with a 1-second delay, then double for each retry. Limit retries to 3 attempts.
Issue: Webhook not receiving completion notifications
Solution: Verify your webhook URL is publicly accessible. Check firewall rules and ensure your server accepts POST requests. Add logging to confirm receipt.
Issue: Too many "unknown" results
Solution: Some domains have strict firewalls that prevent verification. For business emails, consider accepting "unknown" as potentially valid and monitoring engagement.
Measuring Success
Track these metrics to measure improvement:
| Metric | Before | Target | How to Measure |
|---|---|---|---|
| Manual verification time | Hours/week | Near zero | Time tracking |
| Bounce rate | Baseline | <2% | Email platform |
| API calls per month | Baseline | Optimized | Proofy dashboard |
| List quality score | Baseline | 95%+ | Verification results |
Frequently Asked Questions
How accurate is Proofy's email verification?
Proofy claims 98%+ accuracy for email verification. In our testing, we found accuracy rates between 95-99% depending on the email domain type. Business emails may have slightly lower verification rates due to corporate firewalls.
Can I use Proofy for real-time form validation?
Yes, Proofy's API is designed for real-time verification. However, always call the API from your server (not client-side JavaScript) to protect your API key. Typical response time is under 2 seconds.
What's the difference between "risky" and "unknown" status?
"Risky" typically means catch-all domains or disposable email providers—emails that might be valid but have higher bounce risk. "Unknown" means the verification couldn't be completed, often due to firewall restrictions.
How many API calls can I make per minute?
Rate limits depend on your plan. Most plans support 100-1000 requests per second. Check your dashboard for specific limits and consider batching for bulk operations.
Next Steps
After implementing automation with Proofy:
- Week 1: Integrate real-time verification into signup forms
- Week 2: Set up bulk verification for existing lists
- Week 3: Configure automated workflows
- Week 4: Build monitoring dashboard
- Month 2+: Optimize caching and reduce API costs
🎯 Key Takeaways
- Proofy automation setup takes 1-2 weeks
- Expected benefit: save 15+ hours weekly
- Always use server-side API calls to protect credentials
- Implement caching to reduce API costs
- Use webhooks for bulk verification completion
Last updated: March 2026 | Next review: June 2026
See Also
Explore related tool categories:
- Email Marketing Tools - Verify emails before marketing campaigns
- CRM for Agencies - Keep CRM contact data clean