KanbanWP can post short messages to a Slack channel, a Discord channel, or both. You paste one incoming webhook URL per service and the plugin does the rest. No app or bot installation is involved.
What gets posted
Three events send a message:
- A task is created. The message names the person, the task and the board.
- A task is assigned. The message names the assignee and the task.
- A comment is added. The message names the person, the task and the first part of the comment.
Each message ends with a link that opens the task on its board. Moving cards, editing fields and deleting tasks do not post anything.
The same messages go to every URL you configure. The setting is site-wide, not per board, so all boards share the same channel.
Create the webhook URL
In Slack, create an incoming webhook for the channel you want, using Slack’s own app settings, and copy the URL it gives you.
In Discord, open the channel settings, go to Integrations, create a webhook and copy its URL.
Treat these URLs as secrets. Anyone with the URL can post to that channel.
Add it to KanbanWP
- Go to KanbanWP > Settings and open the Notifications tab.
- Paste the address into Slack webhook URL, Discord webhook URL, or both.
- Save the settings.
Leave a field empty to turn that service off.
Create a test task on any board. The message should appear in the channel within a few seconds.
How delivery works
KanbanWP sends one JSON request to each URL. The body contains the message under both a text key (which Slack reads) and a content key (which Discord reads), so the same payload works for both. Requests are sent in the background with a short timeout, and the board does not wait for them.
Because of that, delivery is best effort:
- There is no retry if the service is down.
- A failed delivery is not shown in the interface or recorded in the activity log.
If messages stop arriving, check that the webhook still exists on the Slack or Discord side, then paste the URL again and save.
Slack and Discord versus webhooks
The Slack and Discord fields are for ready-made chat messages with a fixed format. If you need structured data, a choice of events, or one destination per board, use webhooks instead, and handle the payload in a tool such as an automation service.
Notification preferences
These chat messages are separate from email and in-app notifications. Email, digests and the notify-on options sit on the same Notifications tab and are explained in Notifications.