Outreach AI Agents: API, Use Cases and Major Integration
Understand Outreach's native AI agents and API, then build governed lead handoffs, enrollment reviews, and cross-system workflows on Major.

Outreach AI agents research accounts, personalize engagement, prepare meetings, and maintain deal context inside Outreach. This guide covers Outreach's native AI, its API, and how Major adds governed cross-system work with durable apps, scoped agents, and approval workflows.
For RevOps owners, the practical question is which work belongs in Outreach and which needs a shared control surface across enrichment, CRM, and sales engagement.
What Outreach does for revenue teams
Outreach brings sales engagement, conversation intelligence, deal management, and forecasting into a revenue platform. Sales development representatives work prospects through sequences, account executives prepare for meetings and progress opportunities, and sales managers inspect activity and coach execution. RevOps maintains the ownership, data quality, and process controls behind those motions, as described on Outreach's platform site.
Its API reflects that operating model. Prospects represent people, accounts represent companies, sequences organize engagement, and sequence states connect a particular prospect to a sequence. Tasks track work requiring action. Those distinctions matter: creating a prospect is different from enrolling that person into an active sales motion, as the common API patterns explain.
Major fits when that motion needs software spanning several systems. A Major app holds the enrichment evidence, eligibility checks, review queue, and execution receipts. An agent judges fit or drafts a recommendation. A workflow coordinates retrieval, approval, and authorized writes. The repeatable checks run in deterministic software rather than being reasoned through again for every contact.
Outreach AI agents and built-in capabilities
Outreach already offers substantive native AI. Its AI agents page describes Revenue Agent for prospecting and identifying high-intent accounts, Research Agent for combining engagement and external research, and Personalization Agent for turning buyer context into messaging.
Meeting Prep Agent creates briefs before conversations. Deal Agent recommends opportunity-field updates from conversation intelligence, with automatic application or seller review depending on configuration. Outreach Omni Agent supports conversational exploration and action across accounts, conversations, and pipeline. Kaia provides live guidance during meetings. The page labels Reply Agent as coming soon, so it should not be treated as generally available.
These capabilities deserve credit for working close to sellers' existing context. Outreach also describes its own agent orchestration features, so cross-system work is not inherently absent from the product.
Major adds a different control surface: agents can build the deterministic apps they run on, with managed tables, review screens, and reusable execution logic. Use that layer when a decision depends on enrichment provenance, CRM ownership disputes, company-specific suppression policies, or approvals shared across teams. Keep native Outreach intelligence where it already solves the sales task, and add Major around the unresolved operating process.
How Outreach connects to Major
Major has a native Outreach connector, identified as outreach in the connector catalog. It is not a custom API connector. IT configures the connector once, stores credentials centrally in the connector vault, and grants the apps, agents, and workflows only the access their jobs require.
The underlying Outreach REST API uses JSON:API conventions. Its documented API base is https://api.outreach.io/api/v2, while OAuth access authorizes calls on behalf of a user. Confirm which operations the configured connector exposes before designing writes; the existence of a vendor endpoint does not prove every connector action is available.
Build a read-only connection first. Validate the authorized organization's records, ownership boundaries, and returned permissions before enabling prospect creation or enrollment. Keep tokens and webhook secrets out of app code, prompts, and review notes.
Major orchestrates Outreach; it never replaces it. Outreach remains responsible for its sequences and engagement execution. Major's app holds cross-system state, its agent makes bounded judgment calls, and its workflow handles schedules, routing, retries, and human approval. SSO, RBAC, and audit logs cover the Major side of that operating model.
Outreach API guide for apps, agents, and workflows
Authentication and scopes
OAuth documentation describes an authorization-code flow with short-lived bearer access tokens and refresh tokens. Development and production application credentials are distinct. The getting-started guide documents two-hour access tokens, 14-day refresh tokens, and rotation to the newest refresh token.
Start with prospects.read, accounts.read, sequences.read, sequenceStates.read, tasks.read, and mailings.read for retrieval. Add prospects.write and sequenceStates.write only for approved creation and enrollment. Outreach's scope rules use plural resource names plus an access level, and write does not imply read. User governance restrictions still apply after scope checks.
Outreach also documents S2S application tokens, issued per installation without a user's identity, for a limited set of operations. This is a vendor authentication option, not a claim that Major's native connector uses S2S. Some writes need extra actor information or are unavailable through that model.
Pagination, limits, events, and testing
Use cursor pagination with page[size], page[after], and page[before], following the response's next link. Outreach recommends count=false for efficient traversal and deprecates offset pagination in its request guide. Requests require the application/vnd.api+json content type.
The published general limit is 10,000 requests per hour per user, with exceptions for particular APIs. Watch X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, also described as aliased by Retry-After. A 429 means the caller must back off.
Webhook events include prospect changes, mailing replies and bounces, sequence-state changes, and completed tasks. With a secret configured, verify Outreach-Webhook-Signature using HMAC-SHA256 over the original request body. Delivery has a five-second timeout. HTTP error responses are not retried, including 429 and 500; network failures receive three retries with one-second pauses.
For testing, development OAuth credentials are available immediately, with documented authorization restrictions. They are not evidence of a separate sandbox tenant. No dedicated API sandbox is documented in these guides. Use controlled test records and prevent real enrollment during read-only validation.
Eight useful API operations
The reference pages below show resource-relative paths. Prefix them with the documented API base to form the full request URL. Each operation serves a different part of a governed sales process.
GET /prospects retrieves people and their engagement-related attributes.
- App: Maintain a prospect lookup and duplicate-review queue.
- Agent: Read relevant context before judging whether new enrichment describes the same person.
- Workflow: Fetch matching records before any create attempt, then retain the returned identifier.
POST /prospects creates a prospect resource, without by itself selecting a sequence.
- App: Record the submitted attributes and created prospect identifier.
- Agent: Propose which evidence-backed enrichment belongs on the record.
- Workflow: Create the approved record after duplicate and suppression checks, then checkpoint success.
GET /accounts retrieves company-level records and relationships.
- App: Display an account match alongside its source evidence.
- Agent: Assess ambiguous company names against the supplied firmographic context.
- Workflow: Retrieve account context before assigning a prospect to a segment or review owner.
GET /sequences retrieves sequences available to the authorized caller.
- App: Present an administrator-approved sequence catalog with a local policy mapping.
- Agent: Recommend the best permitted sequence for the lead's role and segment.
- Workflow: Refresh the catalog and reject recommendations outside the approved identifier list.
GET /sequenceStates retrieves prospect enrollment state, including sequence relationships and state information.
- App: Show existing enrollment beside a proposed new action.
- Agent: Explain whether the current motion conflicts with the requested follow-up.
- Workflow: Recheck enrollment before executing an approved action to reduce duplicate engagement.
POST /sequenceStates creates the resource that represents a prospect in a sequence.
- App: Store the approved prospect, sequence, mailbox, and resulting enrollment receipt.
- Agent: Recommend enrollment with a rationale, without independently authorizing activation.
- Workflow: Submit the approved enrollment only after revalidating eligibility and ownership.
The enrollment pattern explicitly supplies prospect, sequence, and mailbox relationships. Creating the state starts the sequence's automation, so this write requires the same care as an external communication.
GET /tasks retrieves work items requiring seller action.
- App: Maintain a task-review board tied to prospects and owners.
- Agent: Prioritize ambiguous follow-ups using task notes and account context.
- Workflow: Refresh incomplete work and route recommendations to the assigned reviewer.
GET /mailings retrieves platform mailing records.
- App: Show engagement evidence alongside a lead or exception.
- Agent: Summarize the available mailing context without treating an open as buying intent.
- Workflow: Reconcile records after an event and update the local engagement history.
Outreach automation use cases on Major
ZoomInfo enrichment to approved sequence handoff
This is the published use case in the hub's library: preserve enrichment context while moving qualified contacts toward Outreach engagement.
- App: Stage ZoomInfo evidence, identity matches, suppression outcomes, and owner review.
- Agent: Recommend a permitted sequence and explain how the person's role fits the segment.
- Workflow: Use GET /prospects, POST /prospects, and POST /sequenceStates after approval. Notify the SDR through the team's configured channel.
Salesforce ownership conflicts before enrollment
A proposed lead handoff can look valid in enrichment while conflicting with an active account owner's sales motion. This is a proposed pattern, not a reported deployment.
- App: Keep Salesforce ownership evidence beside Outreach account and enrollment records.
- Agent: Explain a conflict and recommend the right person to resolve it.
- Workflow: Read GET /accounts and GET /sequenceStates, compare approved policy, and route exceptions through Slack. Block enrollment until ownership is resolved.
Outreach task review with Salesforce and Slack
A seller's overdue task might need a new priority, a different owner, or no additional outreach because the account context changed.
- App: Store task snapshots, reviewer assignments, and disposition history.
- Agent: Prioritize the queue using task notes, CRM context, and available engagement evidence.
- Workflow: Combine GET /tasks with GET /mailings, then deliver an internal Slack review digest. Leave task completion and external contact to the authorized owner.
These patterns connect judgment to an inspectable record. They do not require replacing Outreach's native prospecting or deal intelligence, and they should begin with a narrow segment rather than a company-wide write permission.
Architecture: build the Outreach control surface on Major

