Kanera talks to the rest of your stack.
Post live card activity into Slack, Discord, Telegram, or Zulip in two clicks. Automate workflows with signed webhooks, scoped REST API, and native Model Context Protocol (MCP).
AI agents welcome, and they have their own page.
Claude, ChatGPT, Copilot, Cursor, and Codex can all work on your real boards through an MCP server, a command line, and an SDK — with a read-only key when you want one, and the AI of your choosing rather than ours.
Six shapes that cover
most of what teams need.
Because the integration is yours, you decide which tool is the source of truth, which events sync, how conflicts resolve, and how an external update should look once it lands in Kanera.
Kanera ↔ Trello
Keep two trackers honest
Map Trello cards to Kanera cards, hold the mapping in external links so the sync stays idempotent, and decide exactly which updates flow in each direction.
Kanera → Dashboard
Reporting your leadership will read
Pull cards, custom fields, assignments, labels, status, and activity into a live operational or client-facing dashboard, without giving everyone access to every board.
Slack → Kanera
Capture work where it gets mentioned
Chat destinations post outward already. Use the API for the return trip: turn a message, a support thread, or a form response into a real card with an owner and a due date.
Kanera ↔ GitHub
Connect delivery to development
Link cards to issues or pull requests, and move the card when the branch merges, the deploy lands, or the check goes red.
Your app → Kanera
Internal tools on top of Kanera
Onboarding portals, support workflows, operations forms, and admin panels that write into Kanera behind the scenes, for people who never open it directly.
Anything → Kanera
Migrate once, then keep it in step
Create boards, cards, comments, checklists, custom fields, labels, notes, and attachments from any source, then leave the job running as a sync instead of a one-off import.
Post the work
where your team already talks.
Chat destinations are part of Kanera. A workspace admin picks a provider, pastes the connection the chat tool generates, and chooses which card events are worth posting. Kanera formats every message natively for that platform, with the card title linked and its workspace and board for context.
Included in Pro, the 30-day Pro trial, and self-hosted Kanera.
Paste an incoming webhook URL from a Slack app and choose the channel it posts to.
Paste a channel webhook URL from Discord channel settings. Mentions are never parsed.
Add a bot token and chat ID, and target one topic thread in a group when you need it.
Paste a Slack-compatible webhook URL from Zulip Cloud or your own Zulip server.
- Card created
- Status changed
- Priority changed
- Title changed
- Description changed
- Comment created
Scoped to one workspace or standalone board, so a client channel and an internal channel never see each other's work. Card links still respect board permissions.
- Choose which events each channel receives
- Map your own Priority custom field for escalation posts
- Send a test, pause, or replace a connection in place
- Delivery history with retries when a provider fails
- Credentials stored encrypted and never shown again
An API to ask,
and webhooks to be told.
Read and write every part of a board from outside Kanera, and get pushed the changes as they happen instead of polling for them. Between the two you can sync in real time, trigger external workflows, or build on Kanera as the source of truth.
Included in Pro, the 30-day Pro trial, and self-hosted Kanera, which has no plan checks at all.
Reach into Kanera from anywhere, and change anything you could change by hand.
If a person can do it on a board, your code can do it too — cards, comments, checklists, notes, files, fields, labels, and who is on what. Point a reporting tool at it, run a nightly sync, move a decade of work in from somewhere else, or put a simple front end on top for people who should never see a board.
- Full access to boards, cards, comments, checklists, notes, and attachments
- Custom fields, labels, activity, and assignments
- API keys with Read, Write, and Admin access levels
- A typed TypeScript SDK, or plain HTTP in any language
- Interactive reference, Swagger, and an OpenAPI document
Get told the moment something changes, instead of asking over and over.
The second a card moves, Kanera tells whatever you point it at. Kick off a deploy, refresh a dashboard, update the record in your CRM, or keep another tool in step — and every message is signed, so you know it really came from Kanera before you act on it.
- Choose which events each destination receives
- Review delivery history and retry failed deliveries
- Pause destinations and rotate secrets
- Signed payloads, verified in one call with the SDK
- Multiple destinations per workspace
Built for the integration
you are still running next year.
Getting one working is the easy part. What decides whether it is still running in a year is the unglamorous stuff: the tenth re-run, the first outage, and the day somebody asks who moved the card.
A card your sync job creates shows up on everyone's board at once, exactly as if a colleague had just added it. No refreshing, no waiting, and nobody planning their morning around a board that is a minute out of date.
Every write is recorded in card history with the credential behind it, so a change made by an integration is distinguishable from one made by a person. When a sync misbehaves, the evidence is already in the card.
Kanera remembers which card came from which record in the other system, so a sync can be re-run, resumed, or replayed without creating everything a second time. No hidden tracking ids stuffed into card descriptions, where somebody will eventually delete them.
See what was sent, retry what failed, pause a destination while you fix the thing at the other end, and roll a secret without starting over. The parts you actually want at 2am are in the product, not in a support ticket.
A key belongs to the one workspace or board it was made in, so the tool you built for a client account cannot see an internal board. Give each integration its own, and turning one off never disturbs the rest.
Questions about Kanera integrations
Is this a technical API reference?
No. Developers can use the API docs when they need endpoint-level details.
What can I build with the REST API?
You can build custom workflows, reporting tools, sync jobs, internal apps, migration scripts, and integrations that create or update Kanera boards, cards, comments, checklists, notes, attachments, custom fields, labels, activity, and assignments.
What are webhooks used for?
Webhooks let external systems react when work changes in Kanera. You can use them to sync data, send notifications, update dashboards, trigger automations, or keep another tool aligned with Kanera.
Can Kanera post updates into Slack or another chat tool?
Yes, and it is built in. A workspace admin adds a chat destination for Slack, Discord, Telegram, or Zulip, pastes the connection that tool generates, and chooses which card events to post: card created, status changed, priority changed, title changed, description changed, or comment created.
Each destination can be tested, paused, reconnected, and reviewed through its delivery history, and Kanera formats every message natively for that platform. Chat destinations are included in Pro, a Pro trial, and self-hosted Kanera.
Which plans include the API, webhooks, and chat destinations?
The REST API, custom webhooks, the MCP server, chat destinations, and personal ntfy, Gotify, and webhook notification delivery are included in Pro, in the 30-day Pro trial, and in self-hosted Kanera, which has no plan checks at all.
On hosted Free they cannot be set up, and a downgrade revokes API keys, pauses existing webhooks and chat destinations, and switches personal destinations off rather than deleting any of them. Upgrading again restores what was switched off.
The in-app notification drawer, email, browser push, and per-workspace notification rules are available on every plan.
Can Kanera sync with tools like Trello or Jira?
Yes, through integrations you build against the API and webhooks. You control how objects map, which events sync, and how conflicts and updates are handled.
Can I send my own notifications somewhere other than email?
Yes. Each person can send their own Kanera notifications to an ntfy topic, a self-hosted Gotify server, or their own HTTPS endpoint as signed JSON, with separate notification type preferences per destination.
These personal channels are included in Pro, a Pro trial, and self-hosted Kanera, and self-hosted operators can allow receivers on their internal network.
Can integration updates be tracked?
Yes. Changes made by integrations are attributed in Kanera's activity history, so teams can see what changed and where the update came from.
Can I control which webhook events are sent?
Yes. Kanera lets you choose which events each webhook destination receives, review delivery history, retry failures, pause destinations, and rotate secrets.
Is Kanera only for prebuilt integrations?
No. The API, webhooks, and MCP server are designed for custom workflows that connect Kanera to your team's own tools, systems, and processes.
Build the workflow
your team actually needs.
Post work into the channels your team already watches, then connect Kanera to your own systems with an API and webhooks built to be operated, not just switched on.