Slack is full of tasks nobody writes down.
this+that reads your Slack channels and DMs, extracts every request, follow-up, and commitment into DoBox, and runs workflows on what it finds. A message in #support can create a task, email the customer, and notify the on-call engineer. A DM about a deadline can update a project tracker. Your team stops losing work to threads.
OAuth access — reads messages, sends messages
this+that connects to Slack via OAuth. We request read access to the channels and DMs you choose to monitor, plus the ability to send messages and DMs on your behalf as workflow actions. You control which channels are in scope. Authorization is standard Slack app flow and can be revoked from your Slack workspace settings at any time.
Workflows triggered by Slack
Triggers can match by channel, keyword, sender, or message pattern. Actions can span Slack, email, and any connected tool.
"When a message in #support contains the word 'urgent', create a DoBox task and DM the on-call engineer"
Priority routing from Slack to the right person, without anyone monitoring the channel manually.
"When someone posts a GitHub PR link in #engineering, add a reviewer task to DoBox for the tech lead"
Slack becomes a trigger source for engineering review workflows. No separate process to maintain.
"Bridge: when a customer emails about a bug, post the summary to #bugs and create a thread"
Email-to-Slack routing. The support team gets context in Slack; the customer gets their email thread.
"When a sales rep posts a deal closed in #wins, update the HubSpot deal stage and email the account manager"
One Slack message triggers CRM updates and email notifications simultaneously.
"Every Friday at 4pm, post a summary of open DoBox tasks to #team-standup"
Scheduled digests to any Slack channel. No separate standup bot required.
"When someone DMs me asking for a status update, draft a reply using the latest project data from Notion"
DM triggers with MCP-sourced context. Replies drafted, not just flagged.
Tasks extracted from Slack threads — same as email
Slack threads scanned for commitments
DoBox reads monitored Slack channels and extracts requests, follow-ups, and commitments — not just email. Everything lands in the same task view.
Source context preserved
Every task extracted from Slack links back to the original thread. When you follow up, the conversation history is one click away.
Cross-channel task view
Tasks from Gmail, Outlook, and Slack all appear together in DoBox. One view for everything that needs action, regardless of where it came from.
Team-level visibility
Tasks extracted from shared channels surface to everyone on the team. No more asking "did anyone action that Slack message?" — DoBox answers the question.
Slack + email = one stream of incoming work
Combine Slack with Gmail or Outlook and this+that bridges both channels in a single workflow. A customer email can post to a Slack channel; a Slack message can trigger an email reply. Add GitHub via MCP and engineering workflows span code, chat, and communication. Add HubSpot to close the loop between sales conversations in Slack and CRM records.
See what's waiting across your messages.
Connect your inbox — and optionally Slack — to get a free analysis of the tasks and follow-ups this+that would surface.
Free to use · No credit card required