> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-connections/outreach.md).

# Outreach

Connect your company's Outreach account to Cakewalk's MCP Gateway. Every agent tool call against Outreach passes through the gateway and is evaluated against your Policies.

## Requirements

* Outreach org admin who can create apps in the Outreach Developer Portal.
* Outreach Amplify add-on enabled for the org. Outreach MCP requires Amplify licensing.

## Required Scopes

\[VERIFY: confirm with Cakewalk eng before publish; Outreach's MCP server does not publish a scope checklist in canonical docs. The set below is a working hypothesis based on Outreach's resource.action scope pattern.]

```
users.read
accounts.read
prospects.read
mailings.read
sequences.read
```

Outreach scopes follow `resource.action` format. Available actions per resource: `read`, `write`, `delete`, `all`.

## Step 1: Create the OAuth App

1. Open the Outreach Developer Portal at <https://developers.outreach.io/apps>.
2. Create a new app.
3. Enter an app name. The app identifier is pre-populated from the name; edit if needed (must be longer than 6 characters).
4. Click **Create app**.

## Step 2: Configure API Access

1. Open the **API access** tab on your app's configuration page.
2. Add a redirect URI:

```
https://mcp-gateway.getcakewalk.io/api/v1/Auth/Callback
```

3. Select the scopes listed in [Required Scopes](#required-scopes) above.

## Step 3: Copy the Client ID and Client Secret

Generate the credentials. Outreach shows the Client Secret once. Copy both values before navigating away. If you lose the secret, click **Regenerate** to mint a new one.

Development credentials provision instantly. Production credentials require clicking **Publish** and completing Outreach's review process; plan for a delay measured in days if your Connection is for production use.

## Step 4: Paste Credentials Into Cakewalk

1. Open <https://app.getcakewalk.io>.
2. Go to All Connections.
3. Find Outreach.
4. Click Edit credentials.
5. Paste the Client ID and Client Secret.
6. Save.

## Verifying It Works

The Outreach Connection card flips to Active on All Connections. From an agent platform connected to Cakewalk, ask the agent to list your recent Outreach prospects. If Outreach returns results, the Connection is live.

## Troubleshooting

* Invalid redirect URI on consent: confirm the redirect URI on your Outreach app matches `https://mcp-gateway.getcakewalk.io/api/v1/Auth/Callback` exactly.
* 403 errors on specific tools: confirm every scope in [Required Scopes](#required-scopes) is selected on the API access tab.
* Production publish stuck in review: contact <platform@outreach.io> for status. Until Production is published, use development credentials.

## Learn More

* [Outreach OAuth](https://developers.outreach.io/api/oauth/)
* [Building your first Outreach extension](https://developers.outreach.io/client-extensions/your-first-outreach-extension/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-connections/outreach.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.