Outreach is a sales-engagement platform that manages sequences, prospects, and the emails and calls that go out through them. Connecting it as a data source through the Connectors library syncs that activity into your Alta workspace, where it becomes training data for Alta and a foundation for your metrics, dashboards, and Luna analysis. Once it's flowing, you can measure sequence performance, reply rates, and rep activity — and ask Luna questions in plain English. Outreach connects with credentials.

Who this is for: Sales and RevOps teams who run sequences in Outreach and want that activity measured across Alta.

Before you start

Have your Outreach credentials ready, with access to the prospect and sequence data you want to sync.
Connect a source only once per workspace. If Outreach already shows Connected, edit the existing connection.

Connect Outreach

Open Connectors from the sidebar.
Find Outreach via the category tabs or the Search data sources box.
Click the Outreach card to open the Create connector screen.
Fill in the connection fields shown, then click Create.
Alta runs a connect test. If it fails you'll see The connect test has failed with Outreach's error — fix the field and retry.
The card then shows Connected and Data is syncing until the first sync finishes.

Choose which tables sync

Open the connection. Outreach brings in tables like prospects, sequences, mailings, and accounts.
Use the Synced toggle in the Outreach tables section to control what's pulled in.
Turn off Show only synced tables to see everything available.

Key tables and fields synced

prospects — people being worked: id, emails, title, stage, accountId, ownerId
sequences — cadences: id, name, enabled, scheduleCount, step counts
mailings — individual sends: id, state, openCount, clickCount, replyCount, bouncedAt
sequenceStates — a prospect's progress in a sequence: state, sequenceId, prospectId
accounts — companies: id, name, domain
users — reps: id, email, name

What you can ask this data

Once it's syncing, build it into metrics and dashboards or just ask Luna / Ask AI. For example:

"What's our email open and reply rate by sequence?" — aggregates mailings.openCount/replyCount grouped by sequences.name.
"How many prospects are active in each sequence?" — counts sequenceStates by sequenceId and active state.
"Which sequences drive the most replies?" — ranks sequences by total replyCount.
"How many touches happen before a reply on average?" — counts mailings per prospect up to first reply.
"Which reps send the most and get the best reply rate?" — joins mailings to users.

Example use cases

Sequence scorecard. Open, click, reply, and bounce rates per sequence to find your best messaging.
Capacity & activity. Sends per rep per week and active prospects per sequence.
Deliverability watch. Track bounces and reply rates over time to catch deliverability issues early.
Engagement-to-pipeline. Combine with CRM data to see which sequences create real pipeline.

Keep it in sync

Sync status shows Last sync (Succeeded/Failed) and the Sync frequency.
Click Sync now to refresh immediately; it's disabled while a sync runs.
Use the overflow menu (⋯) to Disable, Enable, or Delete.

Tips and common pitfalls

Mailings is the metrics table. Open/click/reply counts live on mailings — sync it to measure performance.
Sync only what you need to keep syncs fast and your data clean.
A failed connect test is almost always credentials or scopes. Read the inline error and correct the field.
Deleting is permanent. Disable instead to pause.