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 data for a single lead, such as viewing lead details, updating lead information, or performing actions based on the lead's attributes.
Practical examples include:
- Fetching a lead's profile before updating their status.
- Retrieving associated lists, tags, or user relationships linked to the lead.
- Displaying lead information in a dashboard or CRM interface.
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's data corresponding to the provided ID. This includes the lead's core attributes and, optionally, related entities such as lists, list sources, tags, and users if selected in the input properties.
If relationships are included, the output JSON will have nested objects or arrays representing these linked entities.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential or authentication token to access the lead management service.
- The node depends on the external lead management system's API to fetch lead data by ID.
- Proper configuration of the API endpoint and credentials within n8n is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent lead ID will result in no data found or an error response.
- Missing or incorrect API credentials can cause authentication failures.
- Selecting relationship options that are not supported by the API may lead to partial or failed responses.
Error messages:
- "Lead not found": Verify the lead ID is correct and exists.
- "Authentication failed": Check API credentials and permissions.
- "Invalid request parameters": Ensure the ID is provided and relationship filters are valid.
Links and References
- Refer to the external lead management system's API documentation for details on lead retrieval endpoints and relationship inclusion parameters.
- n8n documentation on configuring API credentials and HTTP request nodes may assist in setup.