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 retrieve a custom variable by its unique identifier. This operation is useful when you need to fetch detailed information about a specific custom variable within an organization or system, such as for auditing, reporting, or further processing in workflows.
Practical examples include:
- Fetching a custom variable's details to display or log them.
- Using the retrieved variable data to make decisions or trigger other actions in an automation workflow.
- Including additional related information like the organization, author, last editor, or variable group associated with the custom variable.
Properties
| Name | Meaning |
|---|---|
| ID Da Variável Customizada | The unique identifier of the custom variable to retrieve. |
| Parâmetros Adicionais | Optional parameters to include additional related data in the response. Options: Organização (Organization), Autor (Author), Última Edição Por (Last Edited By), Grupo De Variáveis (Variable Group). |
Output
The output will contain a JSON object representing the custom variable identified by the provided ID. Depending on the selected optional parameters, the output may also include related entities such as the organization it belongs to, the author who created it, the user who last edited it, and the variable group it is part of.
If binary data is supported (not indicated in the provided code), it would typically represent attachments or files related to the custom variable, but no such indication is present here.
Dependencies
- Requires an API key credential or similar authentication token to access the service managing custom variables.
- The node depends on an external API or service that stores and manages custom variables.
- Proper configuration of this API connection within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Providing an invalid or non-existent custom variable ID will likely result in an error or empty response.
- Missing or incorrect authentication credentials can cause authorization failures.
- Selecting optional parameters not supported by the backend API might lead to partial responses or errors.
Error messages:
- "Custom variable not found" — Verify the ID is correct and exists.
- "Unauthorized" or "Authentication failed" — Check API credentials and permissions.
- "Invalid parameter" — Ensure optional parameters are valid and correctly formatted.
Links and References
- Refer to the API documentation of the service managing custom variables for detailed information on available fields and optional parameters.
- n8n documentation on creating and configuring HTTP request nodes or custom nodes for API integration.