Description
n8n-nodes-listar
This is an n8n community node for Listar. It finds the phone numbers and emails of professionals, and the decision makers of companies, inside your n8n workflows.
n8n is a fair-code licensed workflow automation platform.
- Installation
- Operations
- Credentials
- Usage
- Pricing
- Compatibility
- Resources
- n8n community nodes documentation
- Listar API reference
- Listar
Installation
Follow the installation guide in the n8n community nodes documentation. In short: Settings > Community Nodes > Install, then enter n8n-nodes-listar.
Operations
| Resource | Operation | What it does |
| ————- | —————– | ———————————————————————————————————————————— |
| Person | Enrich | Finds the phone number, email and/or LinkedIn profile (current job title and company) of a person from their name, company, city… |
| Person | Get Result | Fetches the result of a person enrichment launched earlier |
| Person | Report Wrong Data | Reports a delivered phone or email as wrong: never delivered nor billed to you again for that person |
| Company | Enrich | Returns the company info (register data, domain, industry, headcount…) and its decision makers (name, job title, LinkedIn profile) |
| Company | Get Result | Fetches the result of a company enrichment launched earlier |
| People Search | Search | Finds the people who hold a role without knowing their company (titles, place, seniority, company size), and who just took the job |
| People Search | Get Result | Fetches the result of a people search launched earlier |
| Email | Verify | Checks whether an email address can receive mail |
| Phone | Verify Ownership | Checks whether a phone number belongs to a given person |
| Phone | Check WhatsApp | Checks whether a phone number has a WhatsApp account |
| Credit | Get Balance | Returns the remaining Listar credit |
The node can also be used as a tool by n8n AI agents.
Credentials
1. Create a Listar account at listar.fr.
2. Open Settings > API keys (direct link) and create a key. It is shown only once.
3. In n8n, create a Listar API credential and paste the key. The connection test reads your credit balance.
Usage
Enrich a list of people
Read your list (Google Sheets, CSV, CRM…), then add a Listar node with Person > Enrich. Search By sets what identifies the person and makes its fields required: the name (first and last name), the LinkedIn profile (the strongest identifier), a known email (to find the phone) or a known phone (to find the email). Every other known detail goes in Additional Fields: add at least the company to a name, a bare name is often not enough to deliver anything.
Data to Find limits the search to the phone or the email: only the requested channel is delivered and billed. The person’s LinkedIn profile comes free with every search: its URL, current job title and company (currentJobTitle, currentCompany, positionObservedAt). LinkedIn Profile Only runs no phone or email search, to qualify a list of people cheaply: it is billed only when it tells something the item did not carry (a found URL, a job title or a company).
Waiting for results
Most searches complete within a minute, some take a few minutes. By default the node waits for each result, up to Max Wait (Seconds). A search still running when the wait runs out is not lost: the item comes out with status: "pending" and the search id, and the Get Result operation fetches it later. It is billed once, when it completes.
For large lists, turn Wait for Result off: every search is launched at once and returns its ID. Then add a Wait node (a few minutes) followed by a Listar node with Get Result on {{ $json.id }}. At most 20 company searches can run at the same time per account: a launch beyond that is retried automatically after the delay the API asks for, then fails if the limit is still reached.
From a company to its contacts
Company > Enrich returns the decision makers of a company, without their phone or email. Split the contacts array (Split Out node), then run Person > Enrich on each contact, searched by its linkedinUrl (or by its first and last name), with the company name in Additional Fields.
Company > Enrich works the same way: Search By picks the required identifier (company name, domain, SIREN or SIRET), the others go in Additional Fields. Phone > Verify Ownership checks the number against a name or a LinkedIn profile.
Who just took a job
People Search > Search finds the people who hold a role without knowing their company. Give a Brief in plain words (a judge reads it to keep only the people who really hold the role), every form of the Job Titles (French and English, both genders, the acronyms: each one is matched as whole words), the Countries, and Started Within (Days) to keep only who just took the job: 60 for the last two months. The people come without phone or email, saved in a Listar list (listId): split the people array and run Person > Enrich on each linkedinUrl, or enrich the list in the Listar app. A search of a few hundred people takes a few minutes: raise Max Wait, or collect it later with Get Result. At most 3 people searches run at the same time per account: a launch beyond that fails at once instead of waiting. With Simplify on, stopReason and sourceFailed say why a list is short: only exhausted means there is nobody else.
A wrong number
A delivered number belongs to someone else, an email bounces: Person > Report Wrong Data with the result id (or the id of a row of a bulk enrichment), the issues, and the wrong values in Phones / Emails (empty: every number or email of the result). Free. For a year, those values are never delivered nor billed to you again for that person: run Person > Enrich again to get another number, billed only if one is found.
Output
With Simplify on (default), a person result is one flat item: phone, phoneType, phoneUsage (professional / personal), email, emailStatus, and so on. Turn it off to get the full API response.
Errors
When the Listar credit does not cover a request, nothing is delivered and the node stops with a clear message that gives the search ID. Top up in the app: a result already found is settled automatically and can then be fetched with Get Result and that ID. With Continue on error, the error item keeps the search id too. Turn on Settings > On Error > Continue to keep processing the other items.
Do not turn on Retry On Fail for the Enrich operations: a retried launch is a new search, billed again.
Pricing
Every operation is billed to the Listar credit of the organization that owns the API key, at the same prices as the Listar API. An enrichment that finds nothing is not billed. Verifications are billed per checked number or email, as described in the API reference.
Compatibility
Tested with n8n 2.x.
