Resources · Make integration

Sortlist Make integrationAutomate Sortlist with Make.

Can Make react when a new opportunity lands in your Sortlist inbox? The Sortlist Make integration gives you 6 modules: 4 triggers and 2 actions. This guide is for agencies that live on Sortlist, and it walks you from the connection to a first working scenario.

Try the Sortlist integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Sortlist Make integration do for you?

The Sortlist Make integration links your Sortlist account to Make, a no-code tool where you build a scenario: the automation itself, made of a chain of modules. Each module is one brick. Here, 4 of them watch what happens on Sortlist and 2 of them act on it for you.

Never miss a lead. Watch Received Opportunity starts a scenario when Make finds a new opportunity, so the rest of your stack hears about it without anyone refreshing the page.

Keep your pipeline honest. Watch Opportunity Application Sent and Watch Applied Opportunity follow the applications your agency has made, which is handy for logging them wherever your sales team already works.

Answer clients faster. Watch Direct Message Received picks up incoming messages, and Apply to an Opportunity lets a scenario send an application once the right data is gathered.

What Make does not give you here: no instant trigger (every watcher is scheduled) and no Make an API Call module. Make's own documentation for Sortlist is short and flagged as AI-generated, so check the details with Sortlist before relying on a field. The same kind of app often has an n8n node too; the n8n vs Make comparison helps you pick. New to the tool? Start with the Make review, then the Make training.

Connect

How do you connect Sortlist to Make?

  1. 01

    Open a Sortlist module

    Add any Sortlist module to your scenario, then click Create a connection. A connection is your Sortlist account linked to Make once and reused by every Sortlist module after that.

  2. 02

    Name it and add your token

    Give the connection a name you will recognize later, which helps when several people share the workspace. Then authorize Make or paste the API token that Sortlist gives you, as the window asks.

  3. 03

    Save the connection

    Click Save. Make checks the credentials and, if they are accepted, the module becomes ready to configure. Every other Sortlist module you add can reuse this same connection.

First scenario

Your first scenario: reply to a fresh Sortlist opportunity

GoalWhen a new opportunity reaches your agency on Sortlist, Make sends your application for it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. That empty canvas is where the whole automation will take shape.

  2. 02

    Add the trigger

    Search for Sortlist, pick Watch Received Opportunity and attach your connection. This module starts the scenario each time Make finds a new opportunity on its scheduled check.

  3. 03

    Add the application

    Click the + on the right of the trigger and choose Apply to an Opportunity. Map the opportunity from the first module so the application targets the right one, and read what each field asks for.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles each module received, one bundle per opportunity, so you can check what was sent.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest gap.

Triggers

Which Sortlist triggers can start a scenario?

4 modules start a scenario when something happens in Sortlist. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Sortlist as soon as it happens.

Sortlist1Watch Applied Opportunity

Watch Applied Opportunity

triggerIn the docs only

You get a scenario that wakes up for opportunities your agency has applied to, as the module name suggests, so a follow-up can start without anyone copying details by hand.

How it fires
scheduled. Make checks the app on the scenario's schedule, not at the exact moment something changes.
When to use it
when an application is on its way and you want a task created in your project tool so the pitch gets prepared.
Watch out
Make's documentation gives no description of this module, so run it once and read the bundle before building on its data.
Sortlist2Watch Direct Message Received

Watch Direct Message Received

triggerIn the docs only

Incoming client messages on Sortlist can reach your team where it already talks, because this trigger hands each new message to the next module as a bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a message shows up at the next check rather than instantly.
When to use it
when prospects write to you directly and your account manager spends the day in a chat tool rather than in Sortlist.
Watch out
the docs list no fields for this module; test it with Run once to see what a message bundle actually contains.
Sortlist3Watch Opportunity Application Sent

Watch Opportunity Application Sent

triggerIn the docs only

This one gives you a clean record of every application once it has gone out, which is the moment most agencies want to log a deal in their CRM.

