Every tool your work runs on. Connected.
this+that reads your messages across Gmail, Outlook, Slack, Microsoft Teams, and Google Chat. It acts on the rest of your stack: HubSpot, Notion, GitHub, and any other tool with an MCP server, so the work that starts in a message can finish wherever it needs to.
The channels this+that reads
Connect one or all of them. They work together as a single stream of incoming work.
DoBox extracts tasks from threads. Workflows archive, label, draft, send, and manage your calendar.
Learn moreWorks alongside Teams for complete M365 coverage. Same DoBox and workflow capabilities as Gmail.
Learn moreDoBox extracts tasks from Slack threads. Workflows trigger on messages, bridge to email, and act across your stack.
Learn moreCombine with Outlook for a complete Microsoft 365 workflow. DoBox, task extraction, and cross-channel automation.
Learn moreWorkspace-first teams get DoBox extraction and workflows across Google Chat spaces, DMs, and Gmail in one stream.
Learn moreNot a channel, but read the same way
These are not places your team sends messages, so the channel list leaves them out. They still arrive in this+that, and workflows can act on them.
Message this+that from somewhere else
A way to talk to your assistant when you are away from the app. We do not read these accounts or pull their conversations into your inbox.
Tools your workflows can act on
Workflows can reach into these tools directly, no extra configuration. Use them as action steps alongside your email and messaging triggers.
- Update deal stage from a customer reply
- Create contacts from inbound lead emails
- Update an opportunity when the client emails a decision
- Log the call notes against the right account
- Look up the account record before you reply
- Update a deal when the customer emails a decision
- Find out where a new lead works before you reply
- Pull the company profile into a workflow when a demo request arrives
- Match the sender of an inbound email to a person and a company
- Look up an account in a workflow before the lead is routed
- Research a prospect before you reply
- Pull live web data into a workflow
- Find a slot and book the meeting when a prospect asks for time
- Accept or decline an invite from the thread it arrived in
- Move a meeting when a client writes to reschedule
- Add a colleague to the invite when they join the deal
- Create issues from bug report emails
- PR review digest for engineering leads
- Create pages from meeting follow-ups
- Update project trackers from milestone emails
- Create Jira tickets from support emails
- Log meeting notes to Confluence
- Notify designers when feedback arrives
- Track design review requests from email
- Save email attachments to the right folder
- Share links when documents are requested
- Route contracts to Box on receipt
- Notify teams when files are shared via email
- Create items from client request emails
- Update status when milestones are mentioned in Slack
- Create tasks from email action items
- Update project status from standup messages
- Create tasks from support tickets in email
- Sync DoBox tasks to ClickUp spaces
- Open a story from a bug report sent to support@
- Move a story when the customer confirms the fix
- Create a card from a request that arrives by email
- Move a card when the client approves
- Surface ad spend trends in a Slack briefing
- Pause campaigns when an exec emails to flag overspend
- Draft a campaign and wait for approval before anything spends
- Pull last week's performance into the report you actually read
- Turn a bug report email into a Linear issue with the thread attached
- Post a weekly triage summary to the team
- Write meeting outcomes into Collections so the next reply starts from them
- Create follow-up tasks from what was agreed in the call
- Pull the right asset into a customer reply
- Kick off a design request from an inbound brief
- Push an extracted task into a planned block of time
- Reschedule around what actually arrived today
- Ground a reply in a document nobody could find
- Answer an internal question from what the company already wrote
- Answer a customer data question without leaving the thread
- Attach the number to the weekly report
- Find where a reported bug actually lives
- Give an engineer the context with the ticket
Not seeing your tool? Connect anything.
The Model Context Protocol is an open standard. If your tool has an MCP server (whether it's a commercial product, an internal API, or a community-built connector) you can add it to this+that. The built-in integrations above are the starting point, not the ceiling.
See what this+that can do with your stack
Connect your inbox and this+that starts reading it, turning the tasks and follow-ups buried in your messages into tracked work you can act on.
The Team plan is free for 30 days · No credit card required · Then $35 per user per month · $29 billed annually