Verify a customer’s address before a welcome email

1. 1. Deal won (trigger)

   Read the contact’s email address from the deal.

2. 2. Verify address (http)

   POST the address to /api/v1/verify/single.

3. 3. Check status (branch)

   Branch on data.status.

4. 4. Draft welcome email (action)

   Create a welcome email draft for the account owner to review.

5. 5. Flag for follow-up (action)

   Add a task or note: the address needs correcting.

• Deal won → Verify address
• Verify address → Check status
• Check status → Draft welcome email (valid, catchall, role)
• Check status → Flag for follow-up (invalid, disposable, risky, unknown)

• ValidReach API key YOUR_API_KEY: Create it under Settings → API keys and store it in your automation tool’s secret storage.
• CRM connection CONNECT_YOUR_OWN_ACCOUNT: Use your own CRM connection with read access to deals and contacts.
• Mail connection CONNECT_YOUR_OWN_ACCOUNT: Use your own mailbox; create drafts while testing.

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
  }
}

Test with a sandbox or dummy deal. The branch routing above is a suggested default, so change it to match your policy.

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.