What the Slack integration does

Each new comment in your workspace is posted to a Slack channel you choose, as one message. The message updates itself when the comment changes, and it has a button to resolve the comment without leaving Slack. For an overview, see the Slack integration page.

Before you start

Plan — Slack is on the Team plan. See Understanding plans and pricing.
Role — only workspace owners and admins can connect Slack or choose channels. Other members can open the Integrations page and see that Slack is connected, but can't change anything.

Connect Slack

Open Integrations in your workspace sidebar.
Under Apps, click Connect next to Slack.
Approve the Huddlekit app in Slack.
You're taken back to Integrations, where a Slack connected message says: "Nothing posts until you pick a channel."

A new connection posts nothing until you choose where comments go, so pick a channel next.

Choose where comments are posted

Open the ⋯ menu on the Slack row and choose Configure. The Slack channels dialog saves each change as you make it. Click Done when you're finished.

Default channel

The Default channel is where comments go from every project that doesn't have its own channel. Choose No channel to stop posting for those projects without disconnecting.

Per-project channels

Every project in the workspace is listed under Per-project channels: websites, web apps and uploaded files, each with its type icon. Once there are eight or more, a search box appears. For each project you can choose:

Use the default — the project posts to the default channel. The option shows the default's name, or reads No channel when there is no default.
A channel from the list — the project posts there instead. A project's own channel always wins over the default.
Don't post — keep this project out of Slack even though a default channel is set. This option appears once a default exists.

Changing a channel only affects new comments. Messages already posted stay where they are and keep updating there. If the old channel was deleted, or it's private and the app is no longer in it, the comment's next change posts a new message in its new channel instead. If the old channel was archived, the Slack row shows Posting failed instead.

Before saving a channel, Huddlekit checks with Slack that it exists, that the app can see it, and that it isn't archived. A channel that won't work is refused with a reason (see Troubleshooting). The check can't tell whether a channel limits who may post, such as an announcement-only channel. If posting there fails, the Slack row shows Posting failed.

Private channels

Public channels work straight away. A private channel appears in the list, marked with a lock, only after the Huddlekit app has been invited to it in Slack. Invite the app, then reload the Integrations page to see the channel.

What each message shows

The comment number and project, such as #42 on Acme website, followed by the comment text.
The status (Open, In review, In progress or Resolved), who left the comment, and where they left it: a link to the page for websites and web apps, or the page number or time in a video for a media file.
For websites and web apps, the screenshot. Most screenshots appear as a View screenshot link rather than as an image in the message.
A Resolve button, which becomes Reopen once the comment is resolved, and an Open in Huddlekit button. For a web app comment, Open in Huddlekit takes you to the page in your own app where the comment was left.

Private comments are posted too. Send them to a channel only your team uses, not one you share with a client.

How messages stay up to date

Huddlekit edits the original message instead of posting a new one when:

the comment's status changes,
its text is edited, or
its screenshot finishes processing after the message was posted.

Connecting Slack doesn't post your existing comments. A comment is posted when it is created. An older comment is posted the first time its status or text changes.

Resolving and reopening from Slack

Resolve marks the comment as Resolved in Huddlekit, and the message changes to show Reopen. Reopen sets the comment back to Open.

Anyone who can see the message in Slack can press these buttons. They don't need a Huddlekit account, so choose your channels with that in mind.

Replies don't sync. A reply in Huddlekit doesn't appear in Slack, and a thread reply in Slack isn't sent to Huddlekit. To reply to the person who left the comment, click Open in Huddlekit. Priority, tags and assignees aren't shown in Slack either.

Disconnecting

Open the ⋯ menu on the Slack row and choose Disconnect. Huddlekit revokes its access to your Slack workspace. Messages already posted stay in Slack, but their buttons stop working. If Huddlekit couldn't revoke its access, the Disconnected from Slack message stays on screen until you close it and asks you to remove Huddlekit from your Slack settings to finish.

Disconnect is always available, including when the workspace is no longer on the Team plan.

Connecting again

If you later connect again and approve the same Slack workspace, your default channel and per-project channels come back, and a Slack reconnected message says: "Your channels resume. Invite the app to private channels again." Earlier messages update again the next time their comment changes. Approving a different Slack workspace starts fresh.

