1. Separate enrichment from sending
Start with a new or changed contact event from HighLevel, Pipedrive or another CRM. Pass the contact ID and phone number to your Make or n8n workflow. Require a valid payload and protect the receiving webhook. Keep a last-checked timestamp to avoid checking the same unchanged record on every update.
Use GET https://lookuplab.io/api/v1/phone/ with a number query parameter and an Authorization: Bearer header. In Make, enable parsed responses and run once to inspect the bundle. Select the returned data.line_type and data.carrier fields from that actual output; module nesting varies by HTTP version.
2. Write back to the same contact
Create CRM fields for line type, carrier, checked-at and lookup status. Use the original contact ID in the CRM update action. A webhook response alone does not necessarily update contact custom fields.
Only set the completed status after you have handled the response. Send API errors to an operational review path. Never mark the number invalid merely because the request timed out or the account ran out of credits.
3. Make routing rules explicit
For mobile, continue to consent, suppression and channel-capability checks. For landline or toll_free, select a channel using your actual provider's capabilities. Some non-mobile numbers can receive messages, so line type alone is not a universal SMS permission switch.
For voip or unknown, choose a review route that matches your customer base. Many legitimate businesses use VoIP. For valid:false, flag the record for correction rather than silently losing the lead. None of these signals proves the subscriber's identity.
4. Test the full path with a small set
Run a known mobile, a known landline, an invalid-format input and a simulated API failure through a test workflow. Confirm that each writes to the intended contact and produces the intended status. Keep all sending steps disabled until those outcomes match your policy.
Log the source record ID, check timestamp and charged credits without copying your API key into logs. Recheck based on your freshness needs: carrier data can change, and repeated successful requests may be billable even when upstream data is cached.
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.