Infomaniak CoreResources icon

Infomaniak CoreResources

Interact with Infomaniak API

Actions28

Overview

This node interacts with the Infomaniak API to manage and retrieve information about timezones. Specifically, the "Get" operation for the "Timezone" resource fetches details of a specific timezone by its unique identifier. This is useful in scenarios where workflows need to handle or convert dates and times according to different timezones, such as scheduling events, logging activities, or displaying localized times.

Practical examples:

  • Fetching detailed information about a timezone to adjust event times accordingly.
  • Validating or enriching data records with timezone metadata.
  • Integrating with other systems that require timezone-specific configurations.

Properties

Name Meaning
Timezone ID The unique identifier (number) of the timezone to request details for.

Output

The output is a JSON object containing the details of the requested timezone as returned by the Infomaniak API. The structure typically includes fields describing the timezone's properties such as its name, offset, and possibly other metadata provided by the API.

No binary data output is involved in this operation.

Example output (simplified):

{
  "id": 1,
  "name": "Europe/Paris",
  "offset": "+01:00",
  "description": "Central European Time"
}

Dependencies

  • Requires an API key credential for authenticating with the Infomaniak API.
  • The node makes HTTP GET requests to the Infomaniak API endpoint https://api.infomaniak.com/1/timezones/{timezoneId}.
  • Proper configuration of the API authentication token in n8n credentials is necessary.

Troubleshooting

  • Error: "Timezone with ID X not found"
    This indicates that the specified timezone ID does not exist or is invalid. Verify the ID value before running the node.

  • Error: "Failed to retrieve timezone"
    Could be due to network issues, invalid API token, or API service problems. Check API credentials, network connectivity, and ensure the Infomaniak API service is operational.

  • Invalid JSON format for parameters
    Although not directly applicable to this operation, if additional options are used elsewhere, ensure JSON inputs are correctly formatted.

  • Continue on Fail
    If enabled, errors will be captured in the output JSON instead of stopping execution, allowing workflows to handle failures gracefully.

Links and References

Discussion