feat: use API to create/edit workflows

[alexwilson1]

Is your proposal related to a problem?

Currently, workflows in Cal.com can only be created or edited through the UI unless the user is part of a team. This limitation makes it difficult to automate workflow creation, manage workflows programmatically, or integrate workflow setup into provisioning scripts or external systems.

Describe the solution you'd like

I would like the Cal.com V2 API to support creating, updating, retrieving, and deleting workflows. Ideally, the API would expose endpoints such as:

• POST /v2/workflows — create a workflow
• GET /v2/workflows/:id — retrieve workflow details
• PATCH /v2/workflows/:id — update workflow settings
• DELETE /v2/workflows/:id — remove a workflow
• Potential support for workflow steps, triggers, event types, and actions

This would allow developers to fully manage workflows without relying on the UI, enabling automation and streamlined integration into developer tooling.

Describe alternatives you've considered

• Managing workflows exclusively through the UI (doesn’t scale and cannot be automated).
• Using team-level APIs, which support some workflow-related operations, but are not available unless operating within a team account.
• Scripting browser automation to replicate UI operations (fragile and not ideal).

None of these fully solve the need for a programmatic, stable interface.

Additional context

Workflows can currently be edited through the UI here:
https://app.cal.com/workflows

Having API support for workflows aligns with Cal.com’s existing API philosophy, and would help with automated onboarding, multi–tenant setups, and infrastructure-as-code patterns.

[linear]

CAL-6862

[CarinaWolli]

@JDP-Neo