Slack integration

Website feedback, posted to the Slack channel your team already reads.

When a client pins a comment on the live site, the channel gets it straight away: what they said, the element they clicked, the page, and the screenshot. Nobody has to go looking.

Setup guide
At a glance

What you get in Slack

A pin becomes
A message in the channel you choose for that dock
The message carries
The comment, the element it was left on, the page, the screenshot and a link to the full pin
Also posts
Replies, status changes and resolutions, by default
Connects by
A Slack incoming webhook: no API keys, no developer, about five minutes
Access to Slack
Write-only, to one channel. Layerdock cannot read your workspace
Plans
Pro and Agency
Setup

Connect Slack in three steps

The Slack setup guide has every screen and what to do if something goes wrong.

  1. Step 1

    Create a webhook in Slack

    In Slack’s app directory, create an app, switch on Incoming Webhooks and add one for the channel you want. Layerdock’s button pre-fills the form.

  2. Step 2

    Paste the URL into Layerdock

    Choose the dock, paste the webhook URL and save. The URL is encrypted at rest and never shown again.

  3. Step 3

    Send a test

    Press Test and a message arrives in the channel. Then leave a real pin on your site to see the full format.

Good to know

How it behaves

One channel per dock

A webhook belongs to one channel, and each dock has its own. Client A’s feedback goes to #client-a and never shows up in #client-b.

Replies arrive as separate messages

Slack’s incoming webhooks return no message id, so there is nothing to thread onto. A busy pin produces several messages in the channel.

Long comments are trimmed

The message shows the first 300 characters and links to the full pin, so the channel stays readable during a long review session.

An admin can do the Slack half

On workspaces where only admins install apps, the admin creates the webhook and hands over one URL. They do not need a Layerdock account.

Ready when you are

Make the next
website review easier.

Give your team and clients one clear place to see the issue, capture the context, and share the fix.

Explore the tools
FAQs

Frequently asked questions

What to know before connecting Slack.

Can Layerdock read messages in my Slack workspace?

No. An incoming webhook is write-only and bound to one channel. Layerdock stores only the webhook URL, encrypted, and an optional display name.

Can different client sites post to different Slack channels?

Yes. Each dock connects its own webhook, and each webhook posts to one channel.

Are replies threaded under the original message?

Not today. Slack’s incoming webhooks do not support threading, so each reply is its own message with a link to the pin.

Can I get feedback in Slack and in an issue tracker at once?

Yes. A dock can have Slack connected alongside Jira, Linear, GitHub, Trello or ClickUp, so the channel sees the pin and the tracker gets the ticket.

Which Layerdock plans include integrations?

Pro ($19/mo) and Agency ($69/mo), both per workspace with unlimited reviewers. The Free plan does not include outbound integrations.