Figure 1. Major separates cross-system retrieval, judgment, approval, and durable execution state.
Start with one durable work item per lead and intended sales motion. Store source identifiers, evidence timestamps, current policy version, proposed sequence, reviewer, and execution status in managed database tables. The app exposes those records as a review queue, rather than relying on a conversation as the only history.
- A schedule or enrichment event starts the workflow.
- Scoped connectors retrieve Outreach and CRM context.
- Deterministic checks validate identity, suppression, ownership, and allowed sequences.
- The agent judges fit and supplies its recommendation with evidence.
- The workflow requests approval for consequential writes.
- The app records the resulting vendor identifiers and execution receipt.
Keep retrieval and validation reusable. When an agent identifies repeatable matching or policy checks, it can build that software into the app and run it on subsequent items. Reserve model reasoning for uncertain identity, segment fit, and explanation. This is Major's predictable-agent approach: reason once for the reusable software, then run that software repeatedly while preserving judgment where needed.
Worked example: reviewing 300 enriched leads
For example, consider an illustrative weekly batch of 300 enriched contacts. Today, a coordinator spends six minutes per contact checking identity, account ownership, and sequence fit. That is 300 multiplied by six minutes, or 1,800 minutes, equal to 30 hours of preparation.
A proposed Major process stages the same 300 contacts. Assume 240 have clear evidence and need one minute of human review each. The other 60 have ambiguous matches or ownership conflicts and need five minutes each. Review time becomes 240 plus 300 minutes, or nine hours. Add two hours for queue maintenance and spot checks: 11 hours total, compared with 30, an illustrative difference of 19 hours.
These are planning assumptions, not customer results or a promise of savings. Measure actual reviewer time, missed matches, rejected recommendations, and write failures before expanding permissions.
The workflow still checks every approved contact immediately before enrollment. If a person opts out while approval is pending, the earlier approval cannot override the new exclusion. Time saved in preparation should create more room for careful review, not justify skipping it.
Governance, approvals, and failure handling

