Actions58
- Applications Actions
- Components Actions
- Brands Actions
- Documents Actions
- Weblinks Actions
- Manufacturers Actions
- Catalogs Actions
- Download Actions
- Variations Actions
- Categories Actions
- Upload Actions
- Jobs Actions
Overview
This node integrates with the iTwin Component Center API to retrieve information about component weblinks. Specifically, the "Get Component WebLinks" operation fetches web links associated with a given component, optionally filtered by project ID. This is useful in scenarios where you want to programmatically access URLs or references related to specific components within an iTwin project environment.
Practical examples include:
- Automatically gathering all relevant documentation or resource links for a component during a CI/CD pipeline.
- Displaying component-related web resources inside a dashboard or report.
- Integrating component metadata with other systems by fetching their associated weblinks.
Properties
| Name | Meaning |
|---|---|
| Component ID | The unique identifier of the component whose weblinks you want to retrieve. |
| Project ID | (Optional) The unique identifier of the project to which the component belongs. Used as a query parameter to filter results. |
Output
The node outputs an array of JSON objects representing the retrieved weblinks for the specified component. Each object corresponds to a single weblink and contains its details as returned by the iTwin Component Center API.
If multiple weblinks are returned, each will be output as a separate item in the output array.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the iTwin OAuth2 service.
- The node depends on the iTwin Component Center API being accessible.
- Proper configuration of the OAuth2 credentials in n8n is necessary for successful API calls.
Troubleshooting
Common issues:
- Invalid or missing Component ID will cause the operation to fail.
- Incorrect or expired API authentication token may result in authorization errors.
- Network connectivity problems can prevent reaching the iTwin API endpoint.
Error messages:
"Unknown operation: <operation>"indicates that the requested operation name is not recognized by the node. Ensure the operation name matches exactly.- Errors from the API (e.g., 401 Unauthorized, 404 Not Found) will be surfaced as node execution errors.
Resolutions:
- Verify that the Component ID and Project ID (if used) are correct and exist in the iTwin system.
- Check and refresh the OAuth2 credentials if authorization fails.
- Confirm network access to the iTwin API endpoints.
Links and References
- iTwin Developer Documentation
- iTwin Component Center API Reference (general link; specific endpoints depend on API version)