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 "Remover Listas De Um Lead" (Remove Lists From a Lead) is designed to dissociate one or more specified lists from a particular lead in a CRM or marketing system. It is useful when you want to update the segmentation or categorization of leads by removing them from certain mailing lists, campaign groups, or other list-based classifications.
Common scenarios include:
- Cleaning up lead data by removing outdated or irrelevant list associations.
- Managing dynamic marketing campaigns where leads need to be removed from specific target lists based on behavior or status changes.
- Automating lead lifecycle management by adjusting list memberships programmatically.
For example, if a lead has been unsubscribed or no longer fits a campaign's criteria, this operation can remove that lead from the associated lists to prevent further communications.
Properties
| Name | Meaning |
|---|---|
| ID Do Lead | The unique identifier of the lead from which lists will be removed. |
| ID(s) Da(s) Lista(s) | One or more IDs of the lists to be removed from the lead. Multiple IDs can be comma-separated. |
Output
The output structure is not explicitly detailed in the provided source code. However, typically for such operations, the json output would contain confirmation of the removal action, such as success status, the lead ID affected, and possibly the list IDs that were removed.
If binary data output is supported, it would likely relate to any files or attachments associated with the lead or lists, but there is no indication of binary output in the given code.
Dependencies
- This node requires access to an external service or API managing leads and their list associations.
- An API key or authentication token is necessary to authorize requests to the external system.
- Proper configuration of credentials within n8n is required to enable communication with the lead management backend.
Troubleshooting
- Missing or invalid lead ID: Ensure the lead ID provided exists and is correctly formatted; otherwise, the operation will fail to find the lead.
- Invalid list IDs: If any list ID does not exist or is not associated with the lead, the removal may partially fail or return errors.
- Authentication errors: Verify that the API credentials are valid and have sufficient permissions to modify lead-list associations.
- Network or API downtime: Temporary connectivity issues or service outages can cause failures; retry after some time or check service status.
Common error messages might include:
- "Lead not found" – Check the lead ID.
- "List ID invalid or not associated with lead" – Verify list IDs.
- "Unauthorized" or "Authentication failed" – Confirm API credentials.
Links and References
No direct links or references are available from the provided source code. For further details, consult the documentation of the external lead management system or API used by this node.