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 "Criar Variável Customizada" (Create Custom Variable) allows users to create a custom variable with specific attributes such as name, description, and data type. This is useful in scenarios where users want to define variables tailored to their business logic or workflow needs, for example, defining customer identifiers like CPF or CNPJ, or categorizing data inputs such as emails, numeric values, or option lists.
Practical examples include:
- Creating a custom variable to store a customer's CPF number for validation.
- Defining a variable that holds multiple selectable options for user preferences.
- Setting up a text variable to capture free-form input from users.
Properties
| Name | Meaning |
|---|---|
| Nome | The name of the custom variable to be created. |
| Descrição | A brief description explaining the purpose or details of the custom variable. |
| Tipo De Variável | The data type of the custom variable. Options: CNPJ, CPF, Email, Inteiro (Integer), Lista De Opções (Option List), Múltipla Seleção (Multi Select), Numérico (Numeric), Texto (Text). |
Output
The output JSON structure is not explicitly detailed in the provided source code. However, typically, after creating a custom variable, the node would output an object representing the newly created variable, including its name, description, type, and possibly an identifier or status confirming creation.
If the node supports binary data output, it would likely relate to attachments or files associated with the variable, but no such indication is present in the given code.
Dependencies
- The node depends on an external module
./NI.descriptionto retrieve the node's description metadata. - It likely requires access to an API or service that manages custom variables, authenticated via an API key or token configured within n8n credentials (not specified in the code).
- No explicit environment variables or additional dependencies are visible in the provided snippet.
Troubleshooting
- Missing Required Fields: Ensure that the "Descrição" (Description) field is filled, as it is marked required.
- Invalid Data Type Selection: Selecting an unsupported or mismatched data type could cause errors; verify that the chosen type matches expected formats.
- API Authentication Issues: If the node interacts with an external service, ensure that the necessary API credentials are correctly configured in n8n.
- Empty Name Field: Although not marked required, providing a meaningful "Nome" (Name) is essential for identifying the variable; leaving it empty might lead to unexpected behavior.
Common error messages might include validation errors for missing required fields or authentication failures when connecting to the external service managing custom variables.
Links and References
- No direct links are available from the provided code. For further information, consult the documentation of the external service managing custom variables or n8n's official documentation on creating custom nodes and handling credentials.