Slack Integration

Connect Fishladder to your Slack workspace to keep people and channels up to date on the work that matters to them. Slack gets two kinds of messages:

• Personal DMs about your own tasks — assigned to you, comments, @mentions, completions — based on each person's notification preferences.
• Channel alerts — posts to a channel when something important happens to the tasks of a client, a board or a roadmap project, e.g. “Homepage redesign created for Acme on Deliverables · due Oct 14 · Will” with a link to the task.

Connecting Slack

1. Go to Settings → Integrations → Slack.
2. Click Add to Slack and authorize Fishladder. You need permission to install apps in your Slack workspace.
3. Once connected, you'll see a green check with your workspace name.

Only team admins can connect or disconnect Slack. If your workspace was connected before channel alerts existed, a Reconnect Slack prompt appears in the Channel alerts section: reconnect once to let Fishladder list private channels.

Personal DMs

To get Slack DMs about your own tasks, link your Slack identity:

1. Go to Settings → Profile.
2. In the Slack section, click Link Slack Account and sign in with Slack.

Then choose which events reach you in Slack in your notification preferences. The Notification channel on the Slack settings page is where @mentions from task comments are also posted.

Channel alerts

A channel alert is a rule: post these kinds of updates, for these clients, boards or roadmap projects, to this channel. Admins manage them under Settings → Integrations → Slack → Channel alerts.

Who decides what: anyone who can edit a task or board can link it to a client (a HubSpot or CRM company). That says whose work it is. Only admins decide what reaches Slack — which channel hears about which clients, and at which moments. Linking a company never posts anything by itself. For example:

• #acme-updates ← created, reassigned, due date changed, 2 days before due · for Acme (a HubSpot company)
• #design-team ← status changes · for the Design board
• #leadership ← when a task is due · for the Q4 launch roadmap project

Creating an alert

1. Click New alert.
2. Post to — pick a channel. Fishladder can post to any public channel. For a private channel (shown with a lock), first invite the app in Slack with /invite @Fishladder.
3. Post when — choose any of:
   • When a task is created
   • When a task's status changes — moved to another column, completed (marked done or moved into a closed status) or reopened.
   • When a task is reassigned — its assignee changes or is removed.
   • When a task's due date changes — a due date is set, moved or removed.
   • Before a task is due — a morning post (around 8am Pacific) listing tasks due in the number of days you choose (1–30; 1 means “due tomorrow”).
   • When a task is due — a morning post listing tasks due that day.
   Other edits — the description, title, priority, section or order — never post. If one edit changes several things (say, the assignee and the due date), each channel's post includes only the changes that channel asked for. The two due-date posts go out together as one morning message, and a day with nothing due posts nothing.
4. Alert assigned team member (optional) — @mention the task's assignee in the post, so Slack notifies them directly. Fishladder finds the person by the Slack account they linked in their profile, or else by their email address in your Slack workspace. If they aren't in Slack, the post shows their name instead. In the daily digest, each task mentions its assignee.
5. For — search and add clients (HubSpot companies, or CRM companies if you use the built-in CRM), boards and roadmap projects. A rule posts when a task matches any of them.
6. Click Create alert, then the send icon to post a test message to the channel.

Which tasks count for a client

A task belongs to a client when any of these is linked to that company:

• the task itself (the HubSpot section in the task pane),
• the task's board — link a HubSpot company in Board settings and every task on that board is that client's, from the moment it's created,
• a roadmap project the task is linked to,
• or, with the built-in CRM, the company whose own board the task is on.

Linking a board is the easiest way to make “task created for Acme” work: a brand-new task usually isn't linked to anything yet, but it's already on the client's board.

What gets posted, and when

• Alerts come from every way a task is created or changed: the web app, bulk edits, the CLI and API, the Claude connector, intake from documents, CSV import, approved AI suggestions and recurring tasks. One-off migrations (Asana, Monday, ClickUp, Notion) and template tasks on a new board don't post.
• Posts wait about a minute, so a burst becomes one message — importing 12 tasks for Acme posts “12 tasks created for Acme on Deliverables” with a list, not 12 messages. Each task appears once: several changes to it within the minute are combined (“due Oct 14 → Oct 20 · assigned to Will”), and a completion outranks a creation, which outranks other changes.
• A new task gets one post. Edits made in the first 10 minutes after creating it — setting the assignee, due date or status while you fill it in — aren't posted separately: if the “created” post hasn't gone out yet it shows the task as it ended up, and if it already has, those early edits are skipped. Changes after the first 10 minutes post as usual.
• If two alerts send the same update to the same channel, it's posted once.
• Subtasks and recurring-task templates don't post; each recurring instance does.

Restricted boards

Everyone in a Slack channel sees what's posted there, including people who can't open a restricted board (a board in a project group). So tasks on restricted boards are posted only by alerts that list that board itself — a client or roadmap alert skips them. This is also why only admins can create alerts.

Checking an alert

Each alert shows when it last posted, or what went wrong in plain words — for example the channel was deleted or archived, the app isn't in a private channel, or the Slack connection needs reconnecting. Fix it and send a test to confirm. Use the switch to pause an alert without deleting it.

Disconnecting

To remove the Slack connection, go to Settings → Integrations → Slack and click Disconnect. This stops all Slack DMs and channel alerts for the team; your alert rules are kept and resume if you reconnect. Individual people can unlink their Slack identity from the Profile page.