Lee este artículo en español.

How to validate a phone number in Make (HTTP module)

If you automate lead or order intake with Make, at some point you need to check that a phone number is real and put it in a consistent format (every customer types it differently). With the HTTP module and the Cofferdock API, you handle it in one step.

An honest heads-up: Make has no dedicated "validate phone" module. You do it with the generic HTTP module calling an API that recognizes the country, the number type (mobile, landline...) and returns it already formatted.

What you'll get

You send the phone number and it tells you whether it's valid, which country it belongs to, what type it is (mobile, landline...), and returns it already formatted in E.164 (the standard used by SMS gateways) and in readable international format.

Common uses in Make:

• Filtering leads with fake phone numbers before creating them in your CRM.
• Normalizing phone numbers typed a dozen different ways before sending them to an SMS gateway.
• Checking an order's phone number before confirming it.
• Detecting when a contact gave a landline when you asked for a mobile.

What you need

• A Cofferdock account. The free tier gives you 50 uses/month with no card.
• Your API key, from your dashboard with "+ Create key". It's shown only once.
• The HTTP → Make a request module in your scenario.

Step by step in the HTTP module

Add the HTTP → Make a request module and set it up like this:

• URL: https://api.cofferdock.com/validate-phone
• Method: POST
• Headers: add two → x-api-key with your key, and Content-Type with the value application/json.
• Body type: Raw
• Content type: JSON (application/json)
• Request content:

{ "phone": "{{1.phone}}" }

• Turn on Parse response: the response is JSON.

The response includes valid, country, type, formatted_e164 and formatted_international. With a Set variable module you can keep just the formatted phone number for the rest of the scenario.

A quick example

Say you normalize phone numbers before storing them in your CRM:

1. A module that catches the lead (a webhook from a form) with the phone number exactly as the customer typed it.
2. The HTTP module above, which validates and formats it.
3. A module for your CRM that stores formatted_e164 instead of the raw text, so every phone number ends up in the same format.

Never again a phone number stored three different ways.

If the phone number has no international prefix

If your customers type the number "locally" (no +1, +34, etc. in front), add a default country in the same body:

{ "phone": "{{1.phone}}", "country": "US" }

Prefer to see it in code?

The same call with curl:

curl -X POST "https://api.cofferdock.com/validate-phone" \
  -H "x-api-key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"phone": "2025550123", "country": "US"}'

How much does it cost?

Each check uses 1 credit from your plan, whether the phone number comes back valid or not. Every Cofferdock tool draws from the same pool of credits.

FAQ

Does Make have a native module to validate phone numbers? No. You do it with the generic HTTP module calling the Cofferdock API.

What happens if I don't send country and the number has no +? The module can't guess the country and the number comes back invalid. Always send country if your users don't type the international prefix.

What does type mean? When it can be determined, it tells you whether the number is MOBILE, FIXED_LINE, VOIP, etc. Useful for filtering out landlines when you need to send an SMS.

Can I validate several phone numbers at once? Yes. If the previous module returns several items, Make runs the HTTP module once per item.

Related guides

• Validate an email in Make
• Validate an IBAN in Make

Try it yourself

You'll find the full instructions, with copy-paste examples, on the phone validation page. And if you don't have an account yet, you can create one for free and build your first scenario today.