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 edit an existing lead's information in a system. It allows updating key details such as the lead's name, email, notes, and custom variables associated with the lead. This node is useful in scenarios where lead data needs to be kept current, for example, when contact information changes or additional notes need to be added after initial lead creation.
Practical examples include:
- Updating a lead’s email address after receiving new contact info.
- Adding notes about recent interactions or preferences.
- Modifying custom variables that track specific attributes or statuses related to the lead.
Properties
| Name | Meaning |
|---|---|
| ID Do Lead | The unique identifier of the lead to be edited. |
| Nome | The full name of the lead. |
| The email address of the lead. | |
| Notas | Additional notes or observations about the lead. |
| Variáveis Customizadas | A collection of custom variables to update on the lead. Each variable has: - Slug: The identifier of the custom variable. - Valor: The value to assign to this custom variable. |
Output
The node outputs JSON data representing the updated lead object after the edit operation completes. This typically includes the lead's updated fields such as ID, name, email, notes, and any custom variables. There is no indication that the node outputs binary data.
Dependencies
- Requires access to the lead management system's API or database where leads are stored.
- Needs appropriate authentication credentials (e.g., an API key or token) configured in n8n to authorize editing operations.
- No other external dependencies are indicated from the provided source code.
Troubleshooting
Common issues:
- Providing an invalid or non-existent lead ID will likely cause the edit operation to fail.
- Missing required fields such as "ID Do Lead", "Nome", or "Email" may result in validation errors.
- Incorrect formatting of custom variables (e.g., missing slug or value) could cause partial updates or errors.
Error messages:
- Errors indicating "Lead not found" suggest the provided lead ID does not exist.
- Validation errors about missing required fields mean those inputs must be supplied before execution.
- Authentication errors imply misconfigured or missing API credentials.
To resolve these, verify the lead ID exists, ensure all required properties are filled, and confirm that API credentials are correctly set up in n8n.
Links and References
No external links or references were provided in the source code or property definitions. For further details, consult the documentation of the lead management system integrated with this node.