Actions45
- Evento Actions
- Criar Evento De Acesso Concedido
- Criar Evento De Aguardando Pagamento
- Criar Evento De Boleto Impresso
- Criar Evento De Carrinho Abandonado
- Criar Evento De Nota Nps
- Criar Evento De Pacote Aguardando Retirada
- Criar Evento De Pacote Saiu Para Entrega
- Criar Evento De Pedido Cancelado
- Criar Evento De Pedido Despachado
- Criar Evento De Pedido Entregue
- Criar Evento De Pedido Estornado
- Criar Evento De Pedido Pago
- Criar Evento De Pedido Processando
- Criar Evento De Pesquisa Nps
- Criar Evento De Progresso De Envio
- Criar Evento De Redefinicao De Senha
- Gerenciamento Da Conta Actions
- Grupo De Variável Customizada Actions
- Integração Actions
- Lead Actions
- Lista De Lead Actions
- Variável Customizada Actions
Overview
This node operation "Buscar Todos Os Leads" (Search All Leads) is designed to retrieve multiple lead records from a data source, applying optional filters and including related entities as needed. It is useful in scenarios where you want to fetch a list of leads based on specific criteria such as name, phone number, email, or tag ID. Additionally, it allows including related information like lists, list sources, tags, and users associated with the leads.
Practical examples:
- Fetch all leads whose name contains "John".
- Retrieve leads filtered by a specific email domain.
- Get leads along with their associated tags and user information for detailed reporting.
Properties
| Name | Meaning |
|---|---|
| Filtros | Collection of filters to narrow down the leads retrieved. Options include: |
| - Nome | Filter leads by their name (string). |
| - Telefone | Filter leads by their phone number (string). |
| Filter leads by their email address (string). | |
| - Tag ID | Filter leads by a specific tag ID (string). |
| Incluir Relacionamentos | Multi-select option to include related entities in the response. Possible values are: |
| - Listas (Lists) | |
| - Fonte Das Listas (Source of Lists) | |
| - Tags | |
| - Usuários (Users) |
Output
The output will be a JSON array containing lead objects that match the specified filters. Each lead object may include additional nested objects or arrays representing the selected related entities (lists, list sources, tags, users) if requested.
If binary data is returned (not indicated in the provided code), it would typically represent attachments or files related to leads, but this is not evident here.
Dependencies
- Requires access to an external service or API that manages lead data.
- Needs appropriate API authentication credentials configured in n8n to authorize requests.
- The node depends on the bundled description file (
NI.description) for its metadata but no other external libraries are indicated.
Troubleshooting
- Common issues might include incorrect filter values leading to empty results.
- Missing or invalid API credentials can cause authentication errors.
- Selecting relationships that do not exist or are not linked to leads may result in incomplete data.
- Error messages related to network connectivity or API limits should be checked and resolved by verifying connection settings and usage quotas.
Links and References
- No direct links provided in the source code.
- For more details on filtering and relationship options, consult the API documentation of the lead management system integrated with this node.