iTwin Projects icon

iTwin Projects

Comprehensive iTwin Projects API

Overview

This node allows users to delete a repository within an iTwin project environment. It is useful in scenarios where repositories are no longer needed or must be removed for cleanup, access control, or organizational purposes. For example, a user managing multiple repositories under different iTwin projects can automate the deletion of obsolete repositories by specifying their IDs.

Properties

Name Meaning
iTwin ID The unique identifier of the iTwin project containing the repository to delete.
Repository ID The unique identifier of the repository to be deleted.

Output

The output JSON contains the result of the delete operation. Typically, this will confirm whether the repository was successfully deleted or provide error information if the operation failed. The exact structure depends on the API response but generally includes status or confirmation fields.

No binary data output is involved in this operation.

Dependencies

  • Requires an API authentication token credential to access the iTwin Projects API.
  • The node internally uses an interpreter class (ProjectsOpenApiInterpreter) to map and execute operations against the iTwin Projects API.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing iTwin ID or Repository ID parameters will cause the operation to fail.
    • Insufficient permissions or invalid API credentials may result in authorization errors.
    • Attempting to delete a non-existent repository will likely return an error from the API.
  • Error messages:

    • "Unknown operation: delete-repository": This indicates the operation name is not recognized; ensure the correct operation parameter is set.
    • API errors returned from the iTwin service will be passed through; check the error message for details such as "repository not found" or "access denied".
  • Resolution tips:

    • Verify that the iTwin ID and Repository ID are correct and exist.
    • Confirm that the API credentials have sufficient permissions.
    • Use the node's "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion