Slack

What the Slack integration does

Connect a Slack channel and LinkDrop posts a short message there, with a link back, whenever one of these happens:

• Opened: a new recipient opens one of your share links. Your own opens never post.
• Introduced: a recipient types their name or email on a link, so you know who is reading.
• Visit brief: a recipient finished reading and the brief is ready.
• Replaced: a document got a new version, with what changed.
• Deleted: a document was deleted, with a count of the live links that stopped resolving with it.
• New link: someone created a share link for a document or a project.
• Added: a project was created, a new document finished uploading, or a document was added to a project.

When the reader of a visit brief is one of your contacts with a recent reader summary, the summary is posted as a reply in the thread of that brief, once per visit. It is never posted as a message of its own.

The integration only posts. It does not read your Slack and it has no commands. The only replies it makes are those reader summaries, under its own briefs. Messages appear in the channel only; recipients never see them.

On the Integrations page, Slack is under Data distribution: where LinkDrop sends what happens, as opposed to Data ingestion, where your files come from.

The connection belongs to the workspace, not to a person. Every member sees the same channels on the Slack page, but only owners and admins can change them. See Teams and workspaces for roles.

When messages arrive

• Opens, introductions, replaced and deleted documents, and new links post within seconds.
• A visit brief posts a few minutes after the reader stops. See Notifications and visit briefs for when a visit counts as over.
• A new project posts at once, naming who created it (and the agent, when one did it). New documents wait at least a minute and post within a few minutes. Several added together arrive as one message that lists them, so a bulk upload does not fill the channel.

Slack messages do not follow anyone's email settings. A digest or an email turned off does not change what posts to Slack.

Connect a channel

1. Open Integrations in the sidebar and, under Data distribution, choose Slack.
2. Click Add to Slack. Slack opens its own screen, lists what LinkDrop may do, and asks you to pick the channel.
3. You land back on the Slack page with the channel listed. Click Send a test message to see one arrive.

Only workspace owners and admins see Add to Slack. Other members see the page but cannot connect or change anything.

What LinkDrop asks Slack for, in plain words:

• Post messages as the LinkDrop app.
• Post in public channels without joining them first.
• Let you pick a channel on Slack's install screen.

Nothing that reads messages, channels or people. Slack gives LinkDrop a bot token for posting, which is stored encrypted and never shown back.

Private channels work too, but Slack only lets an app post in a private channel it has been invited to. Invite the app in that channel first (for example /invite @LinkDrop). If it is not there, the channel's card shows Disconnected and says to invite it.

The first channel you connect is the default, marked Default · catch-all: anything not routed to another channel posts there. To make another channel the default, click Make default on its card.

More than one channel

More than one channel is a Pro feature, and so is routing a project to one. Free connects a single channel, and that channel posts everything: every kind of message, on every plan. On Free, Add channel carries a Pro badge and opens the upgrade screen. See Credits and plans.

On Pro, click Add channel to connect another one. Each channel has its own switches and its own projects.

• Routing: on a channel's card, choose Route a project… and pick the project that should post there. A project posts to one channel; picking it on another card moves it. Click × on a project to stop routing it.
• A document that belongs to two routed projects posts to both channels. A document in no routed project posts to the default channel.
• A channel with no projects routed to it receives nothing until you route one or make it the default.
• A document in a private project posts only to the channel that project is routed to, its visit briefs and reader summaries included. It never falls back to the default channel, so a private project that is not routed posts nothing. The picker marks private projects with (private).
• With a single channel, everything posts there.

If a workspace moves from Pro to Free, channels and routes already set up keep posting. You can remove a route, but not add a new one or a new channel.

See Projects for how documents belong to projects.

Choose what posts

Each channel has five switches, all on to begin with:

• Opens: first opens and introductions.
• Visit briefs: the write-up after a recipient finishes reading.
• Replaced and deleted documents, and links: new versions, deleted documents and new share links.
• Received files: nothing posts under this switch today, so it makes no difference whether it is on or off.
• New documents: new projects, uploads that finished, and documents added to a project. A new project posts to the default channel (it cannot be routed anywhere yet), and a new private project posts nothing.

Turn off what you do not want in that channel. Turning a switch off on a routed channel keeps that project's messages of that kind quiet; they do not move to the default channel instead.

What a message says

A message is one line, a short context line, and a link: to the document, the reader's page, the version history, or the new link's list. A deleted document has no page left to open, so that message links to the project it was in, or to your activity feed. Names are plain text, never Slack mentions.

The reader is named the same way on every plan, as in the emails:

• On every plan, opens and briefs name the reader when they are known, link to their reader page, and link to their contact page when they are one of your contacts.
• On every plan, a visit brief posts with its write-up. When no write-up was made (automatic briefs are off, the briefs for the day ran out, or credits ran out), it posts a short recap instead: pages read and time spent, without the write-up.

See Analytics for what each plan records.

Busy channels

A deck sent to a large list can open many times a minute. A channel receives at most 30 messages a minute. Past that, LinkDrop posts one "…and N more in the last minute" line, and the held messages follow a few minutes later. They are held, not dropped.

Disconnect

Click Disconnect on a channel's card and confirm. LinkDrop stops posting to that channel at once and removes the card. If it was the default, the oldest remaining channel becomes the default.

Disconnecting deletes the stored token for that channel. Once no connected channel in that Slack workspace is left, LinkDrop also revokes the token, which removes the app from Slack.

You can also remove the LinkDrop app in Slack's own settings, or from the configuration page link at the bottom of the channel's card. Slack tells LinkDrop when the app is removed or its token is revoked, and LinkDrop then deletes every channel connected in that Slack workspace, with the stored token, straight away. The cards leave the Slack page, and your activity feed shows Slack disconnected for each channel, saying the app was removed from Slack or its token was revoked there. Messages already posted stay in Slack.

If the channel is deleted or archived in Slack, the card shows Disconnected with the reason. So does a channel whose token Slack refuses before LinkDrop has heard that the app was removed. A channel connected with the earlier version of the Slack app is marked Disconnected the next time it has something to post, and asks you to reconnect it. A channel that fails five posts in a row is marked Disconnected too. To reconnect, click Reconnect on its card and pick the same channel on Slack's screen: the card comes back with its switches and projects as they were. Reconnecting a channel you already had is allowed on every plan. On Free, to switch to a different channel, disconnect the old card first.

Agents

An agent connected over MCP can read which channels are connected, which one is the default, which switches are on and which projects are routed where. It cannot connect, change, test or disconnect a channel; a person does that from the Integrations page. See Connect your agent.