Resources · Make integration

Salesloft Make integrationAutomate Salesloft with Make.

Can Make react the moment something happens in Salesloft? Yes. The Salesloft Make integration gives you 7 modules, including 1 instant trigger. This guide is for sales ops teams on the Enterprise plan: connect the account, then build and test a first scenario.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the Salesloft integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Salesloft Make integration do for you?

The Salesloft Make integration links your Salesloft account to Make, a visual tool where you chain apps together without writing code. Each automation is a scenario, and each brick in it is a module. With Salesloft you can react to new events, then create, read, update, search or delete records.

Keep records tidy after each event. Watch Records starts the scenario when Salesloft reports a new event. Add Get a Record to read the full record, then Update a Record to write back the values your team expects.

Push leads in from other tools. A form, a spreadsheet or another CRM can hand its data to Create a Record, so new prospects land in Salesloft without anyone retyping them. Run Search Records first if you want to skip people who already exist.

Reach what the list does not show. Make an API Call reuses your connection to call any endpoint of the Salesloft API, which covers the gaps left by the six ready-made modules.

One limit matters before you start: Salesloft is an Enterprise app in Make, so it only runs on the Enterprise plan. Check Make pricing first. Weighing another tool? The n8n vs Make comparison lays out the criteria, and Make training helps if scenarios are new to you.

Connect

How do you connect Salesloft to Make?

  1. 01

    Add a Salesloft module

    In your scenario, click the +, search for Salesloft and pick any module. In the module panel, click Create a connection. A connection is your Salesloft account linked to Make once, then reused by every Salesloft module.

  2. 02

    Authorize Make in Salesloft

    Give the connection a name if you like, something your team will recognize later. Salesloft relies on OAuth 2.0, so Make opens a Salesloft page where you sign in and approve access. You need an active Salesloft account for this.

  3. 03

    Save and check

    Click Save. Back in the module, the connection now shows in the list, and Make can read the objects your account has access to. Fill the module fields and move on to the next brick.

First scenario

Your first scenario with Salesloft

GoalWhen a new event occurs in Salesloft, Make reads the record involved and updates it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor. Search for Salesloft and pick Watch Records as the first module.

  2. 02

    Connect and set the trigger

    Click Create a connection, approve access in Salesloft, then fill the trigger fields. This trigger is instant: Salesloft calls Make through a webhook as soon as the event happens.

  3. 03

    Fetch the full record

    Click the + on the right of Watch Records and add Get a Record. Map the identifier from the trigger (Run once shows what its bundle carries) so Make loads the record that the event concerns.

  4. 04

    Write the update

    Add Update a Record after it. Map the record identifier again, then fill only the fields you want to change, using values from the previous modules.

  5. 05

    Test with Run once

    Click Run once, then trigger an event in Salesloft. Open each module's bubble to read the bundles it received, one bundle per item passed along.

  6. 06

    Switch it on

    Once the test looks right, switch the scenario on. Because the trigger is instant, the scenario waits for Salesloft to call it instead of checking on a schedule.

Triggers

What starts a Salesloft scenario

1 module starts a scenario when something happens in Salesloft. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Salesloft as soon as it happens.

Salesloft1Watch Records

Watch Records

Instant trigger

In Make“Triggers when a new event occurs.”

Watch Records gives you a scenario that wakes up by itself whenever Salesloft reports a new event, so your follow-up work starts without anyone pressing a button. Every event becomes a bundle, one item passed to the next module.

How it fires
instant. Salesloft calls Make through a webhook as soon as it happens; there is no polling interval to set.
When to use it
open any scenario that has to respond to activity in Salesloft, such as tidying a record or copying data to another tool.
Watch out
the event only carries what Salesloft sends, so add Get a Record when you need the full record.
Modules

Everything the Salesloft app can do in Make

Salesloft gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Salesloft1

Create a Record

Action

In Make“Creates a new record.”

New entries appear in Salesloft without manual typing: this action adds one record from the data mapped out of earlier modules, like a web form or a spreadsheet row.

