Resources · Make integration

SalesTrigger Make integrationAutomate SalesTrigger with Make.

Can Make feed your SalesTrigger campaigns without copy and paste? The SalesTrigger Make integration gives you 2 action modules, one for LinkedIn leads and one open door to the API. This guide is for sales teams that prospect on LinkedIn, and it walks you to a working scenario.

Try the SalesTrigger integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SalesTrigger Make integration do?

The SalesTrigger Make integration lets a Make scenario (the automation you build, a chain of steps) place LinkedIn leads into a SalesTrigger campaign for you. Each step is a module, one brick of one app. SalesTrigger brings two action modules and no trigger, so another app or a schedule starts the run.

Leads from a form land in the right campaign. A prospect fills in a form in another app with a LinkedIn profile. That form starts the scenario, and Add Linkedin Lead to a Campaign drops the person into your outreach sequence without anyone touching a spreadsheet.

A shortlist in a sheet becomes a campaign. Your team gathers profiles in a sheet, one row per person. Make reads each row as a bundle (one item passed from module to module) and adds every lead to the campaign you picked.

Anything the listed module skips goes through the API. Make an API call reuses the same connection to reach other parts of the SalesTrigger API, when your use case needs more than adding leads.

Be aware of the limits. The Make documentation for SalesTrigger is marked as limited because little public information exists about the app, so test each step with real data before you rely on it. The Make troubleshooting guide helps when a run fails, and Make pricing explains how runs count on your plan. If you are weighing tools, read n8n vs Make.

Connect

How do you connect SalesTrigger to Make?

  1. 01

    Open the connection window

    Add the SalesTrigger module to your scenario and click Create a connection. A connection is your SalesTrigger account linked to Make once, then reused by both modules of the app.

  2. 02

    Name it and authorize

    Give the connection a name if you like, handy when several people or accounts share one Make team. Then either approve Make on the SalesTrigger page that opens, or paste the key SalesTrigger gives you.

  3. 03

    Save and check

    Click Save. The connection now appears in the module, and Make can read what your account exposes. Pick it in any later SalesTrigger module instead of creating a second one.

First scenario

Your first scenario with SalesTrigger

GoalWhen a new lead shows up in another app, Make adds that LinkedIn lead to a SalesTrigger campaign.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the +. The first module is the app where your leads appear, since SalesTrigger has no trigger of its own.

  2. 02

    Set up the starting app

    Search for the app that holds your leads, such as your form or sheet tool, choose its module and connect the account. Fill in its fields so it returns one lead per bundle.

  3. 03

    Add the SalesTrigger action

    Click the + on the right, search SalesTrigger and choose Add Linkedin Lead to a Campaign. Create the connection, then map the lead data coming from the first module.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles each module received, so you can confirm the lead reached the campaign before going live.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Adjust it, then switch the scenario on.

Modules

What SalesTrigger can do in Make

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

SalesTrigger1

Add Linkedin Lead to a Campaign

ActionIn the docs only

This action puts a LinkedIn lead straight into one of your SalesTrigger campaigns, so prospects collected elsewhere enter your outreach without manual entry. Each lead it handles costs one operation, the unit Make counts on your plan.

When to use it
a lead comes in from a form, a sheet or a CRM and should join a campaign without anyone retyping it.
Watch out
the docs list no fields for this module, so run the scenario once with a real profile and check the result in SalesTrigger.
SalesTrigger2

Make an API call

ActionIn the docs only

With this module you reach any endpoint of the SalesTrigger API from your scenario, reusing the connection you already created. It covers whatever the dedicated module does not do.

When to use it
you need a SalesTrigger feature beyond adding leads, and you know which endpoint serves it.
Watch out
you write the request yourself, and the Make docs describe no SalesTrigger endpoint, so test each call with Run once before activating.
Need help

Need help automating SalesTrigger with Make?

A person reads every message.

FAQ

SalesTrigger and Make: common questions

01Is the SalesTrigger Make integration free?
Yes, SalesTrigger is a standard app in Make, so it works from the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Every SalesTrigger module you run counts as one operation, the unit Make tracks on your plan, whatever plan you are on.
02What do you need to connect SalesTrigger to Make?
A SalesTrigger account and a Make account. The Make documentation lists no special prerequisite and no official steps for this app, so you follow the generic flow: add a SalesTrigger module, click Create a connection, name it if you want, authorize Make on the SalesTrigger page or paste the key SalesTrigger provides, then click Save. Both modules then share that single connection. Once saved, you never paste credentials again: every new SalesTrigger module in any scenario simply lets you pick the existing connection from a list.
03Does SalesTrigger trigger Make scenarios in real time?
No, because SalesTrigger has no trigger module in Make. The scenario has to start somewhere else. You can open it with an instant trigger from another app, which that app calls through a webhook as soon as something happens, or with a scheduled trigger that Make checks on the scenario schedule, every 15 minutes by default. The SalesTrigger action then runs on each bundle it receives. On paid plans you can shorten that schedule to 1 minute, which keeps SalesTrigger closer to the moment a lead appears in the other app.
04What if a SalesTrigger module is missing in Make?
Use the Make an API call module. It reaches any endpoint of the SalesTrigger API with the connection you already have, so a feature without a dedicated module is still reachable. Keep in mind that the Make documentation for SalesTrigger is limited, because little public information exists on the app. Test every new request with Run once, and check the result inside SalesTrigger before you switch the scenario on. If a request fails, open the bundle that the module received after Run once and compare it with what you sent.
05Should you use Make or n8n for SalesTrigger?
It depends on what the rest of your stack already runs on. In Make, SalesTrigger offers two modules: one that adds LinkedIn leads to a campaign, and Make an API call for everything else. Many apps also have an n8n node, so check whether one exists for SalesTrigger and what it covers. Compare the two on the actions you need, then pick the tool where your other scenarios already live. In Make, the Make an API call module also reaches the SalesTrigger API directly when no ready-made module covers the action you need.
Same platform

Other docs you might need on this stack.

Browse all integrations