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 remove one or more leads from a specified lead list. This operation is useful in scenarios where you need to manage your marketing or sales contact lists by cleaning up or updating the members of a particular list. For example, if certain leads have become unresponsive or are no longer relevant, this node allows you to efficiently remove them from your targeted campaigns.
Properties
| Name | Meaning |
|---|---|
| ID(s) Do(s) Lead(s) | The unique identifier(s) of the lead(s) to be removed. Multiple IDs can be provided separated by commas (e.g., "17, 25, 33"). |
| ID Da Lista | The unique identifier of the lead list from which the leads will be removed. |
Output
The output JSON typically contains information about the result of the removal operation, such as confirmation that the specified leads were successfully removed from the list. If the node supports binary data output, it would generally relate to any files or attachments associated with the operation, but based on the provided code and properties, this node primarily outputs JSON data confirming the action.
Dependencies
- Requires an API key credential or similar authentication token to access the external service managing the lead lists.
- The node depends on an external lead management system or CRM API that supports removing leads from lists.
- Proper configuration of the API credentials within n8n is necessary for successful execution.
Troubleshooting
- Common Issues:
- Providing invalid or non-existent lead IDs or list IDs may cause the operation to fail.
- Network or authentication errors if the API key or credentials are missing or incorrect.
- Error Messages:
- Errors indicating "Lead not found" or "List not found" suggest that the provided IDs do not exist or are mistyped.
- Authentication errors usually indicate misconfigured or expired API credentials.
- Resolution:
- Verify that all IDs are correct and correspond to existing leads and lists.
- Ensure that the API credentials are correctly set up and have sufficient permissions.
- Check network connectivity and API endpoint availability.
Links and References
- Refer to the documentation of the external lead management or CRM system used for managing leads and lists.
- n8n documentation on setting up API credentials and using HTTP Request nodes for custom integrations.