OpenProject icon

OpenProject

Interact with OpenProject via API
Join our community

Actions199

Overview

This node operation allows you to create OAuth credentials for a storage service within the "File Links" resource. It is useful when you need to programmatically register or update OAuth 2.0 client credentials (client ID and client secret) associated with a specific storage identified by an ID. This can be part of automating integrations where secure access tokens are required to interact with external storage providers.

Practical examples include:

  • Automating the setup of OAuth credentials for cloud storage services before performing file operations.
  • Managing multiple storage connections dynamically by creating or updating their OAuth credentials via workflows.

Properties

Name Meaning
Id The unique identifier of the storage for which OAuth credentials are created. Must be a number.
Client Id The OAuth 2.0 client identifier issued by the storage provider.
Client Secret The OAuth 2.0 client secret key associated with the client ID.

Output

The node outputs JSON data representing the result of the OAuth credentials creation request. This typically includes confirmation details such as the stored client ID, possibly an internal identifier for the credentials, and status information from the storage service API.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the storage service's API endpoint that supports OAuth credential management.
  • Needs an API authentication token or API key configured in n8n credentials to authorize the request.
  • The node sends HTTP requests with JSON bodies containing the client ID and client secret.

Troubleshooting

  • Invalid Storage Id: If the provided storage ID does not exist or is incorrect, the API may return an error indicating the storage was not found. Verify the ID before running the node.
  • Authentication Errors: Missing or invalid API credentials for the storage service will cause authorization failures. Ensure the correct API key or token is configured.
  • Invalid Client Credentials: Providing malformed or empty client ID or client secret fields will likely cause the API to reject the request. Double-check these values.
  • Network Issues: Connectivity problems to the storage service API endpoint will prevent successful execution. Confirm network access and endpoint URLs.

Common error messages usually relate to HTTP 4xx or 5xx responses indicating bad requests, unauthorized access, or server errors. Reviewing the response body often provides clues on how to fix input parameters or credentials.

Links and References

Discussion