Actions54
- Resource Actions
- Userpermissions Actions
- Baselinefile Actions
- Locks Actions
- Briefcases Actions
- Checkpoint Actions
- Thumbnail Actions
- Extendeddata Actions
- Changesets Actions
- Changesetgroups Actions
- Permissions Actions
- Recents Actions
- Namedversions Actions
- Shares Actions
- Rolepermissions Actions
- Users Actions
- Favorites Actions
- Fork Actions
- Clone Actions
- Create Actions
Overview
This node interacts with the iTwin Platform to retrieve a list of the user's favorite iModels associated with a specified iTwin. It is useful for workflows that need to access or process metadata about iModels that a user has marked as favorites, such as displaying them in dashboards, syncing favorite projects, or automating notifications related to these iModels.
A practical example would be an automation that fetches all favorite iModels for a given iTwin and then triggers further processing like generating reports or updating project management tools.
Properties
| Name | Meaning |
|---|---|
| iTwin ID | The unique identifier of the iTwin whose favorite iModels you want to retrieve. This is required to specify the context of the query. |
| Continuation Token | A token used for paginated responses to retrieve the next page of results. This token is generated by the service and must be sent exactly as received. It is mutually exclusive with the skip parameter. To start using it, provide an empty token. |
Output
The output is an array of JSON objects, each representing an iModel that is marked as a favorite by the user within the specified iTwin. Each object contains the details of an iModel as returned by the iTwin Platform API.
If pagination is used, the output may include partial lists depending on the continuation token provided.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication credential for the iTwin Platform (OAuth2-based).
- The node depends on the iTwin Platform's REST API to fetch favorite iModels.
- Proper configuration of the OAuth2 credential in n8n is necessary to authenticate requests.
Troubleshooting
- Common issues:
- Missing or invalid iTwin ID will cause the request to fail.
- Incorrect or expired API authentication tokens will result in authorization errors.
- Using both continuation token and skip parameters simultaneously can cause conflicts; only one should be used.
- Error messages:
"Unknown operation": Indicates the operation name was not recognized; ensure "Get My Favorite iTwin iModels" is selected.- Authorization errors typically indicate problems with the API key or OAuth2 token; re-authenticate or refresh credentials.
- Pagination errors may occur if the continuation token is malformed or expired; restart pagination by providing an empty token.