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 operation "Apagar Lista Por ID" (Delete List By ID) under the resource "Lista De Lead" is designed to delete a specific lead list by its unique identifier. This operation is useful in scenarios where you want to remove an entire list of leads from your system, for example, when a campaign ends or when cleaning up outdated or irrelevant lead data.
Practical examples include:
- Automatically deleting a lead list after a marketing campaign concludes.
- Removing test or temporary lead lists created during development or testing phases.
- Managing lead data lifecycle by programmatically deleting lists that are no longer needed.
Properties
| Name | Meaning |
|---|---|
| ID Da Lista | The unique identifier of the lead list to be deleted |
Output
The output structure is not explicitly detailed in the provided source code. However, typically for a delete operation like this, the json output field would contain a confirmation of deletion, such as a success status or message indicating that the list with the specified ID was successfully deleted.
If the node supports binary data output, it would likely be related to any response payloads or logs, but this is not evident from the given code.
Dependencies
- Requires an API key credential or authentication token to authorize the deletion request.
- Depends on the external service or API managing the lead lists.
- Proper configuration of the API endpoint and credentials within n8n is necessary.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent list ID will result in failure to delete.
- Missing or incorrect API authentication can cause authorization errors.
- Network issues or API downtime may prevent successful deletion.
Error Messages:
- "List not found" or similar indicates the provided ID does not correspond to any existing list.
- "Unauthorized" or "Authentication failed" suggests problems with API credentials.
- Timeout or connection errors imply network or service availability problems.
Resolutions:
- Verify the list ID is correct and exists.
- Ensure API credentials are correctly configured and valid.
- Check network connectivity and API service status.
Links and References
- Refer to the external API documentation managing lead lists for detailed information on delete operations.
- n8n documentation on configuring API credentials and handling HTTP requests.