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 Lead Por ID" (Search Lead By ID) is designed to retrieve detailed information about a specific lead using its unique identifier. It is useful in scenarios where you need to fetch a single lead's data for review, update, or integration purposes. For example, you might use this operation to display lead details in a CRM dashboard or to synchronize lead data with another system.
Properties
| Name | Meaning |
|---|---|
| ID Do Lead | The unique identifier of the lead to be retrieved. |
| Incluir Relacionamentos | Select which related entities should be included in the response. Options: Lists, Source of Lists, Tags, Users. |
Output
The output will contain a JSON object representing the lead identified by the provided ID. This object may include additional related data depending on the selected relationships (lists, list sources, tags, users). The structure typically includes lead attributes such as name, contact info, and any associated metadata or linked entities.
No binary data output is indicated.
Dependencies
- Requires an API key credential or similar authentication token to access the lead management service.
- The node depends on the external lead management API that supports fetching leads by ID and optionally including related entities.
- Proper configuration of the API endpoint and credentials within n8n is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent lead ID will likely result in an error or empty response.
- Missing or incorrect API credentials can cause authentication failures.
- Selecting unsupported relationship options may cause the request to fail or ignore those parameters.
Error messages:
- "Lead not found" indicates the specified ID does not exist; verify the ID.
- Authentication errors suggest checking API keys or tokens.
- Network or timeout errors require verifying connectivity and API availability.
Links and References
- Refer to the lead management platform's official API documentation for details on the lead retrieval endpoint and supported query parameters.
- n8n documentation on configuring HTTP Request nodes and managing credentials may be helpful.