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 identified by their unique IDs and want to add them to a particular mailing list or sales list, this node facilitates that process 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 typically contains information about the result of the operation, such as confirmation that the specified leads were successfully added to the list. It may include details like the list ID, the lead IDs processed, and status messages.
If the node supports binary data output, it would generally represent any files or attachments related to the leads or lists, but based on the provided code and properties, this node primarily deals with JSON data.
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 within n8n is necessary for successful execution.
Troubleshooting
Common Issues:
- Providing invalid or non-existent lead IDs or list IDs will likely cause errors or no action.
- Incorrect formatting of multiple lead IDs (should be comma-separated without extra spaces).
- Missing required properties such as lead IDs or list ID.
Error Messages:
- Errors indicating "Lead not found" or "List not found" suggest invalid identifiers.
- Authentication errors imply misconfigured or missing API credentials.
Resolutions:
- Verify that all lead and list IDs exist and are correctly formatted.
- Ensure API credentials are correctly set up and have sufficient permissions.
- Check network connectivity to the external service.
Links and References
- Refer to the external service's API documentation for detailed information on lead and list management endpoints.
- n8n documentation on setting up API credentials and using HTTP Request nodes for custom integrations.