Actions48
- Custom Variable Actions
- Custom Variable Group Actions
- Event Actions
- Integration Actions
- Lead Actions
- Lead List Actions
Overview
This node operation allows users to create a custom variable within an external system via an API. Custom variables are user-defined data fields that can be used to store specific information such as identification numbers, emails, numeric values, or text. This is useful in scenarios where you want to extend the data model of your application or integration by adding tailored attributes.
For example, you might create a custom variable to store a customer's CPF (a Brazilian individual taxpayer registry identification), or an email address, or a multi-select list of options relevant to your business logic. Once created, these variables can be used in subsequent workflows for filtering, personalization, or automation purposes.
Properties
| Name | Meaning |
|---|---|
| Name | The name identifier for the custom variable being created. |
| Description | A brief textual description explaining the purpose or usage of the custom variable. |
| Variable Type | The data type of the custom variable. Options include: CNPJ, CPF, Email, Integer, Multi Select, Numeric, Option List, Text. |
Output
The node outputs JSON data representing the newly created custom variable. This typically includes details such as the variable's unique identifier, name, description, and type as returned by the external API. There is no indication that binary data is output by this node.
Dependencies
- Requires access to an external API endpoint at
https://api.notificacoesinteligentes.comto create the custom variable. - Needs an API authentication token or key configured in n8n to authorize requests.
- The node uses HTTP requests with authentication to communicate with the external service.
Troubleshooting
Common issues:
- Authentication failures due to missing or invalid API credentials.
- Validation errors if required properties like "Description" are missing or if the "Name" conflicts with existing variables.
- Network timeouts or connectivity problems when reaching the external API.
Error messages and resolutions:
- 401 Unauthorized: Check that the API key or token is correctly set up in n8n credentials.
- 400 Bad Request: Verify that all required fields are provided and valid, especially the "Description" and "Variable Type".
- Timeouts: Ensure network connectivity and that the external API is reachable.
Links and References
- API Documentation for Custom Variables (hypothetical link)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/