1. Connect a real credential
Import the JSON through n8n's Import from File option. Create an HTTP Header Auth credential with the name Authorization and the value Bearer followed by your LookupLab API key. Select that credential in the LookupLab phone node. The template contains no key.
Open Your phone list and replace the fictional sample with two or three numbers you are authorized to process. The code trims whitespace, removes exact duplicates and caps the input at 100 records. Use E.164 numbers to keep the country explicit.
2. Inspect the first execution
Run manually. The HTTP node uses the number query-parameter field, so + signs are encoded correctly. Requests are batched one at a time with a short interval. Review results extracts number, valid, line_type, carrier, country and meta.charged.
The review column distinguishes lookup_error, invalid, mobile_check_consent and review_channel. It is deliberately a review recommendation. The workflow does not send messages or mutate CRM records.
3. Handle errors without losing context
HTTP errors fail the node instead of generating a reassuring but incorrect result. A 401 means the credential needs attention; 402 means the account needs credits; 429 means slow down. Inspect the execution's partial results before replaying, because completed checks can be charged again.
When you attach this to a CRM trigger, retain the source contact ID alongside the result using n8n's item linking or a merge step. Test multiple records with different line types before enabling scheduled runs. Do not join records solely by list position after filtering or deduplicating.
4. Add only the next useful action
For a sales workflow, update a carrier or line-type property first. Keep unknown and VoIP records available for review rather than automatically deleting legitimate contacts. Your existing consent and opt-out gates should still run before any message.
For email workflows, call /api/v1/email/ with the email parameter and inspect syntax_valid, has_mx, disposable, smtp.attempted and reason. A deliverable_domain reason is a domain-level signal, not mailbox verification. Do not relabel it as verified inbox.
A successful base phone check uses 1-3 credits depending on line type. Caller-name requests use 3-5. Read
meta.charged for the actual debit and test a sample before scaling.Written by LookupLab. Updated October 12, 2026. Implementation reference: n8n HTTP Request documentation.