Contact enrichment is a complex, synchronous process that queries multiple providers in a cascading sequence.
To ensure your workflow doesn’t fail if the lookup takes time, you must use a specific combination of two nodes: HTTP Request and Wait.
How to do :
Step-by-step guide
Workflow logic:
You must configure your flow in this exact order:
HTTP Request node: Sends the profile to Zeliq and tells n8n where to wait for the response.
Wait node: Pauses the workflow until Zeliq returns the data it found.
Step 1: The HTTP Request node (Sending)
Configure this node to send the request.
Method: POST
URL:
https://api.zeliq.com/api/v1/enrich/phoneAuthentication: Generic Credential Type → Header Auth (
Authorization: Bearer YOUR_API_KEY)
⚠ Required parameter (Body): In the Send Data section (JSON format), you must include the LinkedIn profile URL and the special n8n variable for the callback.
Copy this JSON:
{ "linkedinProfileUrl": "{{ $json.linkedinUrl }}", "callback_url": "{{ $execution.resumeUrl }}" }
Step 2: The Wait node (Receiving)
Connect this node directly after the HTTP request.
Resume: Choose On Webhook Call
Limit Wait Time: Enable this option and set it to 2 hours
Why? Enrichment can be instant or take time depending on the complexity of the lookup. A 2-hour buffer ensures n8n won’t close the connection prematurely, even if the network is slow.
Once Zeliq finds the phone number or email, the Wait node resumes and outputs the enriched data (phone number, status), which you can then use in the rest of your workflow.
Important note
Check your workflow settings and make sure “Timeout Workflow” is either disabled or set to a duration greater than 2 hours.
ChatGPT peut commettre des erreurs. OpenAI n’utilise pas les données de l’espace de travail Zeliq pour entraîner ses modèles.