Skip to content

Kanbanomy can post task updates to a Slack channel: “Maya assigned Ethan to “Logo” in Acme. Due: 14 Nov.” with a link to the task. It uses a Slack incoming webhook, so there is no Slack app to install on your site and nothing to sign in to.

  1. In Slack, add the Incoming Webhooks app to your workspace, pick the channel, and copy the address it gives you (it starts with https://hooks.slack.com/services/).
  2. In WordPress, go to Kanbanomy > Settings > Connections.
  3. Paste the address, choose what to post, and press Connect.

Kanbanomy sends a test message straight away. If Slack refuses it, nothing is saved and you see what Slack said, for example “Not connected: Slack said this webhook no longer exists in Slack.”

Only addresses on hooks.slack.com over https are accepted. Addresses on your own network (localhost, 10.x, 192.168.x and the like) are always refused.

New channels post two kinds of message: A task is assigned and Someone is @mentioned in a comment. Each channel can also post:

Event Example
A task changes status Maya moved “Logo” to Done in Acme.
A comment is added Maya commented on “Logo” in Acme: “Looks good”
A task is created Maya created “Logo” in Acme.
A client approves or asks for changes Lena approved “Logo” in Acme.
A discussion is started Maya started the discussion “Kickoff” in Acme.
Someone replies in a discussion Lena replied in “Kickoff” in Acme: “Thanks, see you Monday”
Tasks due tomorrow One message a day, at the digest hour set under Notifications, listing up to 20 tasks.

A comment that @mentions people is posted once, naming everyone mentioned. A change made by an automation rule is posted as “Automation (rule: )”.

A Slack channel is team-facing, but the people in it may not all be on the project, and agencies often share a channel with their clients. So a message carries only what a client of that project could see:

  • nothing about an Internal task,
  • no Team only comment and no team-only discussion,
  • no budget figures,
  • nothing at all from a Private project.

This rule is fixed. There is no setting that turns it off.

Open the project, then its Connections tab (front end or admin). Project owners and Project Managers see this tab; members and clients do not.

  • Uses the site channel is the default: the project posts to the site channel with the site’s events.
  • Paste another address to give the project its own channel with its own events. Use the site channel removes it again.
  • Tick Don’t post this project to Slack to keep one project out of Slack entirely.

Messages are sent in the background, so saving a task never waits for Slack. If Slack is down or slow, Kanbanomy tries again after 1 minute, 5 minutes and 30 minutes. If Slack says the webhook or channel no longer exists, it stops at once.

The card shows Not delivering and the reason (“Last message failed: channel not found.”). Open Delivery log to see the last 20 messages for that channel, with the time, the event and whether it was delivered. Press Send test message after you fix the address in Slack.

The full webhook address is never shown again after you save it: the screen shows only the start and the last few characters. Disconnect deletes it.

Turn off Integrations under Settings > Features to stop all messages and hide the Connections screens. A project can override it the same way as any other feature.

  • kanbanomy_integrations (filter) - the list of channel providers. Add a class that extends ProjectFlow\Integrations\Provider to add another chat tool without touching Kanbanomy’s code.
  • kanbanomy_integration_message (filter) - change or drop (return null) a message before it is queued. Receives the message array (event, project_id, task_id, text, link, link_label).
  • kanbanomy_slack_webhook_hosts (filter) - hosts accepted for Slack addresses. Default hooks.slack.com.
  • kanbanomy_integration_failed (action) - fires when a message fails for good, with the provider slug, channel key, message and reason.

REST routes (managers only): GET /kanbanomy/v1/integrations, PUT|DELETE /kanbanomy/v1/integrations/{provider}, POST /kanbanomy/v1/integrations/{provider}/test, and the same under /kanbanomy/v1/projects/{id}/integrations/{provider}.