Skip to main content
GET
Export a workflow as a bundle
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.

v2 compatibility notes

GET /api/v2/workflows/exportBundle returns {bundle}, a portable v1 Bundle.

Authentication

External App credential or platform API key, or a Personal key. Requires permission workflows:read at the workflow’s home: a workflow that is malformed, unknown, trashed, unhomed or outside the caller’s reach answers 404. A Personal key acts as its owner, narrowed by its scopes.

Behavior

Query parameter id (required, once). The bundle holds the workflow’s active version and its dependency closure (agents, skills, tools, procedures), for POST /api/v2/bundles/import in another deployment. Deployment-local ids are stripped; secret names and Connection names in the bindings are kept (names, never values). exportedFrom.by names the caller (a Personal key’s owner, or the app or key), never an email. A closure that includes a personal agent answers 409, as does a workflow with no published version.

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Path Parameters

workflowId
string
required

The workflow.

Minimum string length: 1

Response

Success

data
object
required
meta
object
required