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 leads by cleaning up lists, removing outdated or irrelevant contacts, or segmenting your audience dynamically.
For example, if you have a list of leads for a campaign and some leads have opted out or are no longer relevant, you can use this node to remove those leads by specifying their IDs and the target list ID.
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 node outputs JSON data representing the result of the removal operation. Typically, this would include confirmation that the specified leads were successfully removed from the list. The exact structure depends on the API response but generally includes status information and possibly details about the affected leads.
No binary data output is expected from this operation.
Dependencies
- Requires an external service or API that manages lead lists and supports removing leads by their IDs.
- An API key or authentication token is necessary to authorize requests to the external service.
- Proper configuration of credentials within n8n is required to enable communication with the lead management system.
Troubleshooting
- Invalid Lead IDs: If the provided lead IDs do not exist or are malformed, the node may return an error or fail silently. Ensure IDs are correct and formatted as comma-separated values without extra spaces.
- Invalid List ID: Providing a non-existent or incorrect list ID will cause the operation to fail. Verify the list ID before running the node.
- Authentication Errors: Missing or invalid API credentials will prevent the node from executing successfully. Check that the API key or token is correctly configured.
- API Rate Limits: If too many requests are sent in a short period, the external service might throttle or block requests. Implement retry logic or reduce request frequency if needed.
Links and References
- Refer to the documentation of the external lead management API for detailed information on removing leads from lists.
- Consult n8n's credential setup guides to properly configure API authentication.