Resources · Make integration

Sperse Make integrationAutomate Sperse with Make.

Can Make react to a new lead or payment in Sperse without a line of code? Yes. The Sperse Make integration gives you 3 triggers and 7 actions. This guide shows sales and finance teams how to link the account, build a first scenario and pick the right module.

Try the Sperse integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Sperse Make integration do for you?

The Sperse Make integration links your Sperse account to Make so that leads, payments and subscriptions start automations on their own. You build a scenario, the automation made of modules chained one after another, and Make runs it for you on a schedule, without code.

Keep billing in step with cash. Watch New Payment picks up each payment, and Create an Invoice produces the matching document in Sperse, so nobody rebuilds invoices by hand.

Turn a lead into a clean contact record. Watch New Lead starts the flow, Get a Contact Details reads what Sperse already knows, and Update a Contact fills in the rest when another tool holds better data.

Follow subscriptions closely. Watch Subscription Events brings subscription changes into Make, where you can alert the account owner or feed a report. Add a Subscription and Create a Product cover the other direction, when an offer is sold outside Sperse.

Know the limits before you start. The official documentation for Sperse is thin: the Make docs say there is not enough public information about this app to describe it fully, so modules come without field-by-field notes. Run once is your best guide, and Make an API Call covers what the listed modules leave out. For a wider view of the platform, read our Make review; if you also weigh another automation tool, the n8n vs Make comparison lays out the criteria.

Connect

How do you connect Sperse to Make?

  1. 01

    Add a Sperse module

    In a new scenario, click the +, search for Sperse and pick any module. Make then asks for a connection, which is your Sperse account linked to Make once and reused by every Sperse module. Click Create a connection.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it pays off if you manage more than one Sperse account. A clear name saves you from picking the wrong one in a later scenario.

  3. 03

    Authorize and save

    Depending on what Sperse offers, you either approve Make on a Sperse authorization page or paste the key Sperse gives you. Then click Save. The connection appears in the module and you can start filling it in.

First scenario

Your first scenario: an invoice for every Sperse payment

GoalWhen a new payment is recorded in Sperse, Make creates the matching invoice in Sperse.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor to add its first module.

  2. 02

    Place the trigger

    Search for Sperse, choose Watch New Payment and select your connection, or click Create a connection if this is your first Sperse module.

  3. 03

    Add the invoice

    Click the + on the right of the trigger, pick Create an Invoice and map the payment data into it. Each payment arrives as a bundle, one item passed from module to module.

  4. 04

    Test with Run once

    Click Run once, record a test payment in Sperse if none is waiting, and open the bubbles above each module to read the bundles they received. Fix the mapping here.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default; on paid plans it can go down to 1 minute. Then switch the scenario on.

Triggers

What can start a Sperse scenario?

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

Sperse1Watch New Lead

Watch New Lead

triggerIn the docs only

Watch New Lead brings each new Sperse lead into your scenario, so the rest of your stack hears about a prospect without anyone copying it over. Every lead becomes one bundle that the next modules can use.

How it fires
scheduled. Make checks Sperse on the scenario's schedule, so a lead waits until the next check.
When to use it
when a sales rep should get an alert, or a lead should be copied to another tool, once Make picks it up on the next check.
Watch out
the docs describe no fields, so run it once on a real lead before you build mappings.
Sperse2Watch New Payment

Watch New Payment

triggerIn the docs only

Watch New Payment hands every fresh Sperse payment to Make, which is how accounting, receipts or a sales channel can react to money coming in. Each payment travels as its own bundle.

How it fires
scheduled. Make checks Sperse on the scenario's schedule, not at the moment the payment happens.
When to use it
when a confirmed payment should trigger an invoice, a thank-you message or a line in a finance sheet.
Watch out
every payment consumes operations, the executions Make counts on your plan, in each module that follows.
Sperse3Watch Subscription Events

Watch Subscription Events

triggerIn the docs only

Watch Subscription Events feeds what happens to your Sperse subscriptions into a scenario, so a change on a customer plan never goes unnoticed. The Make docs do not list which events it covers.

How it fires
scheduled. Make checks Sperse on the scenario's schedule and picks up events since the previous check.
When to use it
when an account manager needs a heads-up on subscription changes, or a retention report should stay current.
Watch out
click Run once first and read an event bundle, so you know which events it brings before you map anything.
Modules

