h2oGPTe icon

h2oGPTe

h2oGPTe is an AI-powered search assistant for your internal teams to answer questions gleaned from large volumes of documents, websites and workplace content.

Actions198

Overview

This node operation updates the expiry date of a specified collection within the system. It allows users to set or modify when a collection should expire, optionally associating a timezone with the expiry date. This is useful for managing lifecycle and access control of collections, ensuring that collections are only available until a certain date.

Common scenarios:

  • Automatically expiring temporary collections after a project ends.
  • Setting expiry dates for collections containing sensitive or time-limited data.
  • Managing content availability in compliance with organizational policies.

Example:
You have a collection of documents related to a marketing campaign that should no longer be accessible after a specific date. Using this node, you can update the expiry date of that collection to enforce this rule.

Properties

Name Meaning
Collection ID The unique identifier of the collection whose expiry date you want to update.
Expiry Date The new expiry date to set for the collection (string format).
Additional Options - Timezone Optional IANA timezone string to associate with the expiry date, e.g., "America/New_York".

Output

The output will contain the JSON response from the API after updating the expiry date of the collection. This typically includes confirmation details about the updated collection expiry date.

If the operation is successful, the output JSON will reflect the updated expiry date and any associated metadata returned by the API.

The node does not output binary data.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the backend service.
  • The base URL for the API is derived from the credential's URL configuration.
  • The node sends a PUT request to the endpoint /collections/{collection_id}/expiry_date with the expiry date and optional timezone in the request body.

Troubleshooting

  • Missing or invalid Collection ID: Ensure the Collection ID is provided and correct; otherwise, the API will return an error indicating the collection was not found.
  • Invalid expiry date format: The expiry date must be in a valid string format accepted by the API (usually ISO 8601). Invalid formats may cause request failures.
  • Timezone issues: If specifying a timezone, ensure it is a valid IANA timezone string. Incorrect timezone values might be ignored or cause errors.
  • Authentication errors: Verify that the API key credential is correctly set up and has permissions to update collections.
  • API endpoint errors: Network issues or incorrect base URL configurations can lead to failed requests.

Links and References

  • IANA Time Zone Database – Reference for valid timezone strings.
  • API documentation for collection management (not publicly linked here due to internal nature).

This summary is based on static analysis of the node's properties and routing information for the "update_collection_expiry_date" operation under the "collection" resource.

Discussion