Overview
The Crossbeam integration lets users connect their Crossbeam organization so Alysio can query partners, partner populations, populations, account and lead records, and account/lead overlaps on their behalf. Users can ask Alysio to get organization info, list partners and populations, get partner or population details, search their own account or lead records, list or search account overlaps and lead overlaps with partners, and get overlap account counts—all in natural language. The integration uses the user’s connected Crossbeam credential; the organization context (org_id) is supplied with the connection so all calls are scoped to that Crossbeam organization. Usecrossbeam_get_partners_list to discover partner IDs; use crossbeam_get_partner_population_list and crossbeam_get_population_list for population IDs when filtering overlaps or search.
Supported capabilities / objects
- Organization — Get detailed information for the connected Crossbeam organization (org_id from connection context).
- Partners — List partners; get partner by ID.
- Partner populations — List partner populations; get partner population by ID.
- Populations — List your organization’s populations; get population by ID.
- Records — Search account records (term, record_id, domain, or opportunity_id; at least one of term/record_id/domain required; term and domain min 3 chars). Search lead records (term, record_id, or email; at least one required; term and email min 3 chars).
- Overlaps — List or search account overlaps and lead overlaps (optional filters: partner_id, partner_population_ids, population_ids); get overlaps account count by partner (and optional partner_population_ids).
Authentication
Method: OAuth 2.0 (Crossbeam). The MCP sends requests using a Bearer token and a credential ID that identifies the user’s connected Crossbeam account. Requests are scoped to a Crossbeam organization; the organization ID (org_id) is provided as part of the connection or session context, so all tools operate on that organization. Redirect URI: Configured when the Crossbeam integration is set up in Alysio. The Crossbeam OAuth app must allow this redirect URI. Token handling- OAuth tokens for the connected Crossbeam account are stored securely and refreshed automatically.
- Each user/tenant has their own credential and organization context; the MCP sends the appropriate credential and uses the org_id from context so calls are isolated per connection.
- On disconnect, that credential is no longer used and Crossbeam tools will not be available until the user reconnects Crossbeam.
| Scope / capability | Purpose |
|---|---|
| Organization | Get organization info. |
| Partners | List partners, get partner info. |
| Partner populations | List partner populations, get partner population info. |
| Populations | List populations, get population info. |
| Records | Search account records, search lead records. |
| Overlaps | List/search account and lead overlaps, get overlaps account count. |
MCP Tools
The Crossbeam MCP exposes the following tools. Users can invoke these capabilities through natural language in Alysio.| Tool | Description | Example user prompts |
|---|---|---|
crossbeam_organization_info | Returns detailed information for the connected Crossbeam organization (org_id from connection context). | ”Crossbeam organization info”, “What’s our Crossbeam org?” |
crossbeam_get_partners_list | Lists all partners connected to the organization, with optional pagination. | ”List Crossbeam partners”, “Show our partners.” |
crossbeam_get_partner_info | Returns detailed information for a partner by partner ID; use get_partners_list to find IDs. | ”Get partner 123”, “Partner details.” |
crossbeam_get_partner_population_list | Lists all partner populations for the organization, with optional pagination. | ”List partner populations”, “Partner populations.” |
crossbeam_get_partner_population_info | Returns detailed information for a partner population by population ID; use get_partner_population_list for IDs. | ”Get partner population 456”, “Partner population details.” |
crossbeam_get_population_list | Lists all populations owned by the organization. | ”List our populations”, “Crossbeam populations.” |
crossbeam_get_population_info | Returns detailed information for a population by population ID; use get_population_list for IDs. | ”Get population 789”, “Population details.” |
crossbeam_account_records_search | Searches your account records by term, record_id, domain, or opportunity_id; at least one of term, record_id, or domain required (term/domain ≥ 3 chars). | ”Search accounts for Acme”, “Find account by domain example.com.” |
crossbeam_leads_records_search | Searches your lead records by term, record_id, or email; at least one required (term/email ≥ 3 chars). | ”Search leads for john@company.com”, “Find lead by email.” |
crossbeam_overlaps_accounts_list | Lists account overlaps with optional filters (partner_id, partner_population_ids, population_ids) and pagination. | ”List account overlaps with partner X”, “All account overlaps.” |
crossbeam_overlaps_accounts_search | Searches account overlaps by term, record_id, or domain (one required; term/domain ≥ 3 chars), with optional partner/population filters. | ”Account overlaps for Acme”, “Overlaps for domain example.com.” |
crossbeam_overlaps_leads_list | Lists lead overlaps with optional filters (partner_id, partner_population_ids, population_ids) and pagination. | ”List lead overlaps”, “Lead overlaps for this partner.” |
crossbeam_overlaps_leads_search | Searches lead overlaps by term, record_id, or email (one required; term/email ≥ 3 chars), with optional partner/population filters. | ”Lead overlaps for john@company.com”, “Search lead overlaps.” |
crossbeam_get_overlaps_accounts_count | Returns the count of account overlaps by partner (and optional partner_population_ids); uses cursor pagination internally. | ”How many account overlaps with this partner?”, “Overlap counts by population.” |
App Behavior
- API calls are made on-demand only when the user asks something that requires Crossbeam data (e.g. organization, partners, populations, records, overlaps). There is no background sync; each request triggers the relevant Crossbeam API call using the user’s OAuth credential. The organization ID (org_id) from the connection/session context is sent where required.
- User asks: “Which of our accounts overlap with partner X and what are the counts by their population?”
- Alysio routes the request to the Crossbeam MCP.
- The MCP may call
crossbeam_get_partners_listto resolve partner X’s ID,crossbeam_get_partner_population_listfor population IDs, thencrossbeam_overlaps_accounts_searchorcrossbeam_overlaps_accounts_listwith partner_id and optionallycrossbeam_get_overlaps_accounts_countwith partner_id and partner_population_ids. - The request is sent with the user’s OAuth credential and org context.
- The MCP returns overlap and count data; Alysio presents the results in chat.
Troubleshooting
Common issues- Missing or expired connection — User sees errors or no Crossbeam data. Fix: Reconnect Crossbeam in Settings → Integrations (re-authorize via OAuth 2.0) and ensure organization context (org_id) is set.
- 401 Unauthorized — Token invalid or expired. Fix: Re-authorize the integration in Settings → Integrations.
- 403 Forbidden — Insufficient OAuth scopes. Fix: Ensure the Crossbeam OAuth app has the required scopes for organization, partners, populations, records, and overlaps.
- Search requires at least one parameter — account_records_search, leads_records_search, overlaps_accounts_search, and overlaps_leads_search require at least one of their search fields. Fix: Provide one of term, record_id, or domain for account/overlaps-account search; one of term, record_id, or email for leads/overlaps-leads search. term and domain/email must be at least 3 characters.
- Partner or population IDs — Several tools need partner_id or population_id. Fix: Use
crossbeam_get_partners_listfor partner IDs,crossbeam_get_partner_population_listfor partner population IDs, andcrossbeam_get_population_listfor your organization’s population IDs.
- Email: support@alysio.ai