Planned
Gmail
Requests, replies, and decisions that live in a thread instead of a tracker.
Integrations
Connect the channels work already moves through.
Ordo is built to read where requests actually arrive, not to add a new one. Channels below are connectors we are built for — we only mark a tool live when support is real.
Where Ordo reads from
The same five channels described everywhere else on this site — named here where we already know which product.
Planned
Chat
Slack
A follow-up mentioned once in a channel, before it scrolls out of view.
Planned
Docs
Notion
An open decision or an owner named in a page, not yet assigned anywhere.
Planned
Docs
Google Docs
The same gap, wherever the doc actually lives.
Planned
Meetings
Meetings
The action item that dies the moment the call ends.
Planned
Forms
Forms
A submission that needs routing to the right person, not just a notification.
Dev & project tools
Ordo also connects to the tools where project work and code activity live — beyond the core communication channels above.
Planned
Code
GitHub
A PR comment or issue that needs a decision before it can merge.
Planned
Project
Linear
An issue that's blocked on an answer only a thread has.
We only mark a connector live when support is real
Connector availability varies by plan and rollout. A tool listed as planned is not claimed as supported until that support actually exists. When a connector goes live, it shows up here as live — not before.
Want a specific integration prioritized?
Tell us what you use and where the work gets lost. It helps decide what connects first.
Tell us what you use