iTwin Component Center icon

iTwin Component Center

Comprehensive iTwin Component Center API

Overview

This node interacts with the iTwin Component Center API to retrieve information about manufacturers. Specifically, the "Get Manufacturers" operation fetches a list of manufacturers from the service. This is useful in scenarios where you need to integrate or synchronize manufacturer data into your workflows, such as asset management, procurement systems, or digital twin applications.

A practical example would be automating the retrieval of updated manufacturer lists to keep an internal database current or to populate dropdowns in user interfaces dynamically.

Properties

Name Meaning
Continuation Token A token used for pagination. The API returns up to 50 results per request along with a continuation token if more results are available. Provide this token to fetch the next page of results. If no token is provided, the first page is fetched.

Output

The output is an array of JSON objects representing manufacturers retrieved from the iTwin Component Center API. Each item corresponds to a single manufacturer record with its associated data fields as returned by the API.

If the response includes a continuation token, it indicates that more results are available and can be fetched by providing that token in subsequent requests.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the iTwin Component Center API.
  • The node depends on the iTwinOAuth2Api credential configured within n8n for OAuth2 authentication.
  • Internet access to reach the iTwin Component Center API endpoints.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Providing an incorrect continuation token may result in empty responses or errors.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • "Unknown operation: get-manufacturers": Indicates the operation parameter was not recognized; ensure the operation name is correct.
    • API errors related to authentication or rate limits will be surfaced as error messages; verify credentials and usage limits.
  • Resolutions:

    • Double-check that the API key credential is correctly set up and authorized.
    • Use the continuation token exactly as returned by the previous response without modification.
    • Ensure stable network connectivity and retry failed requests.

Links and References

Discussion