Actions48
- Custom Variable Actions
- Custom Variable Group Actions
- Event Actions
- Integration Actions
- Lead Actions
- Lead List Actions
Overview
This node interacts with a custom variables API, specifically allowing users to retrieve a custom variable by its unique identifier. It is useful in scenarios where workflows need to dynamically fetch configuration or metadata stored as custom variables, for example, retrieving user-specific settings or environment parameters during automation.
The "Get Custom Variable By ID" operation fetches detailed information about a single custom variable using its ID. Optional related data such as the organization, author, last editor, or variable group can also be included in the response to provide richer context.
Properties
| Name | Meaning |
|---|---|
| Custom Variable ID | The unique identifier of the custom variable to retrieve. |
| Include Relationships | Optional related entities to include in the response. Options: Organization, Author, Last Edited By, Variable Group. |
Output
The output JSON contains the details of the requested custom variable. This includes its core properties (such as ID, name, value) and optionally any related entities selected via the "Include Relationships" property. The exact structure depends on the API response but typically includes:
- Custom variable fields (ID, name, value, etc.)
- Related objects if requested (organization info, author details, last editor info, variable group)
No binary data output is indicated.
Dependencies
- Requires an API key or authentication token configured in n8n to access the external custom variables API at
https://api.notificacoesinteligentes.com. - The node uses HTTP requests with authentication to communicate with this external service.
- No other external dependencies are indicated.
Troubleshooting
- Invalid or missing Custom Variable ID: Ensure the ID provided is correct and exists in the system.
- Authentication errors: Verify that the API key or authentication credentials are correctly configured and have sufficient permissions.
- Network timeouts or connectivity issues: Check network access to the external API endpoint and increase timeout if necessary.
- Empty or unexpected responses: Confirm that the custom variable exists and that optional relationships requested are valid.
Common error messages will likely relate to HTTP status codes such as 401 Unauthorized, 404 Not Found (invalid ID), or 500 Internal Server Error from the API. Resolving these involves checking credentials, input values, and API status.
Links and References
- API Documentation for Custom Variables (if available) (hypothetical link based on base URL)