Skip to content

Verify leads inside Make scenarios.

Screen emails, phone carriers, and WhatsApp numbers in five Make modules.

Dedicated Make base endpoint https://proweblook.com/api/v1/make

Authenticates with your ProWebLook API key in an encrypted Make connection. Testing your connection calls Get balances for free.

Set up ProWebLook in Make in four steps

Connects using Bearer API key authentication over HTTPS with strict no-store JSON responses.

  1. Create or sign in to ProWebLook

    Open your ProWebLook profile to copy your API key. New accounts start with 50 one-time free credits across email, phone, and WhatsApp.

    Create free ProWebLook account
  2. Add a ProWebLook module in Make

    Add Verify an email, Validate a phone number, Validate a WhatsApp number, Get balances, or Make an API call inside your Make scenario.

  3. Save your encrypted connection

    Click Add next to Connection and paste your ProWebLook API key. Make validates the key immediately against the free Get balances endpoint.

  4. Route clean bundles with a Make Router

    Filter output bundles on verdict equals deliverable, valid, or on_whatsapp before syncing leads into HubSpot, Pipedrive, Google Sheets, or Slack.

Five visual modules built for clean scenario routing

Completed negative or catch-all checks return normal Make bundles rather than throwing runtime errors, keeping multi-bundle runs intact.

Verify an email

1 email credit per completed verdict

Validates syntax, domain MX records, and mailbox status. Outputs deliverable, undeliverable, or unknown (including catch-all domains).

Email Verification API

Validate a phone number

Up to 1 phone credit per check

Accepts international E.164 strings or national numbers paired with a two-letter ISO country code. Returns carrier, location, and Mobile vs VoIP line type.

Phone Number Validator

Validate a WhatsApp number

Up to 1 WhatsApp credit per check

Checks whether an international + phone number is active on WhatsApp or WhatsApp Business without sending any message or OTP.

WhatsApp Number Checker

Get balances & Make an API call

0 credits for Get balances

Monitor email, phone, and WhatsApp credit pools on a schedule, or invoke relative /api endpoints through the universal Make an API call module.

API Playground

Copyable Make filter & HTTP request configs

Use these exact field mappings and cURL smoke tests when building scenarios or testing your API key.

Two-stage Router filter (Email then WhatsApp)

Place a Make Router after Verify an email so Validate a WhatsApp number only runs on deliverable leads.

Route 1 (Qualified Email):
  Condition: {{2.verdict}} Equal to (case-sensitive) deliverable
  Next module: ProWebLook - Validate a WhatsApp number
    phone_number: {{toString(1.phone)}}

Route 2 (Quarantine):
  Fallback route: Yes
  Next module: Google Sheets - Add a Row (Bounce Log)

Block VoIP & invalid numbers before SMS OTP

Check both verdict and details.linetype after Validate a phone number.

Filter name: Confirmed Mobile or Fixed Line
Condition 1: {{2.verdict}} Equal to valid
AND
Condition 2: {{2.details.linetype}} Not equal to (case-insensitive) VoIP
Normalized E.164 output: {{2.details.formatted_number}}

Smoke-test the Make adapter with cURL (0 credits)

Confirm your API key and inspect live credit pools before running a paid scenario.

curl -X POST https://proweblook.com/api/v1/make/get_balance \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

Frequently asked questions

Does testing my ProWebLook connection in Make spend credits?

No. Connection verification calls POST /api/v1/make/get_balance with an empty JSON object {}, which is free and returns your current email, phone, and WhatsApp credit balances.

Why should phone numbers be mapped as text strings in Make?

Spreadsheets and webhook parsers sometimes coerce phone numbers into integers, stripping the leading + sign or leading zero. Wrapping mapped values in toString() preserves E.164 formatting required by Validate a WhatsApp number.

What is the rate limit on the Make integration surface?

Each enabled ProWebLook account can send up to 60 requests per fixed minute across the Make adapter (isolated in its own make-rate bucket). HTTP 429 responses include Retry-After: 60 before any provider call is dispatched.

How should I configure Break or automatic error retries in Make?

Avoid blind automatic retries on 5xx or network timeout errors for paid verification modules. Because an upstream timeout cannot prove a check did not complete, inspect Get balances before replaying incomplete executions.

Does ProWebLook log my scenario IDs or customer contact fields in plugin analytics?

No. Shared plugin telemetry records only canonical account ID, literal platform make, operation name, outcome category, latency, and timestamp for 90 days. Scenario IDs, API keys, and checked emails or phone numbers are never stored.

Automate lead verification across every Make scenario

Sign up free for 50 email, phone, and WhatsApp credits and connect ProWebLook to hundreds of apps in Make.