Slack

Pro and above. Setup is an incoming webhook URL.

Connect

Create a Slack app

Go to api.slack.com/apps → Create New App → From scratch. Name it "Annot8" and pick your workspace.

In the app, open Incoming Webhooks and turn Activate Incoming Webhooks on. Click Add New Webhook to Workspace, choose the channel, and copy the URL. It looks like https://hooks.slack.com/services/....

Paste it into Annot8

Integrations in the sidebar → Slack → paste the webhook URL → Connect, then Test to confirm it lands.

Enable it per project

Project → Integrations → toggle Slack on for the projects that should post there.

What gets posted

Every new thread on an enabled project posts a message carrying the project name, the author, the comment, and a link to the page.

Automations can also post to Slack, but only for threads matching their conditions — and those messages name the rule that fired, so you can tell "everything" from "the critical-bug rule".

Different channels per project

Connect Slack once, then set a per-project override with a different webhook URL under Project → Integrations. One credential, per-project routing.

Create the extra webhook in the same Slack app — Add New Webhook to Workspace again, choosing a different channel.

Troubleshooting

Nothing arrives. A Slack webhook is bound to the channel it was created for. If that channel was archived, renamed, or deleted, the webhook stops working — create a new one and update the URL. The integration's last-delivery status will show the error.

Messages arrive twice. You've probably connected Slack at the workspace level and set a project override pointing at the same channel. Clear one.

Practical advice

Give it a dedicated channel — #feedback — rather than a busy team channel. On a project with real volume, a shared channel is unreadable within a day. If the volume is still too high, switch the workspace integration off and drive Slack from an automation that only posts high and critical threads.