Disconnecting removes the app from every channel it was in. Public channels keep working, but private ones need the app invited back. Huddlekit checks your channels as you reconnect, and if it can't reach some of them, the Slack row shows Posting failed. Open Configure and hover over the badge to see which channels: "Huddlekit can't post in … since reconnecting. Invite the Huddlekit app to them again." Until you invite the app back, nothing is posted or updated in those channels, and what happens in the meantime isn't sent later. After that, existing messages pick up again the next time their comment changes.

If the workspace leaves the Team plan

New comments stop posting, and existing messages stop updating.
Pressing Resolve or Reopen does nothing except show the person who pressed it this note: "This Huddlekit workspace isn't on the Team plan anymore, so these buttons are paused."
The Slack row shows Paused to owners and admins. Channels can't be changed, but Disconnect still works.
Messages already posted keep the status they showed when posting paused, even after the workspace is back on Team, until their comment changes again.

All of this also applies while a payment is past due. Nothing is queued while posting is paused. Comments left during that time aren't posted when posting resumes, unless they change again afterwards.

Troubleshooting

The Slack row says Not configured. No default channel is set and no project has its own channel, so nothing is being posted. The dialog says: "Nothing is being posted yet. Pick a default channel below, or route individual projects."

"Slack does not recognise that channel. If it is private, invite the Huddlekit app to it first." Invite the app to the private channel in Slack, then try again.

"That channel is archived, so Slack will not accept messages in it." Unarchive the channel in Slack, or pick another one.

"Slack could not confirm that channel (…). Nothing was saved — please try again." Slack didn't answer the check. Choose the channel again.

"This Slack installation cannot read channels. Reconnect Slack to grant the missing permission." Choose Reconnect from the ⋯ menu and approve the app.

Reconnect needed. The Slack installation is missing a permission Huddlekit now needs. Slack sets an app's permissions when it is installed, so the only fix is to connect again. Choose Reconnect from the ⋯ menu and approve the app. Your channel choices are kept, even though the message after you approve still says "Nothing posts until you pick a channel."

"Could not load channels from Slack (…). Existing routing is unchanged." The channels you already chose aren't affected. Reload the page to try again. If it keeps happening, choose Reconnect. If the message mentions the Team plan, see If the workspace leaves the Team plan.

The Slack row says Posting failed. A comment couldn't be posted or updated, and Huddlekit has stopped trying. Open the ⋯ menu, choose Configure, and hover over Posting failed at the top of the dialog to see why and what to do:

"… is archived, so Huddlekit can't post there. Choose another channel."
"Huddlekit can't post in …. Invite the Huddlekit app to the channel, or choose another one." The channel was deleted, or it's private and the app isn't in it.
"Posting in … is restricted, so Huddlekit can't post there. Choose another channel." The channel only lets some people post, or only takes thread replies.
"Slack no longer accepts Huddlekit. Reconnect Slack." The app's access was revoked or expired in Slack, or an admin of your Slack organization hasn't granted it to this workspace.
"Huddlekit is missing a Slack permission. Reconnect Slack."
"Could not post to … (…)." Slack refused for another reason, named in brackets.

The badge clears the next time any comment posts or updates successfully, in any channel, and choosing Reconnect clears it too. So once it's gone, check that the channel that failed actually works again. Comments left while posting was failing aren't posted later, unless they change again afterwards.

A Huddlekit message was deleted in Slack. It is posted again the next time the comment changes, as long as its project still posts to a channel.

"Slack not connected". Connecting didn't finish, and you're back on Integrations with the reason. Nothing has changed, so click Connect again:

"Cancelled. Nothing changed." You cancelled on Slack's screen.
"That link expired. Start again." More than ten minutes passed before you approved.
"That link was already used. Start again." You finished in a different browser, or went back and approved twice.
"That link was not valid. Start again." The link from Slack was damaged or incomplete.
"You switched accounts partway. Sign back in and retry." You were signed in to Huddlekit as someone else by the time Slack sent you back.
"Only workspace admins can do this." or "Needs the Team plan." Your role or the workspace's plan changed while you were on Slack's screen.
Anything ending in "Try again." Something failed on the way back from Slack.

For other ways to send feedback on, see Connecting Linear, Connecting Zapier and Setting up webhooks.

Connecting Slack