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 inactivity interval setting of a specific collection within the system. The inactivity interval defines the number of days after which a collection is considered inactive if no activity occurs. Adjusting this interval can help manage collections by automatically flagging or handling those that have not been used for a specified period.

Common scenarios:

  • Automatically archiving or cleaning up collections that have not been accessed or modified for a certain number of days.
  • Setting custom inactivity periods for different collections based on their importance or usage patterns.
  • Managing resource allocation by identifying stale collections.

Practical example:
If you have a document collection that should be archived after 30 days of inactivity, you can use this operation to set the inactivity interval to 30. This helps automate maintenance tasks and keeps your workspace organized.

Properties

Name Meaning
Collection ID The unique identifier of the collection whose inactivity interval you want to update.
Inactivity Interval The new inactivity interval expressed as an integer number of days (e.g., 30 for 30 days).

Output

The output will contain the full HTTP response from the API call that updates the inactivity interval of the specified collection. The json field in the output typically includes confirmation details or the updated collection data reflecting the new inactivity interval.

No binary data is involved in this operation.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • The node sends a PUT request to the endpoint /collections/{collection_id}/inactivity_interval.
  • The base URL and headers are configured via credentials and node settings.
  • Ensure the API key has permissions to update collection settings.

Troubleshooting

  • Invalid Collection ID: If the provided collection ID does not exist or is incorrect, the API will return an error. Verify the collection ID before running the node.
  • Permission Denied: Insufficient permissions or invalid API key may cause authorization errors. Confirm that the API key has the necessary rights.
  • Invalid Inactivity Interval: The inactivity interval must be a non-negative integer. Providing invalid values may result in validation errors.
  • Network Issues: Connectivity problems can cause request failures. Check network access and API availability.

Links and References

  • Refer to the official API documentation for collections management for detailed information on the inactivity interval property and related endpoints.
  • Consult your platform's API key and permission management guides to ensure proper setup.

Discussion