These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Integrations
Understand integrations for CRM with Lead Scoring.
- Business connections
- Acquisition sourcesin and out
- Scoring providerin and out
- Pipeline CRMin and out
- Connection records
- ConfigurationIntegrationConnections · in and out
- ReconciliationIntegrationEvents · in and out
- Agents
- Your agentWorks within the permissions you assign
Business connections
- Acquisition sources. Web forms and imports retain stable source identities and permission evidence.
- Scoring provider. Optional model requests use approved features, versioned configuration and an explicit contribution boundary.
- Pipeline CRM. Handoff requests retain their command key until the destination acknowledges account, contact and opportunity references.
Connection records
- Configuration. IntegrationConnections retains provider identity, enabled state and secret references.
- Reconciliation. IntegrationEvents retains command and provider correlation, including failed or unknown outcomes.
How connections are governed
service accounts, audit, pausingAdmin configures scoped credentials and authenticates callbacks. Keep imports and outgoing actions disabled until mappings are reviewed and representative results reconcile. Duplicate events do not repeat a business action. An unresolved provider response remains open instead of being presented as success.
The API is one more client of the same interface. Agent and automation →
# Example work after configuration
› Explain why this lead received its current score.
› List my qualified leads that still need a confirmed CRM handoff.
› Prepare a follow-up using the contact’s permitted channel.