Outreach (Preview)
Outreach is an AI Revenue Platform for go-to-market teams. This connector gives agents and automated workflows access to live Outreach data through the Model Context Protocol. Search accounts, prospects, and opportunities, review deal stages and pipeline, analyze sequence enrollment and engagement, retrieve sent emails and calendar events, and pull Kaia call recordings and transcripts. Every request runs under the signed-in user's identity and honors their Outreach profile permissions.
This connector is available in the following products and regions:
| Service | Class | Regions |
|---|---|---|
| Copilot Studio | Premium | All Power Automate regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Logic Apps | Standard | All Logic Apps regions except the following: - Azure Government regions - Azure China regions - US Department of Defense (DoD) |
| Power Apps | Premium | All Power Apps regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Power Automate | Premium | All Power Automate regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Contact | |
|---|---|
| Name | Outreach Support |
| URL | https://support.outreach.io/ |
| support@outreach.io |
| Connector Metadata | |
|---|---|
| Publisher | Outreach |
| Website | https://www.outreach.ai |
| Privacy policy | https://www.outreach.io/privacy-statement |
| Categories | Sales and CRM |
Outreach
Outreach is the AI Revenue Platform used by go-to-market teams at thousands of enterprises. This connector lets Microsoft Copilot Studio agents reason over Outreach data and execute revenue workflows under the signed-in user's identity and permissions.
The connector uses the Model Context Protocol (MCP) streamable HTTP transport. A single agent-callable operation (InvokeServer) exposes the underlying MCP server, through which tools for accounts, prospects, opportunities, sequences, emails, Kaia call recordings, and users are made available to agents at runtime.
Pre-requisites
- An active, licensed Outreach user account.
- Amplify capability enabled on the Outreach instance and the user account.
- Tenant administrator consent for the OAuth 2.0 application in Outreach.
Supported operations
| Operation | Description |
|---|---|
InvokeServer |
Invokes the Outreach MCP server (JSON-RPC 2.0 over streamable HTTP) to discover available tools and execute them. The MCP server exposes read tools across accounts, prospects, opportunities, sequences, emails, calendar events, Kaia call recordings, sequence states, users, and supporting metadata. |
The MCP server exposes the following tool families to agents at runtime:
- Users:
current_user,user_search,user_get_by_id - Accounts:
account_search,account_search_by_external_id,account_get_by_id,account_answer_question - Prospects:
prospect_search,prospect_search_by_external_id,prospect_get_by_id - Opportunities:
opportunity_search,opportunity_search_by_external_id,opportunity_get_by_id,opportunity_answer_question,opportunity_stage_fetch - Sequences:
sequence_search,sequence_state_search - Activity:
emails_search,calendar_events_fetch,kaia_meeting_search - Stages and metadata:
stage_fetch,filter_fields_fetch,input_fields_fetch - Meeting prep:
prepare_for_meeting
Obtaining credentials
The connector authenticates with Outreach using OAuth 2.0 (Authorization Code Grant). A multi-tenant OAuth application is registered in Outreach by Outreach Corporation. The Client ID and Client Secret are provided to Microsoft via Partner Center at submission time.
Scopes requested at consent:
accounts.read prospects.read opportunities.read sequences.read sequenceStates.read mailings.read calls.read users.read
The redirect URI used by Power Platform is the global per-connector URI:
https://global.consent.azure-apim.net/redirect
Getting started
- Install the connector from the Microsoft 365 / Power Platform admin center.
- Create a connection. Each end user signs in with their Outreach credentials and grants the requested scopes.
- Add the connector as a tool to a Copilot Studio agent. The agent discovers the underlying MCP tools at runtime via
tools/listand can call them per user request. - Verify the connection by asking the agent a basic Outreach question, for example: "Find the Acme account."
Known issues and limitations
- The connector uses the MCP streamable protocol (
x-ms-agentic-protocol: mcp-streamable-1.0) and is intended for use by Copilot Studio agents. Power Automate flows cannot invoke MCP-protocol operations directly. - Only data the signed-in user is permitted to see in Outreach is returned. Outreach Profile-level access controls are honored on every call.
- Outreach instances and users must have the Amplify capability enabled.
- Outbound traffic from the connector to Outreach originates from the standard Power Platform IP ranges; Outreach allowlists these.
FAQ
Does this connector work with Power Automate flows?
It is designed for Copilot Studio agents. Power Automate flows do not currently invoke MCP-protocol operations.
What data does the connector send to Microsoft?
The connector sends JSON-RPC requests on behalf of the signed-in user to the Outreach MCP endpoint and returns the responses to the calling agent. Outreach honors the user's Profile permissions on every call.
Where can I get support?
Contact support@outreach.io or visit https://support.outreach.io/.
Actions
| Invoke Outreach MCP server |
Sends a JSON-RPC 2.0 request to the Outreach Model Context Protocol (MCP) server and returns the response. Use this to discover tools (method 'tools/list') or invoke a tool (method 'tools/call') for accounts, prospects, opportunities, sequences, emails, calendar events, Kaia call recordings, and users under the signed-in user's identity. |
Invoke Outreach MCP server
Sends a JSON-RPC 2.0 request to the Outreach Model Context Protocol (MCP) server and returns the response. Use this to discover tools (method 'tools/list') or invoke a tool (method 'tools/call') for accounts, prospects, opportunities, sequences, emails, calendar events, Kaia call recordings, and users under the signed-in user's identity.
Returns
JSON-RPC 2.0 response envelope from an MCP server invocation.
- Body
- McpResponse
Definitions
McpResponse
JSON-RPC 2.0 response envelope from an MCP server invocation.
| Name | Path | Type | Description |
|---|---|---|---|
|
JSON-RPC version
|
jsonrpc | string |
JSON-RPC protocol version. Always '2.0'. |
|
Request ID
|
id | string |
Identifier matching the original request. |
|
Result
|
result | object |
Method-specific result payload returned by the MCP server. |
|
Error code
|
error.code | integer |
JSON-RPC error code. |
|
Error message
|
error.message | string |
Human-readable error message. |