Verify CRM contacts before automated Gmail follow-up
Re-verify aging CRM contacts before triggering a follow-up email through Gmail so job changes and deactivated corporate domains do not cause hard bounces.
Starts when: CRM deal stage changes or follow-up task becomes due.
Steps
1. CRM follow-up triggered (trigger)
Read the contact email and last-verified timestamp from the CRM.
2. Verify address with ValidReach (http)
POST the contact email to /api/v1/verify/single.
3. Check status (branch)
Branch on data.status.
4. Send or draft Gmail follow-up (action)
Stamp the fresh verification date on the CRM contact and queue the Gmail message.
5. Notify account owner of bad address (action)
Create a CRM task alerting the rep that the contact mailbox is no longer valid.
Connections
- CRM follow-up triggered → Verify address with ValidReach
- Verify address with ValidReach → Check status
- Check status → Send or draft Gmail follow-up (valid)
- Check status → Notify account owner of bad address (invalid, disposable, catchall, unknown)
Credentials you provide
- ValidReach API key
YOUR_API_KEY: Create it under Settings → API keys and store it in your automation tool’s secret storage. - CRM & Gmail connection
CONNECT_YOUR_OWN_ACCOUNT: Connect your CRM and Gmail accounts in your automation runner.
Sample
POST https://validreach.dev/api/v1/verify/single
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
{"email":"user@example.com"}{
"success": true,
"data": {
"email": "user@example.com",
"status": "valid",
"is_deliverable": true,
"reason": "accepted_email",
"credits_used": 1,
"retryable": false
}
}Before you run it
B2B contacts decay over time; re-verifying any contact checked more than 60 days ago prevents sudden bounce spikes on follow-up sequences.
Verification status. Schema: checked in unit tests. Import: not tested on any platform. Sandbox run: not run. The download is this ValidReach definition, not an importable file for an automation platform.