Verify leads from a web form before they reach your CRM

1. 1. Form submitted (trigger)

   Receive the submission and read the email field.

2. 2. Verify address (http)

   POST the address to /api/v1/verify/single from your server or automation tool.

3. 3. Check status (branch)

   Branch on data.status.

4. 4. Create contact (action)

   Create the CRM contact and store the status.

5. 5. Create tagged contact (action)

   Create the contact with an “unverified” tag.

6. 6. Ask for a correction (action)

   Show or send a message asking for a corrected address.

• Form submitted → Verify address
• Verify address → Check status
• Check status → Create contact (valid)
• Check status → Create tagged contact (unknown, catchall, risky, role)
• Check status → Ask for a correction (invalid, disposable)

• 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 permission to create contacts.

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

Never put the API key in browser code; run the verification step on a server or inside your automation tool. If verification fails, accept the lead and tag it rather than losing it.

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.