Figure 2. Internal staging runs automatically; enrollment waits for owner approval and fresh checks.
Allow read-only staging and internal summaries to proceed automatically. Require human approval before first-time enrollment, bulk record changes, or actions that can initiate messaging. The agent must never override opt-outs, invent consent, change an account owner to bypass review, or choose an unapproved sending mailbox.
Apply SSO and RBAC to the review app. Separate the person who changes segment policy from the person approving a bulk run. Audit the evidence, agent recommendation, human approval, executed payload, and vendor response without copying credentials into those records.
For webhook reliability, verify the signature, persist the event quickly, and acknowledge within the documented timeout. Build asynchronous processing behind that receipt. Because HTTP errors do not trigger redelivery, use scheduled reconciliation to recover missed updates.
For outbound API calls, follow rate-limit reset headers, add bounded backoff, and stop repeated permission failures. Deduplicate events using a local fingerprint and retain checkpoints. If a create call times out after submission, reconcile vendor state before retrying; do not assume the write failed. Keep unresolved cases visible in an exception queue.
Outreach AI Apps, Agents and Workflow Automations
Every published Major use case that works with Outreach, newest first. Each one names the Outreach API objects involved and shows the app, agent and workflow split.
- Automate ZoomInfo-to-Outreach Lead Handoffs on Major: Move enriched ZoomInfo contacts into the right Outreach sequence without losing context. This brief maps the data flow, judgment points, duplicate checks, approvals, and controls an SDR team needs.
Frequently asked questions
What are Outreach AI agents?
Outreach AI agents are native revenue features for research, prospecting, personalization, meeting preparation, deal updates, and conversational analysis. Major adds governed cross-system apps and workflows around Outreach when a process needs durable state and shared review.
Does Major have a native Outreach connector?
Yes. Major's connector catalog lists the native Outreach connector. IT configures it once, keeps credentials in the connector vault, and scopes access for the apps, agents, and workflows using it.
How do you enroll an Outreach prospect through the API?
Create a sequence state with the prospect, sequence, and mailbox relationships. Outreach's enrollment guide says this starts sequence automation, so validate consent, ownership, and approval first.
What authentication does the Outreach API support?
Outreach documents OAuth authorization-code access with access and refresh tokens, plus a separate S2S model for limited operations. Confirm the model supported by the configured connector rather than assuming interchangeability.
Does Outreach retry failed webhooks?
According to the webhook guide, network failures receive three retries, but HTTP error responses do not trigger retries. Persist events quickly and run reconciliation for gaps.
Can an agent enroll leads without human approval?
The proposed Major design requires approval before enrollment because enrollment can start communication. Read-only staging and recommendations can run automatically, but agents cannot bypass suppression rules or grant themselves new permissions.
Sources
- Outreach platform overview: Revenue-team roles and platform capabilities.
- Outreach AI agents: Named native agents, live guidance, and availability labels.
- REST API overview: JSON:API model and integration purpose.
- OAuth access: Authorization flow and development credentials.
- S2S access: Installation-specific application authentication and limits.
- Getting started: Token lifetimes, scope semantics, governance restrictions, and rate-limit headers.
- Making requests: Content type, cursor pagination, and deprecated offsets.
- Webhooks: Events, signatures, timeouts, and precise retry behavior.
- Common API patterns: Enrollment relationships and the start of sequence automation.
- Outreach API reference: Reference entry point and machine-readable schema locations.
- Official OpenAPI schema: API base URL and published operations.
- Prospect reference index: Prospect operation documentation links.
- Sequence state reference index: Enrollment operation documentation links.
- List prospects: Prospect retrieval attributes and relationships.
- Create prospect: Prospect creation request structure.
- List accounts: Company records and account relationships.
- List sequences: Sequence catalog response structure.
- List sequence states: Enrollment status and relationships.
- Create sequence state: Enrollment request and response structure.
- List tasks: Work item records and relationships.
- List mailings: Engagement record response structure.
- Developer documentation index: Official navigation to machine-readable guides.
- Sales AI overview: Additional context for Outreach's native intelligence capabilities.
Start building on Major
Build an Outreach review app that keeps enrichment evidence, sequence recommendations, human approvals, and execution receipts in one governed process.
About the author
Ritvij Gautam is Head of Growth at Major.
Last reviewed November 20, 2026 by Ritvij Gautam.
Frequently asked questions
- What are Outreach AI agents?
- Outreach AI agents are native revenue features for research, prospecting, personalization, meeting preparation, deal updates, and conversational analysis. Major adds governed cross-system apps and workflows around Outreach when a process needs durable state and shared review.
- Does Major have a native Outreach connector?
- Yes. Major's connector catalog lists the native Outreach connector. IT configures it once, keeps credentials in the connector vault, and scopes access for the apps, agents, and workflows using it.
- How do you enroll an Outreach prospect through the API?
- Create a sequence state with the prospect, sequence, and mailbox relationships. Outreach's [enrollment guide](https://developers.outreach.io/api/common-patterns) says this starts sequence automation, so validate consent, ownership, and approval first.
- What authentication does the Outreach API support?
- Outreach documents [OAuth authorization-code access](https://developers.outreach.io/api/oauth) with access and refresh tokens, plus a separate [S2S model](https://developers.outreach.io/api/s2s-access) for limited operations. Confirm the model supported by the configured connector rather than assuming interchangeability.
- Does Outreach retry failed webhooks?
- According to the [webhook guide](https://developers.outreach.io/api/webhooks), network failures receive three retries, but HTTP error responses do not trigger retries. Persist events quickly and run reconciliation for gaps.
- Can an agent enroll leads without human approval?
- The proposed Major design requires approval before enrollment because enrollment can start communication. Read-only staging and recommendations can run automatically, but agents cannot bypass suppression rules or grant themselves new permissions.