Where work already happens: ToDidIt for Slack

Most of the useful decisions on a team do not start in a task app. They start in a thread. Someone asks a question, someone else says "I'll handle it," and then the action evaporates unless someone copies it into a tracker. ToDidIt for Slack exists to catch that moment without making Slack the new project manager.

This is our first live third-party integration. It ships on Squad and Business. It is also the template for everything that follows: meet people where they already work, run every action as the linked person, and refuse to post private work into a room that cannot already see it.

Capture in the thread, finish in ToDidIt

The message shortcut Create ToDidIt task turns a Slack message into a task in a project you can edit. Blueprint from thread goes further: Didi drafts a project from the conversation, you review it, then you create it. Neither path invents a second source of truth. The task lives in ToDidIt. Slack is the capture surface.

Slash commands cover the daily loop. /todidit mine lists your open assigned work. /todidit today narrows to due today. /todidit share searches tasks you can see and lets you add a card into the channel or thread. App Home shows assigned, due today, and recently updated work without leaving Slack. From the cards you can complete, assign, and comment the same way the web app enforces editor and inbox rules.

Privacy is the product, not a footnote

The boring way to ship a Slack app is to grant a bot broad access and spray updates into every channel that asked for them. That is how private projects become public gossip. We took the opposite stance.

Channel posts, "Add to conversation," and rich link unfurls only proceed when every human member of that Slack channel is linked to ToDidIt and can already see the project or inbox task. If anyone cannot, we skip the post. Opting into project channel posts under Project settings does not override that check. It is annoying in the short term and correct forever.

Linking is automatic when Slack email matches a workspace member, usually on first slash command or App Home open. Actions always run as that person. There is no god-mode bot writing on behalf of the company.

Why Slack first

We started with Slack because that is where the unfinished sentence lives. Calendar sync and native install paths matter too (see Apps), but chat is where work gets promised out loud. An integration that cannot catch that promise is ornamental.

Slack also forced the privacy rule into the open. If we could not ship channel posts without a strict gate, we did not want the feature. That decision now sits under everything else on Integrations.

What comes next

Zapier is next for Squad: triggers and actions around tasks and projects so you can wire ToDidIt into the rest of your stack without us building every connector by hand. After that, a read-only API and webhooks for Business: reporting, completion events, project finish, the kinds of signals ops and finance already ask for.

We are not racing to a wall of logos. Each integration has to earn the same bar Slack did: useful in a real workflow, respectful of who can see what, and boring to operate once it is connected. Marketplace distribution for Slack itself is staged behind real usage, not a vanity listing. When the Directory URL goes live, Add to Slack will prefer it. Until then, an owner or admin connects from Settings.

If you want the hands-on walkthrough, the Slack guide has tutorials, the command reference, and the connect steps. Field Notes is for the why. The guide is for Tuesday afternoon.