Crossbeam is a partner ecosystem platform that lets companies find overlapping accounts and collaborate with partners.
It can be connected to Agen.co two ways, matching the Official / In-house filter in the connector picker:
- Official — Agen.co connects through Crossbeam's own hosted MCP server, so your AI agents work within the Crossbeam organization and permissions of the person who authorizes the connection.
- In-house — Agen.co wraps the Crossbeam Partner API directly through its own integration layer, using a dedicated OAuth app you register in your Crossbeam organization.
Pick Official if the built-in MCP tools cover what your agents need. Fall back to In-house if you need broader API coverage or finer-grained scope control.
Prerequisites
Prerequisites
- A Crossbeam account with a Full Access or Sales seat. No app registration or admin approval is needed — Crossbeam's MCP server uses OAuth 2.1 with PKCE and dynamic client registration, so no Client ID or Client Secret needs to be created beforehand.
- In the Agen.co portal, go to Connectors → My connectors and click Add connector.
- In the search bar, type
Crossbeamand select it from the results. - In the Instance Slug field, enter a slug for this connector instance — it prefixes each imported tool as
slug__tool, so a second instance of the same connector needs a slug of its own. Use lowercase kebab-case. You can change it later from the connector's settings. - Click Connect.
- You're redirected to Crossbeam to sign in, review the requested permissions, and approve access. No Client ID or Client Secret needs to be entered manually.
- Return to Agen.co and click Add below the list of tools that were added.
Crossbeam's MCP server is organization-specific — the connection only reaches partnership data in the Crossbeam organization you authorize against. To work across more than one organization, add the Crossbeam connector again with a different Instance Slug and authorize it against another organization.
Once connected, Crossbeam appears under My connectors with tools spanning:
| Area | What it covers |
|---|---|
| Overlaps | Finding accounts, leads, and partners shared with one or more partners |
| Accounts | Reading unified account context, owner information, and population membership |
| Contacts | Finding partner-shared contacts and key decision makers at an account |
| Prospecting | Finding net-new accounts from Pipeline Generation and ranked partner recommendations for open opportunities |
| Ecosystem | Reading recent partner activity and generating shareable Crossbeam list links |
| Knowledge | Answering questions about Crossbeam functionality and ecosystem-led growth practices |
Enabling the Crossbeam connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.
Crossbeam is a partner ecosystem platform that lets companies find overlapping accounts and collaborate with partners. Integrating Crossbeam with Frontegg lets your application read partnerships, populations, and reports, work with threads, and read the current profile on behalf of your users — all through Frontegg's integration layer. Crossbeam authenticates with OAuth 2.0 (Authorization Code flow), and every Partner API request is scoped to a specific Crossbeam organization, so you also provide your Organization ID.
Prerequisites
Prerequisites
- A Crossbeam account with access to your organization's settings
- Permission to create a custom integration (OAuth application) in Crossbeam
You register an OAuth 2.0 application in Crossbeam. The application provides the Client ID and Client Secret and defines the callback (redirect) URL that Crossbeam returns users to after they authorize access. You also need your Crossbeam Organization ID.
Sign in to Crossbeam and go to Settings → Integrations. Open the Custom section and create a new application (custom integration).
Set the application's Callback URL to your Frontegg Redirect URL: https://YOUR_MCP_GATEWAY_URL/integration-callback
Click Create.
Open the application (click View). Crossbeam displays the Client ID and Client Secret. Copy both values.
Keep your Client Secret safe
Keep your Client Secret safe
The Client Secret grants access to your account through the API. Treat it like a password and never expose it in client-side code or commit it to version control.
Every Crossbeam Partner API request is scoped to one organization. Your Organization ID is a UUID (for example xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). You can find it in your Crossbeam organization settings, or by calling the Partner API "current user" endpoint (GET https://api.crossbeam.com/v0.1/users/me), which returns the organization UUID.
Once you have your Client ID, Client Secret, and Organization ID, configure the integration in the Frontegg portal:
- Open the Frontegg portal and navigate to [ENVIRONMENT] → Integrations → Crossbeam.
- Enter the Client ID and the Client Secret.
- Enter your Organization ID (the organization UUID).
- Click Save.
Frontegg requests the following scopes during authorization:
| Scope | Description |
|---|---|
read:partnerships | Read partnerships |
read:populations | Read populations |
read:reports | Read reports |
read:threads | Read threads |
write:threads | Create and update threads |
read:profile | Read the current user profile |
offline_access | Obtain a refresh token for long-lived access |
Keep your credentials secure
Keep your credentials secure
Never share or commit your Client Secret to version control.