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 (required). |
| Nome | The full name of the lead (required). |
| The email address of the lead (required). | |
| 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 that variable. |
Output
The node outputs JSON data representing the updated lead object after the edit operation. This typically includes the lead's ID, name, email, notes, and any custom variables with their updated values.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the lead, but this is not evident from the provided code and properties.
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.
- The node depends on the underlying service described in the bundled source code, which is not fully visible here but implied by the resource and operation context.
Troubleshooting
- Missing Required Fields: Errors may occur if the lead ID, name, or email fields are empty or invalid. Ensure these are correctly provided.
- Invalid Lead ID: If the specified lead ID does not exist, the node will likely return an error indicating the lead was not found.
- Authentication Failures: Incorrect or missing API credentials can cause authorization errors.
- Custom Variables Format: Ensure custom variables are provided with both slug and value; incomplete entries might be ignored or cause errors.
- API Rate Limits: Frequent edits might hit rate limits imposed by the external service.
Links and References
- Refer to your lead management system’s API documentation for details on editing leads.
- n8n documentation on creating and using custom nodes: https://docs.n8n.io/integrations/creating-nodes/
- General best practices for managing leads in CRM systems.