Let ChatGPT or Claude do the thinking. Let Workden manage the work.
Two connectors planned, zero shipped — and we will not pretend otherwise. Workden has no live third-party integrations today. This page describes exactly what they will be, so you can judge the plan rather than a marketing claim.
Planned
What we are building.
ChatGPT
In developmentReach your Workden workspace from ChatGPT through OpenAI’s supported connector mechanism, so you can ask about your own pipeline where you already work.
Claude
In developmentThe same connection from Claude, through Anthropic’s supported connector mechanism, with identical permission handling.
A consumer ChatGPT or Claude subscription is not an API account. Anyone telling you otherwise is guessing.
The model
How the connection will work.
Through whatever official connector or authorisation flow each provider supports at launch — and through the permission chain Workden already enforces today.
- You authorise the connection on the provider's side, using their own flow.
- Workden resolves that connection to a specific Workden user — not to a shared service account.
- Every request is then narrowed by that person's workspace, role, module permissions and tool permissions.
- Only the fields needed to answer the question are returned, scoped to their workspace at the database.
Commitments
What Workden will never ask you for.
- Your ChatGPT or Claude password.
- A session cookie copied out of your browser.
- Permission to scrape or automate a provider's web session.
- Acceptance of the claim that your existing AI subscription doubles as a server-side API account for us. It does not.
If a connector cannot be built within a provider's supported mechanism, we will not ship a workaround that gets there by other means.