CRM integration guide
Salesloft + UbiGrowth workflows
Salesloft is a revenue engagement platform that owns cadences, rep workflow, and engagement measurement alongside a CRM. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Salesloft part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a CRM workflow around Salesloft with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Person, Account, Cadence, Step, Activity, Call, and Email. Salesloft People are keyed to CRM records through a configured link that can be absent, so an integration matching on email finds people the CRM cannot resolve and vice versa.
Salesloft is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
Grow is the usual destination for this connection, because the value shows up as outreach, reply handling, scheduling, and pipeline execution against the connected records.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
The recurring failure with a Salesloft integration is not connectivity. It is that the CRM ends up holding a record of what someone remembered to log, while the work itself happened in an inbox, a call, a spreadsheet, and a separate AI tool that never saw the account.
When that gap exists, everything built on top of it inherits it. Forecasts describe logged activity rather than real activity, outreach is written without the reply history that would make it relevant, and the team spends its day reconciling systems instead of working accounts.
You're likely here because
- Pipeline data is only as current as the last time someone logged activity
- Outreach is generated without the account history that would ground it
- The same account context is rebuilt in several tools each day
Record model
What a Salesloft integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Salesloft's.
Identity and matching
Salesloft People are keyed to CRM records through a configured link that can be absent, so an integration matching on email finds people the CRM cannot resolve and vice versa.
Start here
Read Cadence outcomes for one team, join them to the CRM opportunities they were meant to influence, and surface where activity is happening without pipeline movement.
What this will not do
It will not consolidate engagement history across tools. Salesloft records what happened in Salesloft; email sent from a mail client is invisible to it.
The constraint to plan around
Cadence membership rules are evaluated inside Salesloft, so adding a person externally can conflict with an exclusion rule and produce duplicate touches the rep will not see coming.
Build notes
What you actually have to reason about in Salesloft.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| cadence_id / current_state | cadence membership and position, owned by Salesloft and hazardous to write externally |
| do_not_contact | suppression state that must be honoured before any send decision, from any system |
| crm_id | the configured link to the CRM record, which can be null and frequently is on manually created people |
| email_address / secondary emails | a person can hold several, and the cadence sends to one of them |
| last_contacted_at | Salesloft-visible activity only; email sent from a mail client never appears |
Authentication
OAuth with refresh tokens, scoped per resource type. Team-level access differs from individual access in what it returns, so a report built with one credential and validated with another will disagree for reasons that look like a bug.
Events and delivery
Webhooks are available for the main activity types. Because cadence rules are evaluated inside Salesloft, an event tells you what happened rather than what will happen next, and inferring the latter externally will drift.
Workflow
How the Salesloft workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Read the pipeline as it stands
The workflow starts from live Salesloft accounts, contacts, and opportunities rather than an export, so prioritization reflects today's pipeline.
Step 02
Assemble the account context
Reply history, documents, and prior activity are brought together so the next action is grounded in what actually happened with the account.
Step 03
Decide the next action
ARIA proposes the specific next step for the account, with the supporting context attached, instead of producing a message with no stated reason.
Step 04
Execute through Grow
Outreach, reply handling, and scheduling run against the same record, staged for review while the motion is being proven.
Design decisions
The CRM decisions this connection forces.
Each of these has to be settled before the Salesloft workflow is allowed to write anything.
Step 01
Resolve the account identity
Decide how a person and a company are matched between Salesloft and the rest of the stack before any write happens. Most CRM integration damage is duplicate records created by a weak match rule.
Step 02
Keep execution attached to the opportunity
Outreach, replies, meetings, and stage changes should resolve back to the same opportunity, so the CRM reflects what actually happened rather than a parallel activity log.
Implementation path
How to implement the Salesloft workflow.
- 01
Decide which fields Salesloft owns and which the workflow may write, and write that decision down before enabling anything.
- 02
Define the identity match rule for contacts and companies, including what happens on an ambiguous match.
- 03
Start read-only. Prove that the workflow reads the right records before it is allowed to change any of them.
- 04
After activity-to-pipeline correlation works, invert it: identify accounts with pipeline movement and no recorded activity, which is usually where the CRM is wrong.
Governance
Controls that matter.
Control 01
CRM write scopes are limited to the specific objects the workflow needs, never blanket admin access.
Control 02
Duplicate creation is treated as a defect, not an acceptable side effect of syncing.
Control 03
Stage changes and closed-won updates stay under human control; automation prepares them rather than deciding them.
Failure modes
How a Salesloft integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
A prospect receives two touches in the same day from different cadences.
Cause
A person was added externally, bypassing an exclusion rule evaluated inside Salesloft.
Fix
Add through the API in a way that respects cadence rules, and check existing membership before adding.
Symptom 02
Engagement reporting disagrees with what reps say happened.
Cause
Salesloft records only what happened in Salesloft — mail sent from a client is invisible.
Fix
State the measurement boundary on the report rather than presenting it as complete activity.
Symptom 03
People cannot be matched back to CRM records.
Cause
crm_id is null on manually created people.
Fix
Match on email as a fallback and surface unmatched people as a data-quality queue rather than dropping them.
What changes at scale
Rate limits are per team with cost varying by endpoint. Bulk exports for reporting should use the bulk paths rather than iterating people, which exhausts the budget quickly on a large team.
Examples
What a working Salesloft workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Cadence operations
With Salesloft connected, ARIA works from live account, contact, and opportunity records instead of an export, so prioritization reflects the pipeline as it stands today.
Grounded outbound
Grow drafts outreach against the account history already in Salesloft, so the message references what actually happened with the account rather than a generic template.
Limitations and considerations
What to validate before you depend on this.
- Cadence membership rules are evaluated inside Salesloft, so adding a person externally can conflict with an exclusion rule and produce duplicate touches the rep will not see coming.
- Adding a person to a cadence externally can conflict with an exclusion rule that exists precisely to prevent double-touching. The rep finds out when the prospect does.
- When engagement data is already in the CRM and nobody disputes it. A second engagement system is worth its cost only when the cadence itself is the thing being managed.
- If Salesloft data is incomplete, the workflow inherits that gap. Connected context is not automatically accurate context.
- Custom objects, custom fields, and heavily-customized permission models change what an integration can safely do; validate them against your own instance rather than the vendor default.
FAQ
Salesloft integration questions.
What records does a Salesloft integration actually work with?
The primary records are Person, Account, Cadence, Step, Activity, Call, and Email. Salesloft People are keyed to CRM records through a configured link that can be absent, so an integration matching on email finds people the CRM cannot resolve and vice versa.
What should the first Salesloft workflow be?
Read Cadence outcomes for one team, join them to the CRM opportunities they were meant to influence, and surface where activity is happening without pipeline movement.
What will a Salesloft integration not do?
It will not consolidate engagement history across tools. Salesloft records what happened in Salesloft; email sent from a mail client is invisible to it.
What is the main constraint to plan around?
Cadence membership rules are evaluated inside Salesloft, so adding a person externally can conflict with an exclusion rule and produce duplicate touches the rep will not see coming.
What changes about a Salesloft integration at scale?
Rate limits are per team with cost varying by endpoint. Bulk exports for reporting should use the bulk paths rather than iterating people, which exhausts the budget quickly on a large team.
How does authentication work for Salesloft?
OAuth with refresh tokens, scoped per resource type. Team-level access differs from individual access in what it returns, so a report built with one credential and validated with another will disagree for reasons that look like a bug.
Does Salesloft support webhooks, and can they be trusted?
Webhooks are available for the main activity types. Because cadence rules are evaluated inside Salesloft, an event tells you what happened rather than what will happen next, and inferring the latter externally will drift.
What is the risk of writing to Salesloft?
Adding a person to a cadence externally can conflict with an exclusion rule that exists precisely to prevent double-touching. The rep finds out when the prospect does.
When is connecting Salesloft the wrong call?
When engagement data is already in the CRM and nobody disputes it. A second engagement system is worth its cost only when the cadence itself is the thing being managed.
What should a Salesloft integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Salesloft to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Will this create duplicate records in Salesloft?
Only if the identity match rule is weak. Define how people and companies are matched, and how ambiguous matches are handled, before enabling any write path.
Does Salesloft stay the system of record?
Yes. The design assumption is that Salesloft remains authoritative for the objects it owns and the workflow builds around it rather than replacing it.
Can pipeline stages be updated automatically?
Stage progression should stay under human control. Automation can prepare and propose the update, but deciding that a deal moved is a judgment call.
How this access is governed
What ARIA is allowed to do in Salesloft, and who decides.
Connecting Salesloft is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.