n8n — WhatsApp Profile API

Setup

1. Add node → HTTP Request.
2. Configure:
   • Authentication: Generic Credential Type → Header Auth
   • Header (direct proxy): x-rapidapi-key: YOUR_DIRECT_KEY — single header. Direct-purchase key from our dashboard.
   • Header (RapidAPI marketplace): add a second header x-rapidapi-host: whatsapp-data1.p.rapidapi.com AND change URL host below.
   • Method: GET
   • URL: https://whatsapp-proxy.checkleaked.cc/number/{{ $json.phone }} (digits only, no +). For RapidAPI: https://whatsapp-data1.p.rapidapi.com/number/{{ $json.phone }}.
   • Response → Response Format: JSON
3. Execute — downstream nodes receive the parsed JSON.

Batch processing pattern

For n8n bulk runs, use the SplitInBatches node before the HTTP Request to cap concurrency and respect the per-tier burst limit:

1. Read data — e.g. Google Sheets or Postgres.
2. SplitInBatches — batch size = your tier's burst limit (2 for BASIC/PRO/ULTRA, 4 for MEGA).
3. HTTP Request — WhatsApp Profile API lookup.
4. Merge / Aggregate — combine results back into a single dataset.
5. Write back — update source or route to CRM.

Self-hosted considerations

• Store the API key in n8n's encrypted credentials store, not as a plain env var.
• Enable the HTTP Request node's built-in retry: Continue On Fail + Retry On Fail with 5 retries and exponential backoff.
• For high-volume production workflows, use the dedicated MEGA-tier endpoint for lower latency.

Related