---
sidebar_position: 4
title: Plane Integration
---

# Plane Integration

Connect [Plane](https://plane.so) — the open-source project-management tool — so your agents can read and write projects, work items, cycles, modules, and comments. Plane uses an **API key**, not OAuth.

## How It Works

You provide three values: an API key, a workspace slug, and (optionally) a base URL. Zibby validates them (by listing the workspace's projects) before storing, then the `plane` skill talks to Plane's official MCP server.

## Connect Plane

1. In Plane, go to **Workspace Settings → API tokens** and create a personal API token (form `plane_api_...`)
2. Note your **workspace slug** — it's the segment in your Plane URL (`app.plane.so/<workspace-slug>/...`)
3. In the Zibby dashboard, go to **Settings → Integrations** and click **Connect Plane**
4. Paste the API key and workspace slug
5. **Base URL** — leave blank for Plane Cloud (`https://api.plane.so`). For self-hosted or Zibby-hosted Plane, set it to your instance's API base.

Zibby lists your workspace's projects to confirm the credentials work before saving.

| Field | Required | Notes |
|---|---|---|
| API key | Yes | From Workspace Settings → API tokens |
| Workspace slug | Yes | The `<slug>` in your Plane URL |
| Base URL | No | Defaults to `https://api.plane.so` (Plane Cloud). Set for self-hosted. |

## What Agents Can Do

Nodes that attach the [`plane` skill](../skills/index.md) get tools for projects, work items, cycles, modules, epics, and comments, backed by Plane's official MCP server.

## Reference keys (SDK / CLI)

When running agents directly, the connector reads `PLANE_API_KEY`, `PLANE_WORKSPACE_SLUG`, and `PLANE_BASE_URL` from the environment.

## Pairs well with hosted Plane

Plane is also in the [Managed Apps catalog](../apps/index.md) — you can host a Plane instance on Zibby and point this connector at it via the **Base URL** field.

## Troubleshooting

**"Workspace not found"** — double-check the workspace slug matches the segment in your Plane URL exactly.

**Self-hosted instance rejects the token** — confirm the **Base URL** points at the API base of your instance, not the web UI URL.
