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 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, such as for reporting, synchronization, or further processing within an automation workflow.
A practical example would be: You have multiple marketing lead lists and want to pull the details of one specific list by its ID to analyze its source or other attributes before deciding on further actions like segmentation or export.
Properties
| Name | Meaning |
|---|---|
| ID Da Lista | The unique identifier of the lead list you want to retrieve. |
| Incluir Detalhes Da Fonte | Options to include additional source details in the response. Currently supports including "Fonte" (source) details. |
Output
The output JSON contains the detailed information 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 metadata related to the origin or source of the list.
No binary data output is indicated.
Dependencies
- Requires access to an external service or API that manages lead lists.
- Needs proper authentication credentials (e.g., an API key or token) configured in n8n to authorize requests.
- The node depends on the external system's API endpoint that supports fetching lead list details by ID.
Troubleshooting
Common issues:
- Invalid or missing list ID: Ensure the "ID Da Lista" property is correctly set with a valid identifier.
- Authentication errors: Verify that the API credentials are correctly configured and have sufficient permissions.
- Network or API downtime: Check connectivity and the status of the external service.
Error messages:
- "List not found" or similar indicates the provided ID does not exist; verify the ID.
- Authentication failures suggest invalid or expired credentials; reconfigure or refresh them.
- Timeout or connection errors imply network issues; retry or check network settings.
Links and References
- Refer to the external service's API documentation for lead list retrieval endpoints.
- n8n documentation on configuring API credentials and using HTTP request nodes may be helpful for setup.