DocuWare Cloud OAuth Bearer Token Webhook (n8n HTTP Request)

Get a DocuWare Cloud OAuth2 Bearer Token on demand—via an n8n webhook

This n8n workflow exposes a secured webhook that accepts your DocuWare Cloud credentials, exchanges them for an OAuth2 bearer access token using DocuWare’s /connect/token endpoint, and returns the token_type and access_token to the caller.

What this workflow does

• Receives a POST request on an n8n webhook endpoint protected with header authentication.
• Reads DocuWare Cloud credentials from request headers: x-dw-cloudid, x-dw-username, and x-dw-password.
• Requests an OAuth2 access token by sending a form-urlencoded POST to DocuWare Cloud’s identity service /connect/token using the password grant.
• Responds with JSON containing exactly the token_type and access_token returned by DocuWare.

Use cases

• Centralized authentication for DocuWare Cloud API calls: other services can obtain a bearer token through one controlled webhook.
• SaaS integrations: securely mint short-lived access tokens without embedding DocuWare credentials directly in every consumer.
• Automation engineers: streamline setup for downstream workflows that require a bearer token for DocuWare Cloud endpoints.

Technical details

• n8n nodes used: Webhook, Sticky Note, HTTP Request, Respond to Webhook.
• Security: webhook secured with Header Auth; only authorized callers can request tokens.
• Required headers: x-dw-cloudid, x-dw-username, x-dw-password (plus your configured header-auth credential name/value).
• Region support: if your tenant is not on login-emea.docuware.cloud, update the identity service base URL in the HTTP request to match your region.

Perfect for n8n automation workflows that need a fast, reliable DocuWare Cloud OAuth bearer token exchange.