What can Make do in Sperse?

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

Sperse1

Add a Contact

ActionIn the docs only

Add a Contact creates a new person in Sperse from data another app collected, so your CRM fills itself instead of waiting for manual entry.

When to use it
after a signup form, a webinar registration or a booking in another tool.
Watch out
if the person may already exist, read the record first with Get a Contact Details to avoid duplicates.
Sperse2

Add a Subscription

ActionIn the docs only

Add a Subscription records a subscription in Sperse from inside a scenario, which keeps recurring revenue tracked in one place even when the sale happened elsewhere.

When to use it
when a customer signs up for a recurring plan through a checkout or form outside Sperse.
Watch out
the docs list no fields, so test with Run once on a test customer before going live.
Sperse3

Create a Product

ActionIn the docs only

Create a Product adds an item to your Sperse catalog without opening Sperse, handy when your offer list is maintained in another tool and should not be typed twice.

When to use it
when a new offer is approved in a spreadsheet or project tool and must be ready to sell in Sperse.
Watch out
run it against a test product first, then check the result in Sperse before you map real data.
Sperse4

Create an Invoice

ActionIn the docs only

Create an Invoice produces an invoice in Sperse from the data of the scenario, so billing follows the event that should cause it instead of a reminder on someone's desk.

When to use it
right after Watch New Payment, or when a deal is marked as won in another sales tool.
Watch out
an invoice is a financial document, so test with Run once on sample data before switching the scenario on.
Sperse5

Get a Contact Details

ActionIn the docs only

Get a Contact Details reads one Sperse contact and passes its data to the next modules, which lets you enrich a message or check a record before changing it.

When to use it
before Update a Contact, or when a message you send from the scenario should use what Sperse knows about the person.
Watch out
it reads a single contact, so you need an identifier from an earlier module to point it at the right person.
Sperse6

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the Sperse API with the connection you already set up, which covers everything the other nine modules do not.

When to use it
when you need a Sperse feature that no listed module offers, and the Sperse API documents it.
Watch out
you write the request yourself, so check what Sperse documents about its API and test each call with Run once.
Sperse7

Update a Contact

ActionIn the docs only

Update a Contact changes an existing Sperse contact with newer data from your scenario, so the record your sales team opens is the right one.

When to use it
when a customer edits their details in a portal or form, or when another tool learns something new about them.
Watch out
map only the fields you want to change, and read the current record with Get a Contact Details if you are unsure.
Need help

Need help automating Sperse with Make?

A person reads every message.

FAQ

Sperse and Make: common questions

01Is the Sperse Make integration free?
Yes, Sperse is a standard app, so it works on the Make 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, Enterprise) lift the interval to 1 minute, allow unlimited active scenarios and count usage in credits, which are operations, per month. Sperse's own pricing is a separate matter.
02What do you need to connect Sperse to Make?
A Sperse account and a Make account are enough to start; the Make documentation lists no other prerequisite. You add any Sperse module, click Create a connection, give it a name if you like, then either approve Make on the Sperse authorization page or paste the key Sperse provides, and save. The same connection is reused by every Sperse module in all your scenarios, so you only do this once per account.
03Do Sperse triggers in Make fire in real time?
Most likely not. The Make docs give no details on the three Sperse triggers, Watch New Lead, Watch New Payment and Watch Subscription Events, but their Watch names point to scheduled triggers: Make checks Sperse on the schedule you set on the first module. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest interval, while paid plans can check as often as every minute. Check the badge on the module in the editor: a clock confirms it.
04What if a Sperse module is missing in Make?
Use Make an API Call. It calls any endpoint of the Sperse API with the connection you already created, so you are not stuck with the ten listed modules. Keep in mind that the Make documentation for Sperse is limited, as the docs themselves say there is not enough public information on the app. Plan to test each call with Run once and to ask Sperse for its API details, since Make gives none.
05Should Sperse users pick Make or n8n?
It depends on your criteria rather than on Sperse alone. In Make, Sperse comes with 10 modules, three scheduled triggers and Make an API Call for the rest, and it runs on the Free plan. n8n often has a node for the same app, so check its catalog for Sperse and compare how each tool fits the rest of your stack, your team's habits and the way you want to maintain scenarios over time.
Same platform

Other docs you might need on this stack.

Browse all integrations