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 manage leads within a list, specifically focusing on adding leads to a designated list. This operation is useful in scenarios where you want to organize or segment leads by grouping them into specific lists for targeted marketing campaigns, follow-ups, or categorization.
For example, if you have multiple leads collected from different sources and want to add certain leads to a promotional campaign list, this node allows you to specify the lead IDs and the target list ID to perform that action efficiently.
Properties
| Name | Meaning |
|---|---|
| ID(s) Do(s) Lead(s) | The unique identifier(s) of the lead(s) to be added. Multiple IDs can be provided separated by commas (e.g., "17, 25, 33"). |
| ID Da Lista | The unique identifier of the list to which the leads will be added. |
Output
The output JSON structure typically contains confirmation or status information about the operation of adding leads to the list. It may include details such as the IDs of leads successfully added, any errors encountered, or metadata about the updated list.
If the node supports binary data output, it would generally represent attachments or files related to the leads or lists, but based on the provided code and properties, this node primarily deals with JSON data representing lead and list identifiers.
Dependencies
- Requires an API key credential or similar authentication token to access the external service managing leads and lists.
- The node depends on an external service or API that handles lead and list management.
- Proper configuration of the API credentials in n8n is necessary for successful execution.
Troubleshooting
- Invalid Lead or List IDs: If the provided lead IDs or list ID do not exist or are incorrectly formatted, the node may fail to add leads. Ensure IDs are correct and exist in the system.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key or token is correctly configured.
- Network Issues: Connectivity problems with the external service can result in timeouts or errors. Check network connectivity and service availability.
- Empty Input: Providing empty or missing required fields (lead IDs or list ID) will likely cause errors. Always provide valid inputs.
Links and References
- Refer to the external service's API documentation for detailed information on lead and list management endpoints.
- n8n documentation on how to configure API credentials and use custom nodes.