Two-way connections to the tools you already run on
org.run reads what is happening in your systems and writes the work back. Replies get sent, records get updated, tickets get closed. All inside the tools your team already uses.
Reads in, writes back
Read a new ticket from Zendesk
Sent the reply from Gmail
Updated the deal in HubSpot
Directory
Where org.run works today
Grouped by the part of the company they run. Some tools show up twice because they do two jobs.
Communication
6- Gmail
Zoom
Aircall
Intercom
Google Calendar
Sales and CRM
3Gong
Support
2
Finance
4- QuickBooks
SAP
Google Sheets
Engineering
8Jira
Sentry
Datadog
PagerDuty
Statuspage
Firebase
Docs and product
5Figma
Amplitude
Google Docs
Google Slides
Mobile
2App Store
Play Store
Don't see a tool you rely on? We add connectors on request, including your own internal systems. Ask for a connector
How connections work
Access is earned, one action at a time
You stay in charge of what org.run can see and what it can change.
- 01
Connect with OAuth
Sign in to each tool the normal way. org.run uses your existing permissions and never sees more than the account you connect.
- 02
Start read-only
Every new connection begins by reading. org.run learns how the work flows before it touches anything.
- 03
Earn write access per action
You approve each kind of write on its own. Drafting a reply is one grant. Sending it is another.
- 04
Logged and reversible
Every write is recorded with what changed and why. If something is wrong, you roll it back.
What it listens to
Every way work reaches org.run
Today it works from your systems, your conversations, your alerts and your direct asks. More sources are on the way.
Connected systems
Your CRM, books, codebase, support desk and core database. org.run reads the state of the business and writes updates back.
Conversations
Email, chat, calls and meeting notes. It picks up decisions and requests, then turns them into finished work.
Direct requests
Ask it for something in Slack or email, the way you would ask a colleague. It does the work and reports back.
Internal monitors
Alerts, metric thresholds and overdue states from tools like Sentry, Datadog and PagerDuty become work the moment they fire.
Work observation
Learning a process by watching how your team already does it, so you don't have to write it down.
Outside-world monitors
Keeping an eye on sources outside your company, like App Store reviews and regulator sites, and acting when something changes.
Integration questions
Both. It reads to understand what is happening and writes to get work done. Write access is granted per action, and every write is logged and reversible.
The same ones as the account you connect, and no more. You can narrow them further inside org.run, down to a single kind of action.
Usually, yes. We add connectors on request, including internal tools and your own database. Tell us what you use.
org.run stops reading and writing straight away and its access tokens are revoked. You decide what happens to any data it held.
Early access
Connect your stack to org.run
Start read-only. Grant write access when you are ready.
Scoped, auditable and reversible from day one. Your data stays yours.