IT Glue icon

IT Glue

Utilize the IT Glue API

Overview

This node integrates with the IT Glue API to perform various operations on IT Glue resources. Specifically, for the Configuration resource with the Bulk Delete operation, it allows users to delete multiple configuration records in one request by specifying their IDs. This is useful for cleaning up or managing large sets of configurations efficiently without needing to delete each individually.

Practical examples include:

  • Removing outdated or deprecated configurations from your IT Glue account.
  • Bulk deleting configurations that are no longer relevant after a system migration or audit.
  • Automating cleanup tasks as part of a larger workflow to maintain data hygiene.

Properties

Name Meaning
Configuration IDs Comma-separated list of configuration IDs to delete. These specify which configurations will be removed in bulk.

Output

The node outputs JSON data representing the result of the bulk delete operation. Typically, this includes confirmation of which configuration IDs were successfully deleted or any errors encountered during the process.

If the node supports binary data output (not indicated here), it would generally represent file attachments or related binary content, but for bulk deletion of configurations, the output is purely JSON-based status information.

Dependencies

  • Requires an API key credential for authenticating with the IT Glue API.
  • The node depends on the IT Glue REST API being accessible and the user having appropriate permissions to delete configurations.
  • No additional external services are required beyond the IT Glue API.

Troubleshooting

  • Invalid or missing Configuration IDs: Ensure the "Configuration IDs" property is provided as a comma-separated string of valid IDs. Missing or malformed IDs will cause the operation to fail.
  • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • API rate limits or network issues: If requests fail intermittently, check for API rate limiting or connectivity problems.
  • Partial failures: Some IDs may not exist or may be protected; the response should indicate which deletions succeeded or failed.

Common error messages might include:

  • Unauthorized access due to invalid credentials.
  • Not found errors if specified configuration IDs do not exist.
  • Validation errors if the input format is incorrect.

Resolving these typically involves verifying credentials, checking ID correctness, and ensuring the user has proper permissions.

Links and References

Discussion