How it fires
scheduled. Make checks the app on the scenario's schedule and passes along what it found since the previous check.
When to use it
when sales wants each sent application to open a deal automatically, instead of someone typing it in after the fact.
Watch out
its name sits close to Watch Applied Opportunity; run both once and compare their bundles before choosing one.
Sortlist4Watch Received Opportunity

Watch Received Opportunity

triggerIn the docs only

New business is what this trigger surfaces: each opportunity Sortlist sends your agency becomes a bundle that the rest of the scenario can route, store or answer.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and on paid plans the gap can go down to 1 minute.
When to use it
when speed matters on new briefs and the partner who qualifies them should hear about each one at the next check.
Watch out
every check and every bundle uses operations on your plan, so pick a schedule that matches how quickly you really reply.
Modules

Which Sortlist actions can Make run?

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

Sortlist1

Apply to an Opportunity

ActionIn the docs only

Your application goes out from inside a scenario, so the data gathered by earlier modules turns into an actual answer on Sortlist without a trip to the website.

When to use it
after Watch Received Opportunity, once the opportunity has been checked and your standard pitch is ready to map in.
Watch out
an application is sent for real, so test with Run once on a single opportunity before you switch the scenario on.
Sortlist2

Send Universal Request

ActionIn the docs only

This module is your way out when the other five do not cover the need: judging by its name, it sends a request of your own design to Sortlist through your connection.

When to use it
when a Sortlist task you need has no dedicated module, and you are comfortable reading the Sortlist API documentation.
Watch out
Make's docs describe nothing about it, so check what Sortlist expects before sending anything that changes data.
Need help

Need help automating Sortlist with Make?

A person reads every message.

FAQ

Sortlist Make integration: common questions

01Is the Sortlist Make integration free?
Yes, on the Make side. Sortlist is a standard app, so it is available from the Free plan, alongside 3,000+ other standard apps. The Free plan gives you 2 active scenarios, a minimum gap of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the gap to 1 minute and count usage in credits each month. Your Sortlist subscription is a separate matter: check the Sortlist pricing page for that side.
02What does the Sortlist Make connection require?
An active Sortlist account and an API token, according to Make's documentation. That documentation gives no specific connection steps, so you follow the usual path: add a Sortlist module, click Create a connection, optionally name it, authorize Make or paste your token, then click Save. The connection is stored once and reused by every Sortlist module in your scenarios. Note that Make marks its Sortlist page as AI-generated, so if a step looks different on screen, trust Sortlist's own instructions.
03Do the Sortlist triggers in Make fire in real time?
No. All 4 Sortlist triggers are scheduled, a type Make's catalogue infers from their names: Make checks Sortlist on the scenario's schedule instead of being called by a webhook. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest possible gap, while paid plans can go down to 1 minute between checks. The clock badge on the trigger module is the visual sign of this. If you need a faster reaction, a shorter schedule on a paid plan is the lever, keeping in mind that each check uses operations.
04What if a Sortlist module is missing in Make?
Try Send Universal Request first. Judging by its name, it lets you send your own request to Sortlist through the same connection, which covers cases the other modules skip. Sortlist has no Make an API Call module, so this is the route inside the app. If the request gets too technical or the data you need is unclear, another app in your scenario can sometimes fill the gap, and a Make agency can help you design the flow. Keep in mind that Make's Sortlist documentation is brief and flagged as AI-generated.
05Is Make or n8n better for Sortlist?
It depends on what each tool offers for Sortlist. In Make, you get 6 ready-made modules: 4 scheduled triggers and 2 actions, usable from the Free plan and assembled visually. The same kind of app often has an n8n node as well, so check whether one exists for Sortlist and which operations it covers before deciding. Compare the two on the modules you actually need, not on general reputation. If your scenario only needs to watch opportunities and apply to them, the Make modules already cover that path.
Same platform

Other docs you might need on this stack.

Browse all integrations