Integration
Fluidwave + Slack: add tasks with a slash command and share a board
Add tasks from any Slack conversation with a slash command, and mirror a Fluidwave list to a native Slack List board so your team sees the work without opening another app.
What syncs
| Data | Direction | Notes |
|---|---|---|
| Tasks created with /fluidwave (Slack to Fluidwave) | One-way | The text after the command becomes a task in your Fluidwave workspace, ready for prioritization and scheduling. |
| A Fluidwave list to a Slack List board (Fluidwave to Slack) | One-way | The synced list appears as a native Slack List in Board layout. Changes flow from Fluidwave to Slack. |
| Task cards in a channel (Fluidwave to Slack) | One-way | Tasks from the synced list post as cards in the channel you choose. Card modes: off, compact, basic or full. |
| Profile link (Slack to Fluidwave) | One-way | Your Slack identity is matched to your Fluidwave account once, so commands and cards are attributed to the right person. |
How to set it up
- 1
In Fluidwave, open Settings, choose Slack and install the Fluidwave Slack app into your workspace. A workspace admin may need to approve it.
- 2
Link your Slack profile to your Fluidwave account so commands you run create tasks for you.
- 3
Type /fluidwave followed by a task in any channel or DM to confirm the link works.
- 4
To share a board, run /fluidwave board or open the Slack settings in Fluidwave, pick the Fluidwave list to sync and the channel to post in.
- 5
Choose a card mode for that channel: off, compact, basic or full.
- 6
Note that Slack Lists require a paid Slack plan; on a free workspace the slash command still works but board sync is unavailable.
Privacy and permissions
The Fluidwave Slack app is installed into a workspace by an admin, and each person then links their own Slack profile to their own Fluidwave account. That link is what lets a slash command from you create a task that belongs to you, and it is the only way Fluidwave knows who is who in Slack.
Fluidwave does not read your Slack messages. The app has no permission to read channel history or direct messages; it receives only the text you type after the slash command and the interactions you make on the cards it posts. What it writes is limited to the Slack List it creates for a synced board, the task cards it posts in the channel you choose, and direct messages to you about your own link and settings.
Slack data is never used to train AI models, never sold, and never used for advertising. Disconnecting the workspace or unlinking your profile stops the sync, and deleting your Fluidwave account removes synced data and encrypted tokens.
| Permission | Why it is needed |
|---|---|
| Add slash commands | Register the /fluidwave command so you can add tasks and open board settings from any conversation. |
| Create and update Slack Lists | Create a native Slack List for each synced Fluidwave list and keep its items up to date. |
| Post messages in channels | Post task cards in the channel you pick for a synced board, including public channels the app has not been added to. |
| View channel names | See the names of public and private channels so you can choose where a board posts. |
| View members and their email addresses | Match your Slack profile to your Fluidwave account when you link them, and identify who ran a command. |
| Send direct messages | Send you a direct message with setup confirmations and link status. |
Features that matter for this
Slack integration
Sync a task list to a Slack board and add tasks with slash commands.
Auto-prioritization
The app orders your list for you using tunable criteria such as due dates, quick wins, importance and dependencies.
Kanban board
Drag tasks between status columns.
What you can do once Slack is connected
The Slack integration solves two specific problems: tasks that get promised in a thread and then forgotten, and teammates who want to see the plan without adopting a new tool.
Capture from anywhere in Slack. Type /fluidwave Send the revised quote to Priya by Thursday in any channel or DM and the task is created in your Fluidwave workspace. Once it is there, the same natural-language parsing, auto-prioritization and AI scheduling apply as to any other task, so a promise made in Slack shows up in tomorrow’s time blocks rather than in a scroll-back you will never revisit. The command also has board and settings subcommands for managing the sync from inside Slack.
Share a board without sharing the app. Pick one Fluidwave list, choose a channel, and Fluidwave creates a native Slack List for it in Board layout. Your teammates open the list inside Slack and see the columns and cards; they never need a Fluidwave login. Optionally, tasks from that list also post as cards in the channel, in a compact, basic or full layout, so a busy channel gets a heads-up when work lands.
This pairs well with the rest of the app. An email triaged into a task in the Gmail client can live on a list that is mirrored to your team’s channel, and a task you complete from your calendar updates the shared board. Remote teams tend to use exactly this shape: capture anywhere, plan in Fluidwave, show progress in Slack.
Automations that use tasks captured from Slack
Slack itself is not an automation trigger in Fluidwave, but tasks created from Slack are ordinary tasks, so every task automation applies to them the moment they arrive. The When a task changes trigger, set to new tasks, is the hook.
Rules that make Slack capture cleaner:
- Route by keyword. Task name contains “bug” → Set List “Engineering,” Add Categories “Bug,” Set Urgency Time-sensitive. Now
/fluidwave bug: checkout button unresponsive on iOSlands sorted. - Default a length. Duration estimate is empty → Set Duration Estimate 30 minutes, so AI scheduling can place Slack-captured tasks without a manual step.
- Keep the shared board honest. List is the one synced to Slack and status is Draft → Update Status Pending, so teammates on the Slack List never see half-written drafts.
- Escalate what is stuck. Status is Waiting and due date is before today → Set Important, which pushes it up the prioritized list you check each morning.
Each rule shows a live preview of matching tasks before you save, and Fluidwave flags contradictory actions and overlaps with other automations. The result is that Slack becomes a capture surface with the same quality of intake as typing into Fluidwave directly, which is the point: the fewer decisions you make at capture time, the less decision fatigue you carry into the day.
Limits and what is not supported
A few honest boundaries so you know what to expect.
- Slack Lists need a paid Slack plan. Slack Lists is a paid feature on Slack’s side, so board sync is unavailable on free workspaces. The slash command works on any plan.
- Board sync is one direction. Changes made in Fluidwave flow to the Slack List and channel cards. Edits your teammates make inside the Slack List are not written back to Fluidwave, so treat the board as a window rather than a second editor.
- One list per board. You pick a single Fluidwave list to mirror to a given channel. Mirror several lists by setting up several boards.
- No message reading. Fluidwave does not read channel history or DMs and cannot turn an arbitrary message into a task; the slash command is the capture path.
- Not a chat-ops suite. There are no reminders posted to Slack, no daily digests and no Slack-side notifications for task changes beyond the cards you enable.
- Platforms. The macOS desktop app is available; Windows and Linux desktop apps are coming soon. Web, iPhone and Android cover the rest.
If your team lives in Slack and wants the whole task manager inside it, a Slack-native tool will feel more complete. If you want one person’s tasks, email and calendar in one place with a light, honest bridge to the team channel, this is that bridge.
Frequently asked questions
Ready to know exactly what to do next?
Tasks, email, calendar and contacts in one place, with AI that works out what to do next. Free forever, no credit card.