Integrations
Coco Kanban connects to the tools your team already lives in — your code host, your chat. Connect a service once at the workspace level, then wire it up per project.
Plan: Business and above (Jira import is available on Free — see Jira import)
What you can connect
| Integration | What it does | Where you set it up |
|---|---|---|
| GitHub | Link GitHub repos to projects. Sync branches, commits and pull requests to work items. Push a work item to the repo as a GitHub issue. | Workspace settings → Integrations |
| Bitbucket | Link Bitbucket repos to projects. Sync branches, commits and pull requests to work items. Push a work item to the repo as a Bitbucket issue. | Workspace settings → Integrations |
| Slack | Send work-item and comment notifications into Slack channels, per project. | Workspace settings → Integrations → Slack |
| Microsoft Teams | Post work-item and comment notifications into Teams channels via a channel Workflow. | Workspace settings → Teams |
| Jira import | One-off migration of a Jira project into a Coco Kanban project. | Workspace settings → Imports |
Getting started
Open the integrations page
- Click your workspace name, then Settings.
- Choose Integrations in the settings sidebar.
You'll see one card per available integration, each with a Connect button. Once a service is connected, the card shows a green Connected badge — for GitHub and Bitbucket it also shows the account name the credentials belong to.
📷 Screenshot: Workspace settings → Integrations, showing the GitHub, Bitbucket and Slack cards with one of them marked Connected.
Who can connect
Connecting and disconnecting an integration is workspace-admin only. The Integrations settings page itself only appears in the settings sidebar for admins. Once an integration is connected, any workspace member can use it — for example, pushing a work item to a linked repo.
How the pieces fit together
Integrations have two levels:
- Workspace level — the credential. You connect GitHub, Bitbucket or Slack once for the whole workspace, using a token you generate on their side.
- Project level — the link. You then link a specific repo to a specific project (Project settings → Integrations), or map a project to a Slack/Teams channel.
Nothing flows until both levels exist. A connected GitHub account with no repo linked to a project won't do anything; a linked repo with no connected account can't exist.
Connecting each service
Each service has its own connect form and its own gotchas. Full instructions live on the dedicated pages:
- GitHub & Bitbucket — personal access tokens, app passwords, linking a repo to a project, the "Push to repo" button, and what actually syncs.
- Slack — creating a Slack app, the bot token, and mapping projects to channels.
- Microsoft Teams — connecting a channel with a Teams Workflow webhook. No Azure app or admin consent needed.
- Jira import — moving an existing Jira project across.
Disconnecting
On the Integrations page, a connected GitHub or Bitbucket card shows a Disconnect button instead of Connect. You'll get a confirmation dialog before anything happens.
Disconnecting stops the sync. Repos that were linked to projects and work items that were already pushed to the repo stay where they are — the links just go stale. Reconnecting the same account restores the sync without recreating your project links.
Slack and Microsoft Teams are disconnected from their own settings pages, not from the Integrations card list.
Tips
- Use a service account. GitHub and Bitbucket credentials are stored per workspace, not per user. If you connect with your personal token and later leave the company, the integration breaks for everyone. A shared bot/service account avoids that.
- Paste tokens as plain text. Copying a token out of a formatted document (Word, Google Docs, Notion) can silently substitute an em-dash or smart quote. Coco Kanban rejects this with a clear error rather than failing mysteriously, but it's easier to just copy straight from the provider.
- Credentials are encrypted at rest. Tokens, app passwords and webhook secrets are encrypted before they're stored.
Limits & good to know
- One account per provider per workspace. You can't connect two GitHub organisations to the same workspace with different tokens. Attempting a second connection returns "Workspace is already connected".
- GitHub and Bitbucket only, for code hosts. GitLab, Azure DevOps and self-hosted Git servers aren't supported.
- Slack is one-way. Coco Kanban posts into Slack; you can't create or update work items from Slack.
- Microsoft Teams is one-way for notifications. Replies in Teams do not appear as work-item comments in the standard Workflow-webhook setup.
- Integrations don't back-fill. Connecting Slack today won't post yesterday's work items. Notifications start from the moment the connection is live.