Bundles & App Kits

Export and import complete Taskade Genesis apps and workspaces as portable bundles using the Action API v2.

What Are Bundles?

A bundle is a portable snapshot of a workspace's building blocks — projects, agents, automations, templates, media, and Genesis app source — packaged so you can move it between workspaces, accounts, and environments. Bundles power app sharing, backups, and the community App Kits.

Bundles come in two flavors:

Flavor	Format	Includes media?	Use when
JSON (SpaceBundleData)	application/json	No (media items are skipped)	Programmatic export/import, diffing, version control
ZIP / .tsk	binary archive	Yes (media files included)	Full-fidelity transfer, backups, distribution

Bundle endpoints are part of the Action API v2. Authenticate with a personal access token. Exporting requires the bundle permission on the space; importing is gated by your plan (see Plan Limits).

---

What's Included in a Bundle

Component	Details
Projects	Tasks, custom fields, views, and structure
Templates	Reusable project/task templates
AI Agents	System prompts, tone, and knowledge configuration
Automations	Triggers, actions, and full flow logic
Genesis apps	App source files (apps/{id}/…)
Media	Uploaded files and assets (ZIP/.tsk only)

---

API Reference

Export a Bundle (JSON) — v1

get

Export a space (subspace / app) as a JSON bundle (SpaceBundleData v1). Returns all agents, automations, projects, templates, and apps. Media items are excluded — use the ZIP export or download media separately via the media endpoints.

Authorizations

oAuthAuthorizationCode & personalAccessToken

OAuth2authorizationCodeRequired

Authorization URL: Token URL:

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Path parameters

spaceIdstringRequired

The space (subspace / app) ID to export.

Responses

200

Exported workspace bundle

application/json

Exported workspace bundle

okboolean · enumRequiredPossible values:

4XX

Error description

application/json

get/bundles/{spaceId}/export

HTTPcURLJavaScriptPython

GET /api/v1/bundles/{spaceId}/export HTTP/1.1
Host: www.taskade.com
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*

{
  "ok": true,
  "item": {
    "version": "1",
    "items": {
      "ANY_ADDITIONAL_PROPERTY": {
        "type": "text",
        "ANY_ADDITIONAL_PROPERTY": "anything"
      }
    }
  }
}

Export a Bundle (ZIP / .tsk) — v1

get

Export a space (subspace / app) as a ZIP bundle containing all agents, automations, projects, templates, apps, and media files. The ZIP includes a manifest.json, individual item files in type directories, and media files downloaded from storage.

Authorizations

oAuthAuthorizationCode & personalAccessToken

OAuth2authorizationCodeRequired

Authorization URL: Token URL:

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Path parameters

spaceIdstringRequired

The space (subspace / app) ID to export.

Query parameters

formatstring · enumOptional

Export format: "zip" (default) or "tsk" (.tsk app kit).

Default: zipPossible values:

Responses

4XX

Error description

application/json

Error description

okboolean · enumRequiredPossible values:

messagestringRequired

codestringRequired

statusMessagestringRequired

get/bundles/{spaceId}/export/zip

HTTPcURLJavaScriptPython

GET /api/v1/bundles/{spaceId}/export/zip HTTP/1.1
Host: www.taskade.com
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*

4XX

Error description

{
  "ok": false,
  "message": "text",
  "code": "text",
  "statusMessage": "text"
}

Import a Bundle (JSON) — v1

post

Import a JSON bundle (agents, automations, projects, templates, apps) into a workspace. The bundle is validated against the SpaceBundleData v1 schema and all items are installed into the target workspace. Media items are not supported — use the ZIP import or upload media separately via the media endpoints after import.

Authorizations

oAuthAuthorizationCode & personalAccessToken

OAuth2authorizationCodeRequired

Authorization URL: Token URL:

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Path parameters

workspaceIdstringRequired

The target workspace ID to import the bundle into.

Body

application/json

Responses

200

Successful bundle import

application/json

Successful bundle import

okboolean · enumRequiredPossible values:

4XX

Error description

application/json

post/bundles/{workspaceId}/import

HTTPcURLJavaScriptPython

POST /api/v1/bundles/{workspaceId}/import HTTP/1.1
Host: www.taskade.com
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 119

{
  "bundleData": {
    "version": "1",
    "items": {
      "ANY_ADDITIONAL_PROPERTY": {
        "type": "text",
        "ANY_ADDITIONAL_PROPERTY": "anything"
      }
    }
  }
}

{
  "ok": true,
  "item": {
    "id": "text",
    "projectCount": 1,
    "flowCount": 1,
    "agentCount": 1,
    "templateCount": 1,
    "mediaCount": 1,
    "appCount": 1
  }
}

Import a Bundle (ZIP / .tsk) — v1

post

Import a ZIP/.tsk bundle (exported from the export/zip endpoint) into a workspace. All items are installed into the target workspace. The ZIP must contain valid bundle data (either bundle.json or directory structure). Media files in the ZIP are re-uploaded to storage automatically. Send the file as the raw request body with Content-Type: application/zip, application/octet-stream, or application/x-tsk.

