Actions48
- Custom Variable Actions
- Custom Variable Group Actions
- Event Actions
- Integration Actions
- Lead Actions
- Lead List Actions
Overview
This node operation "Get All Custom Variables" retrieves a list of custom variables from an external service. It allows users to fetch all available custom variables with optional filtering and inclusion of related entities. This is useful in scenarios where you want to dynamically access or manage custom variables defined in the external system, for example, to use them in automation workflows, reporting, or data synchronization.
Practical examples:
- Fetching all custom variables related to a specific variable group to process or display them.
- Including relationships such as the organization or author details to enrich the retrieved data.
- Filtering variables by type (e.g., email, integer) or slug to narrow down the results.
Properties
| Name | Meaning |
|---|---|
| Include Relationships | Optional parameters to include related entities in the response. Possible values: Organization, Author, Last Edited By, Variable Group. |
| Filters | Collection of filters to narrow down the custom variables returned: |
| - Slug | Filter by the slug identifier of the variable. |
| - Type | Filter by variable type. Supported types: cpf, cnpj, email, integer, option_list, multi_select, numeric, text. |
| - Variable Group Name | Filter by the name of the variable group to which the variable belongs. |
Output
The output is a JSON array containing the custom variables matching the request criteria. Each item typically includes the variable's properties such as its slug, type, and potentially related entities if requested via the "Include Relationships" property.
If relationships are included, the output will contain nested objects representing those related entities (e.g., organization details, author information).
No binary data output is indicated.
Dependencies
- Requires an API key credential or similar authentication token to access the external service at
https://api.notificacoesinteligentes.com. - The node uses HTTP requests with authentication to communicate with the external API.
- No additional environment variables beyond standard API credentials appear necessary.
Troubleshooting
- Common issues:
- Authentication failures due to missing or invalid API credentials.
- Network timeouts or connectivity issues when calling the external API.
- Incorrect filter values leading to empty results.
- Error messages:
- Timeout errors may occur if the API does not respond within 5 seconds.
- Errors related to invalid query parameters if filters are malformed.
- Resolutions:
- Verify that the API key or authentication token is correctly configured.
- Check network connectivity and API availability.
- Ensure filter values conform to expected formats and supported types.
Links and References
- API Documentation of the External Service (assumed base URL)
- n8n HTTP Request Node documentation for configuring authenticated requests: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/