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 Todas as Listas" (Search All Lists) under the resource "Lista De Lead" is designed to retrieve multiple lead lists from a system. It allows users to fetch all available lead lists with options to include related data and apply filters to narrow down the results. This is useful in scenarios where you want to analyze, report on, or process multiple lead lists at once, such as marketing campaigns, sales outreach, or data synchronization tasks.
Practical examples:
- Fetching all lead lists that contain leads for targeted email campaigns.
- Retrieving lead lists filtered by name or type to integrate with CRM systems.
- Including additional information like the source of the list or the count of leads for reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Incluir Relacionamentos | Choose which relationships to include in the request, such as "Fonte (Source)" or "Contagem De Leads" (Lead Count). Options: source, leadsCount |
| Mais Propriedades | Select list properties to filter by, e.g., whether the list contains leads (has_leads). |
| Filtros | Define filters to search specific lists: |
| - Nome | Filter lists by their name (string). |
| - Tipo | Filter lists by their type (string). |
Output
The output will be a JSON array containing the lead lists matching the specified criteria. Each item in the array represents a lead list object, potentially including related data such as the source of the list and the number of leads it contains if those relationships were requested.
If binary data is present (not indicated here), it would typically represent attachments or files related to the lead lists, but this node appears focused on JSON data only.
Dependencies
- Requires access to the external service or API that manages lead lists.
- Needs appropriate API authentication credentials configured in n8n to authorize requests.
- No other explicit dependencies are indicated in the provided code.
Troubleshooting
- No lists returned: Check if filters are too restrictive or if the account has no lead lists.
- Authentication errors: Ensure the API key or token is correctly set up and has permissions to read lead lists.
- Invalid filter values: Confirm that filter inputs like name and type match expected formats or existing values.
- Empty relationships: If related data like source or lead count is not appearing, verify that these options are selected and supported by the API.
Links and References
- Refer to the API documentation of the lead management system for details on list retrieval endpoints and filtering capabilities.
- n8n documentation on how to configure API credentials and use multiOptions and collection parameters effectively.