Make phone and email validation

Why validate inside Make

Use Make when your lead source and CRM already live there. Call the phone endpoint, inspect the returned data, and write fields back to the same contact before choosing a communication channel.

Build an error route separately from your invalid-number route. A 402 or 429 response is an account or capacity issue, not evidence that the lead supplied a bad phone.

Setup

1. Start with a manual test or a single lead event. Carry the CRM contact ID and phone field through the scenario.
2. Add HTTP > Make a request. Use GET https://lookuplab.io/api/v1/phone/ and add a query parameter named number mapped to the phone field. Use a parameter field to preserve the leading +.
3. Set the Authorization header to Bearer YOUR_API_KEY. Enable response parsing. Keep the key in your connection or protected scenario configuration.
4. Run once. Inspect the HTTP output, then map data.valid, data.line_type, data.carrier and meta.charged. Module output paths vary by Make HTTP version, so map from the observed bundle.
5. Add a Router: invalid results go to review; mobile results continue to consent checks; every other type goes to a separate channel-review route. Add an error handler for non-200 responses.
6. Use your CRM module to update the original contact by ID. Do not send a message during the first test.

Walk through the complete workflow.
See the setup, sample output and review rules →

Phone validation is not consent, ownership verification or guaranteed delivery. Email syntax and MX checks establish domain-level signals, not proof that a particular mailbox exists.

What teams build with it

• Enrich Pipedrive records without changing contact identity.
• Write line type into a CRM custom field.
• Keep API errors separate from invalid data.

Related: Zapiern8nSlack