Outreach integration · Beta

What Management OS does with your Outreach data.

How it connects: OAuth 2.0 through an app your admin registers for your Outreach org, read-only scopes. Checked against the product on 5 November 2026.

1. What Management OS reads

  • Prospects and accounts, and the user roster, so activity is attributed to the right seller.
  • Opportunities, their stages and the prospects' roles on them.
  • Sequences and sequence states: who is in which sequence and how far along.
  • Mailings: engagement counts and the subject line, and the mailbox that sent each one, so it is attributed to the right seller. Never the body.
  • Calls with their dispositions, and tasks.

It reads only what the connected Outreach user can see. Mailing bodies are never requested.

2. What it writes

Nothing. Every scope is a read scope and every request is a read. Management OS never writes to Outreach.

3. The access it asks for, and why

Select exactly these scopes when you register the app in Outreach. The connect page lists them too.

prospects.read, accounts.read

The people and accounts your team works.

opportunities.read, opportunityProspectRoles.read, opportunityStages.read, stages.read

Outreach opportunities, their stages and who plays which role, joined to the rest of your pipeline.

sequences.read, sequenceStates.read

Which sequence each prospect is in, and how far along.

mailings.read, mailboxes.read

Mailing engagement and the subject line, and which seller's mailbox sent it. The body is not read.

calls.read, callDispositions.read

Calls and their outcomes, as evidence of progress.

tasks.read, users.read

Follow-ups, and the roster so activity is attributed to the right seller.

4. How fresh the data is

  • A first sync is queued as soon as you connect; the Outreach page shows counts as it runs. It goes back 90 days rather than through all history.
  • After that, Management OS reads Outreach every 2 hours, picking up only what changed, and stays well inside your hourly API budget.
  • Outreach refresh tokens expire after 14 days, so once a day Management OS refreshes any connection whose tokens are more than 7 days old. A quiet connection keeps working.

5. Where it shows up in Management OS

  • Your Desk and morning brief: sequences, replies, calls and Outreach opportunities joined to your pipeline. Each seller sees their own book; leaders see their team.
  • Ask Anything: questions about sequences, replies and calls, answered from the synced records.

6. Where your Outreach data lives

Your credential. The client secret and every user's tokens are sealed with application-layer encryption before they are stored, and are never shown back in your browser. Outreach rotates the refresh token on every refresh, so Management OS stores the new pair before doing anything else, and only one process refreshes a given connection at a time. If Outreach refuses the grant, the page shows Reconnect.

Hosting. Runs in the United States on Vercel and Supabase.

AI processing. The data a brief or an answer needs is sent to Anthropic or OpenAI, on API terms that prohibit training. Each keeps prompts up to 30 days for abuse monitoring, with narrow exceptions listed on Sub-processors. We do not use Customer Data, prompts, or AI Output to train, fine-tune, or improve any AI model, including our own.

If you leave. Revoke access at any time, and export or delete your data on request. Active data is deleted within 30 days of termination; encrypted backups roll off within 90 days. See the Privacy Policy and the Data Processing Addendum.

7. How to connect Outreach

Before you start.

  • Outreach takes a few more steps than most connections, by design: your admin registers Management OS as an application in your own Outreach org, so the connection stays under your control and does not wait on a vendor review.
  • A Management OS workspace owner or admin to register the Outreach app once. Members see who to ask.
  • An Outreach account that can create an app at developers.outreach.io.
  1. Open Management OS, then Settings, then Integrations. Find Outreach and choose Connect. The page shows the Redirect URI and the scopes to select.
  2. At developers.outreach.io, sign in with your Outreach account and create an app. On the API access tab, add the Redirect URI, select the scopes listed, and copy the Client ID and Client Secret.
  3. Back in Management OS, an owner or admin enters the Client ID and Client secret and saves them.
  4. Each seller then chooses Connect, signs in to Outreach and approves read-only access for their own user. The first sync starts.

8. How to disconnect

On the Outreach page in Settings, choose Disconnect. Management OS deletes your stored tokens and stops reading for your user. The disconnect is recorded in your workspace's audit log.

Outreach has no call that lets Management OS revoke the grant, so the grant lapses unused. Remove the app's access in Outreach to end it at once.

An owner or admin can also remove the workspace's app from the same page. Records already synced stay in your workspace until you ask for them to be deleted at privacy@mgmt-os.ai.

9. How to revoke access from Outreach

In Outreach, remove Management OS from the apps your user has authorized, or delete the app your admin registered at developers.outreach.io. Outreach then refuses the tokens and the page in Management OS shows Reconnect.

10. If something goes wrong

The page says Outreach did not complete the connection.
Outreach returned an error during sign-in, shown in brackets. The most common causes are a Redirect URI that does not match the one on the page exactly, or scopes missing from the app. Fix the app and connect again.
Some data is missing after the first sync.
If a scope was not selected on the app, that part of the sync is skipped and the rest continues. Add the scope, then disconnect and connect again.
Members see Not set up yet.
A workspace owner or admin needs to register the Outreach app and save its Client ID and secret first.

11. Contact

Help connecting: support@mgmt-os.ai
Privacy and data requests: privacy@mgmt-os.ai
Security reports: security@mgmt-os.ai

Every other guide is on the Help page, and every connection is listed on Integrations.