In this article:
Overview
Crossbeam’s newest API endpoint gives you programmatic access to ecosystem signals, both partner-driven events and those triggered by your own CRM activity events. These signals are designed to help your teams and tools act on partner activity as it happens. You can:
Access these signals via the API for on-demand data retrieval
Receive these signals via a webhook for real-time delivery into your existing
Together, these options make it easier to connect Crossbeam data to the systems your team already uses for automation, analytics, and reporting.
What are signals?
A signal is a data point or event that represents a meaningful partner activity, such as an opportunity opening or closing from a partner's CRM or from your reps' CRM activity.
Signals help your teams:
Detect opportunities or risks early (a partner closing a deal in an overlapping account)
Automate next steps (notify account owners, trigger workflows)
Attribute partner influence on closed-won deals
Power AI-driven insights and recommendations
These are delivered in real time through our webhook or via the API.
Signal Types
There are two categories of signals:
Partner-triggered signals fire based on activity in your partners' CRM:
Partner Deal opened—a partner opens a new opportunity on a shared account
Partner Deal closed-won—a partner closes a deal on a shared account
Own opportunity signals fire based on activity in your own CRM on accounts with an active partner overlap:
Own deal opened—one of your reps opens an opportunity on an account where a partner overlap exists
Own deal closed-won—one of your reps marks an opportunity closed-won on an account where a partner overlap exists
✍️ Note
Own opportunity signals fire only when the account has an active partner overlap at the time of the event. If no overlap exists, no signal is sent.
Signals can also fire on Net New Accounts—accounts your partners are sharing with you that don't yet exist in your CRM. Learn more about Net New Accounts here.
✍️ Note
Signals also power Automations. The Automations triggers for a partner opening a new opportunity or closing a deal won on a mutual account use these same Ecosystem Signals, so they need the same partner requirements below. See Setting Up Automations in Crossbeam.
‼️ Important
API calls and Webhooks are included in Record Exports limits.
Contact the support team at support@crossbeam.com for further assistance.
Requirements
To receive partner-triggered signals, your partner must:
Have a CRM connected to Crossbeam
Be syncing and sharing the following fields with you:
Deal open date
Deal close date
Deal is closed
Deal is won
✍️ Note
Your company only needs to sync these fields with Crossbeam—you do not need to share them back with your partner. If you'd also like your partners to receive signals based on your CRM activity, you'll need to share these fields with them as well.
To use Own Opportunity Signals, your company must be syncing the same CRM fields above. No additional partner sharing requirements apply—Crossbeam checks for an active overlap at the time of the event.
Receiving Contact Information on Opportunity Signals
To receive contact information on opportunity signals, your partner must also be syncing and sharing CRM contact data.
If contact data is included, signals may contain the following fields:
Required Contact Fields
Contact Name
Contact Title
Signal Contact Parameters
contact_name– Full name of the contactcontact_role– The contact’s role at the organizationcontact_type– Classification of the contact (decision maker, influencer, buyer)
Contact information will only appear in a signal if your partner is actively sharing this data.
Plan Access
Free and Connector plans: No access
Supernode plan: Access to the API (Signals and the API endpoint)
Enterprise plan: Access to the API and Webhook
To upgrade your account, visit the Plan & Billing page.
✍️Note: Only Admin users can create or edit webhooks and API integrations.
How It Works
Webhooks and API integrations are set up on the API page (Data > API). For more on the page and its tabs, see How to Use the API Page in Crossbeam.
Crossbeam makes ecosystem signals available in two main ways: via webhook and API endpoint.
Webhook
Webhook (Push Model): Delivers immediate, near real-time updates to your system as events occur. This is ideal when you need to trigger workflows, send notifications, or automate actions in response to partner events. Because updates are pushed automatically, you don't need to pull data repeatedly, ensuring your system responds instantly.
Example: When a partner opens a new opportunity on a shared account, Crossbeam “pings” your connected app—such as Slack, HubSpot, or a custom internal tool—to trigger a workflow or alert.
Best for:
Real-time notifications or automations
Systems that should respond instantly to partner events
How to Set Up a Webhook in Crossbeam
From the left-side Navigation Menu in Crossbeam:
Click on Data → API → Open Webhook tab and click Create Webhook
Next, define your webhook settings:
Event types → Choose which event(s) you’d like to receive signals for:
Partner Deal opened (when a partner opens a new opportunity)
Partner Deal closed-won (when a partner closes a deal)
Own deal opened (your rep opens an opportunity on an overlap account)
Own deal closed-won (your rep closes a deal on an overlap account)
Add Webhook name
Add Destination URL
After clicking Finish, a secret key will appear
Copy and store it safely—you won’t be able to view this same key again
Some external tools may require this key to authenticate incoming data
See Developer Documentation here for more details
Test your webhook
Crossbeam will send a test call to the destination URL you provided
If the test fails, you can click the edit configuration button and try again until it succeeds
Once you pass the test, you will be able to move on to apply filters
Define and select filters for your webhook
✍️ Note
Filters cannot be added until the webhook has been successfully tested.
Filters let you narrow which partners or Populations you want to receive signals for
The webhook will only be triggered for the overlaps between your selected Populations and partner/s’ selected Populations
Click Save Settings to finalize setup. Your webhook is now active and will appear on the Webhooks tab.
To manage your webhook later, navigate to Data > API, open the Webhooks tab, and click Settings next to the webhook.
👉 For more technical details on configuring your webhook, visit our Developer Documentation
API Endpoint
API Endpoint (Pull Model): Provides on-demand access to data, which you retrieve by pulling updates from the API. This is useful for supplemental insights, reporting, or tasks that don't require immediate action. Unlike webhooks, you control when and how often you pull the data.
Example: Your CRM or internal analytics platform can call the Crossbeam API to fetch all new Opportunity Closed Won signals from the past 24 hours.
Best for:
On-demand insights or scheduled analyses
Use cases that don't require immediate real-time actions
How to Set up APIs in Crossbeam
From the left-side Navigation Menu in Crossbeam:
Click on Data > API, open the API Integrations tab, and click Create Integration.
Next, define your API settings:
Integration name
Integration description
Callback URL and Allowed Origins
Click Create Integration, then follow the step-by-step instructions in our Developer Documentation to complete your endpoint setup.
👉 See setup details in the Developer Documentation
Use Cases
Use Case | How It Works | Model |
Instant deal notifications | When a partner opens a new opportunity on an overlap, send a Slack alert to the account owner | Webhook |
Trigger outreach cadences | Automatically start a HubSpot or Outreach sequence when a partner adds a new opportunity | Webhook |
Timed follow-ups | Wait 60 days after a partner’s Closed Won deal, then trigger a “better together” campaign | Webhook |
Deal prioritization scoring | Fetch Closed Won signals daily to update opportunity scores in your CRM | API Endpoint |
Co-sell warm intro alert | Notify a partner manager the moment your rep opens an opp where the partner has a relationship | Webhook |
Closed-won attribution | Fetch own opportunity Closed Won signals daily to log partner influence in your CRM | API Endpoint |
FAQs
Does the webhook count towards Record Exports?
Yes, just like Crossbeam's existing API, the new webhook will also count towards Record Export limits.
Do you need to have a license to leverage signals and the webhook?
No additional licenses are required. Only Admins can create webhooks, but anyone in your organization can benefit from the workflows or alerts they trigger in other tools.
Can I access signals if my data source is a CSV or Google Sheet?
Yes, as long as your partner has a connected CRM and is sharing the required fields, you'll receive partner-triggered signals.
Own opportunity signals require your own CRM to be connected—they are not available if your data source is a CSV or Google Sheet.
How is this different from Crossbeam's existing API?
Our existing API provides access to raw overlap data.
The new API and webhook deliver:
Event-based, enriched data—like “Opportunity Opened” or “Closed Won” as they happen
Real-time push updates via webhook (or on-demand pulls via API)
AI-ready formats for use with intelligent systems like Crossbeam’s MCP or other AI tools
Richer integrations that reflect structured, real-time data streams
Support for both partner-triggered and own deal event types.
Are Greenfield account signals supported?
Yes! You can receive ecosystem signals related to Net New Accounts — accounts your partners are sharing with you that do not already exist within your CRM. Learn more about Net New Accounts and the webhook functionality here.
📄 Related Articles