KanbanWP connects to the rest of your WordPress site and to outside tools in a few focused ways. Nothing here requires an account with us, and there is nothing to license. Each integration is either a setting on your site or a hook you call from code.
What is available
| Integration | What it does | Where you set it up |
|---|---|---|
| WooCommerce | Creates a task for each new order and for each newly published product. | KanbanWP > Settings > Integrations |
| WordPress posts | Links cards to posts and pages, and can keep stages and post statuses in step. | Block editor sidebar and the Import Drafts screen |
| Forms | Turns a form submission into a task through the kanbanwp_form_submission action. | A small snippet in your theme or a code plugin |
| Slack and Discord | Posts a message when a task is created, assigned or commented on. | KanbanWP > Settings > Notifications |
| Webhooks | Sends signed JSON to your own URL when board events happen. | KanbanWP > Webhooks |
AI providers and the MCP server for AI agents are covered in their own section: see AI and MCP.
Choosing the right one
- You want chat alerts for a team. Use Slack or Discord. It is one URL per service and needs no code.
- You want another system to react to board changes. Use webhooks. They are per board, signed, and you pick the events.
- You sell with WooCommerce. Map orders and products to a board and stage, and your fulfillment or merchandising work shows up as cards.
- You publish content. Link cards to posts so the card and the post point at each other.
- You collect leads or requests through a form plugin. Fire the form action and each submission becomes a card on the board you choose.
Things to know
- WooCommerce, post linking and the form action are part of KanbanWP itself. The WooCommerce code only runs when WooCommerce is active.
- Slack and Discord messages are fire-and-forget. KanbanWP does not retry them or report a failure.
- Webhooks are scoped to a board, so you need permission to manage that board to add one.
- Everything that creates tasks respects the normal task rules: a task needs a board and a stage, and falls back to the board’s first stage when you do not name one.
If you want to build something that is not listed, the hooks and filters page and the REST API cover the developer side.