Salesloft on Make Enterprise
Salesloft is a sales engagement platform. Sequences, tasks and activity data that have to stay consistent with the CRM. Here is what Make lists for it, what we build around it, and what to settle before you automate it.
What does Make list for Salesloft?
Make's page lists 1 trigger, 5 actions, 1 search by name.
Triggers
- Watch Records
Actions
- Create a Record
- Delete a Record
- Get a Record
- Make an API Call
- Update a Record
Searches
- Search Records
Module lists change as Make updates the app. Treat this as a snapshot and confirm on Make's page before you scope work.
What do we build around Salesloft?
These are the kinds of scenarios we build for sales engagement. They describe our work, not features of Salesloft.
- Prospect hand-offs from the CRM into sequences
- Activity and reply data written back to the CRM
- Do-not-contact checks before anyone is enrolled
- Rep-level reporting feeds
Example flows
- A qualified lead is enrolled in the right sequence after a do-not-contact check
- A reply stops the sequence and creates a task in the CRM
- Weekly activity totals feed the sales report
What should you settle before automating Salesloft?
Settle these before the first production scenario so builders can start without waiting on a later security review.
- Which system owns do-not-contact status
- What happens to a prospect who is already in another sequence
- Which fields the tool may write back to the CRM
- Who can enroll people in bulk
Platform-level controls such as SSO, roles, encryption and log retention are Make's own published terms; see make.com/security and our Make Enterprise page for how we scope against them. Make describes the Enterprise plan itself at make.com/enterprise.
Frequently asked questions
Can Make connect to Salesloft?
Yes. Make has a Salesloft app, and its page states that it is supported and maintained by Make. It is listed in Make's Enterprise integrations category. The modules and names on this page are what Make shows on its own Salesloft page as of November 5, 2026, so check Make's page for the current list.
What do you build around Salesloft?
We build the scenarios around it: prospect hand-offs from the CRM into sequences; activity and reply data written back to the CRM; do-not-contact checks before anyone is enrolled. Scope is set on a call, and each scenario is documented in plain language before hand-over.
What should we decide before automating Salesloft?
Start with the guardrails: which system owns do-not-contact status; what happens to a prospect who is already in another sequence; which fields the tool may write back to the CRM. Settling these first lets builders start without waiting on a security review later.
Does the connection need Salesloft admin access?
That depends on what the scenarios do and on Salesloft's own permission model. We aim for a dedicated service account with the narrowest role that works, and we record which scenarios write and which only read. Your Salesloft administrator decides what that account may reach.
Consultants in a Box is a Make partner. This page is written by us and is not published by Make or by Salesloft's vendor. Salesloft, Make and related names are trademarks of their owners. Statements about Make's platform are the ones Make publishes.
Planning to automate Salesloft?
Book a call. We map your systems to the pages here, agree the guardrails and give you a written scope and price afterwards.