Authorizations

oAuthAuthorizationCode & personalAccessToken

OAuth2authorizationCodeRequired

Authorization URL: Token URL:

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Path parameters

workspaceIdstringRequired

The target workspace ID to import the bundle into.

Responses

200

Successful ZIP bundle import

application/json

Successful ZIP bundle import

okboolean · enumRequiredPossible values:

4XX

Error description

application/json

post/bundles/{workspaceId}/import/zip

HTTPcURLJavaScriptPython

POST /api/v1/bundles/{workspaceId}/import/zip HTTP/1.1
Host: www.taskade.com
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*

{
  "ok": true,
  "item": {
    "id": "text",
    "projectCount": 1,
    "flowCount": 1,
    "agentCount": 1,
    "templateCount": 1,
    "mediaCount": 1,
    "appCount": 1
  }
}

---

Export a bundle (JSON) — Action API v2

POST /api/v2/exportBundle — returns the full SpaceBundleData object (no binary media).

cURL

curl -X POST https://www.taskade.com/api/v2/exportBundle \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "spaceId": "SPACE_ID" }'

TypeScript

Response:

{
  "ok": true,
  "item": {
    "version": "1",
    "name": "Sales CRM",
    "description": "Pipeline + outreach agent",
    "items": {
      "proj_abc": { "type": "space-bundle-project-item", "projectId": "proj_abc", "root": { } },
      "agent_xyz": { "type": "space-bundle-agent-item", "agentId": "agent_xyz", "template": { } }
    }
  }
}

Import a bundle (JSON)

POST /api/v2/importBundle — installs a SpaceBundleData object into a target workspace.

curl -X POST https://www.taskade.com/api/v2/importBundle \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "workspaceId": "WORKSPACE_ID", "bundleData": { "version": "1", "items": { } } }'

Response reports what was created:

{
  "ok": true,
  "item": {
    "id": "WORKSPACE_ID",
    "projectCount": 3,
    "flowCount": 1,
    "agentCount": 2,
    "templateCount": 0,
    "mediaCount": 0,
    "appCount": 1
  }
}

The JSON import skips media items — use the ZIP/.tsk flavor to carry media. Importing always creates new resources; it never overwrites existing projects or agents.

Export / import as ZIP (.tsk)

For full-fidelity transfer including media, use the binary endpoints:

# Export as a binary .tsk archive (or ?format=zip)
curl -X GET "https://www.taskade.com/api/v2/bundles/SPACE_ID/export/zip?format=tsk" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  --output workspace.tsk

# Import a .tsk / .zip archive (raw binary body, max 50 MB)
curl -X POST "https://www.taskade.com/api/v2/importBundleZip?workspaceId=WORKSPACE_ID" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/zip" \
  --data-binary @workspace.tsk

---

The SpaceBundleData Schema

The JSON bundle is a flat map of items keyed by id:

interface SpaceBundleData {
  version: "1";
  name?: string;
  description?: string;
  items: Record<string, SpaceBundleDataItem>;
}

type SpaceBundleDataItem =
  | { type: "space-bundle-project-item";  projectId: string; root: object; preferences?: object }
  | { type: "space-bundle-template-item"; projectId: string; root: object }
  | { type: "space-bundle-agent-item";    agentId: string;   template: object; dependsOn?: string[] }
  | { type: "space-bundle-flow-item";     flowId: string;    template: object; dependsOn?: string[] }
  | { type: "space-bundle-app-item";      appId: string;     files: object; branding?: object }
  | { type: "space-bundle-media-item";    mediaId: string };

The .tsk Format

A .tsk file is a ZIP archive with a manifest and type-based directories:

manifest.json          # { version, exportedAt, spaceId, spaceMetadata, name?, description? }
projects/{id}.json
templates/{id}.json
agents/{id}.json
automations/{id}.json
apps/{id}/…             # Genesis app source as a real directory tree
media/{mediaId}/metadata.json
media/{mediaId}/{originalFilename}

Two manifest format versions exist: 1.0 stored apps as a single JSON blob; 1.1 (current export) spreads app source as a real directory tree. Import accepts both.

---

Plan Limits

Imports are checked per item type against your plan:

Item	Free	Paid
Agents	1	Varies by plan
Genesis apps	3	Unlimited
Automations (flows)	— (paid only)	Enabled

The public ZIP import is limited to 50 MB per archive. Bundle operations are rate-limited to protect large transfers.

---

Use Cases

• Share apps across workspaces — export from one workspace, import into another.

• Back up before big changes — snapshot a workspace and restore later.

• Distribute through the community — publish a .tsk so others import a working app in seconds.

• Template creation — build once, export, and reimport for fresh copies.

---

Next Steps

• Action API v2 Reference — the full v2 operation set

• Authentication — get your API token

• MCP Connectors — connect your imported apps to external services