When to use it
a prospect fills a form in another app and you want them in Salesloft right away.
Watch out
it creates every time it runs, so put Search Records before it to avoid duplicates.
Salesloft2

Delete a Record

Action

In Make“Deletes a record.”

Cleanup becomes part of the flow. This action removes one record from Salesloft, identified by the value you map into it, so outdated entries leave without a manual pass.

When to use it
a contact asks to be removed and another tool already logs that request.
Watch out
a deletion cannot be undone from Make, so test it with Run once on a record you can afford to lose.
Salesloft3

Get a Record

Action

In Make“Retrieves a record.”

You get the full details of one known record, ready to map into the next modules. It reads a single entry when you already hold its identifier, often handed over by the trigger.

When to use it
right after Watch Records, when the event alone lacks the values your next step needs.
Watch out
it needs an exact identifier; if you only know a name or an email, use Search Records.
Salesloft4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the Salesloft API offers becomes reachable, even when no ready-made module covers it. Make an API Call sends a request to the endpoint you choose, using the connection you already created.

When to use it
the six other modules stop short of the object or action your process requires.
Watch out
you write the request yourself, so keep the Salesloft API documentation open while you write it.
Salesloft5

Update a Record

Action

In Make“Updates a record.”

Existing entries stay current without anyone editing them by hand. Update a Record changes the fields you fill on one record and leaves the rest as it was.

When to use it
a status changes in your billing or support tool and Salesloft should reflect it.
Watch out
the record has to exist first, so pair it with Get a Record or Search Records to find the right identifier.
Salesloft6

Search Records

Search

In Make“Retrieves a list of records, filtered.”

Filtered lists come back from Salesloft. That way the scenario can check what already exists before it acts on anything. The module can return zero, one or several bundles, and each of them runs through the following modules.

When to use it
before Create a Record, to see whether a prospect is already there.
Watch out
with several results, every next module runs once per bundle, which adds operations on your plan.
Need help

Need help automating Salesloft with Make?

A person reads every message.

FAQ

Salesloft and Make: common questions

01Is the Salesloft Make integration free?
No. Salesloft is an Enterprise app in Make, which means it is reserved to the Enterprise plan. The Free plan covers 3,000+ standard apps with 2 active scenarios and a 15 minute minimum interval, but enterprise apps like Salesloft are not part of it. Make counts usage in operations, one execution of one module on one bundle, deducted from the credits of your plan. You also need an active Salesloft account, which is billed by Salesloft itself.
02What do you need to connect Salesloft to Make?
Three things: an active Salesloft account, a Make organization on the Enterprise plan, and permission to approve access in Salesloft. The connection uses OAuth 2.0. You add a Salesloft module, click Create a connection, sign in on the Salesloft page that Make opens, approve, and click Save. The connection is then reused by every Salesloft module in your scenarios, so you only do this once per account. Once it exists, Make lists the objects it can read when you fill a module.
03Does the Salesloft trigger in Make fire instantly?
Yes. Watch Records is an instant trigger: Salesloft calls Make through a webhook as soon as a new event occurs, and the scenario starts right away. You do not set a polling interval for it, unlike scheduled triggers that Make checks on the scenario's schedule. The lightning badge on the module marks it. Keep the scenario switched on: while it is off, events go unprocessed. Test it with Run once while you create an event in Salesloft.
04What if a Salesloft module you need is missing in Make?
Use Make an API Call. It reuses your Salesloft connection and lets the scenario call any endpoint of the Salesloft API, so an object or action outside the six listed modules is still reachable. You build the request yourself, so the Salesloft API documentation becomes your reference. If the blocker is the plan rather than a module, remember that Salesloft only runs on the Make Enterprise plan. Test each call with Run once before switching the scenario on.
05Should you pick Make or n8n for Salesloft?
It depends on your criteria. On the Make side, the facts are clear: 7 modules, one instant trigger, a generic API call module, and access limited to the Enterprise plan. The same app often has an n8n node too, so check the node list there before deciding. Compare how each tool fits your team, your plan and the objects you need, rather than relying on a general ranking between the two.
Same platform

Other docs you might need on this stack.

Browse all integrations