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
The node operation "Buscar Lista Por ID" (Search List By ID) under the resource "Lista De Lead" is designed to retrieve detailed information about a specific lead list by its unique identifier. This operation is useful when you want to fetch metadata or details of a particular leads list stored in an external system, for example, to verify its existence, check its attributes, or prepare it for further processing such as adding or removing leads.
Practical examples include:
- Fetching a lead list before updating or deleting it.
- Retrieving source details of a lead list to understand where the leads originated.
- Validating that a list exists before performing batch operations on it.
Properties
| Name | Meaning |
|---|---|
| ID Da Lista | The unique identifier of the lead list to be fetched. |
| Incluir Detalhes Da Fonte | Additional parameters to include source details in the response. Options: "Fonte" (Source). |
Output
The output JSON will contain the details of the requested lead list identified by the provided ID. If the option to include source details is selected, the output will also contain additional information about the origin/source of the list.
No binary data output is indicated for this operation.
Dependencies
- Requires access to an external service or API that manages lead lists.
- An API key or authentication token is likely required to authorize requests to the external system.
- Proper configuration of credentials within n8n is necessary to enable communication with the lead management service.
Troubleshooting
Common issues:
- Providing an invalid or non-existent list ID will result in errors or empty responses.
- Missing or incorrect API credentials can cause authentication failures.
- Network connectivity problems may prevent successful API calls.
Error messages and resolutions:
- "List not found": Verify that the provided list ID is correct and exists in the external system.
- "Authentication failed": Check that the API key or authentication token is correctly configured and valid.
- Timeout or network errors: Ensure stable internet connection and that the external API endpoint is reachable.
Links and References
- Refer to the external lead management system's API documentation for details on list retrieval endpoints and parameters.
- n8n documentation on setting up API credentials and HTTP request nodes for integrating with external services.