Resources · Make integration

Sensorpro Make integrationAutomate Sensorpro with Make.

Tired of copying contacts into Sensorpro by hand? The Sensorpro Make integration gives you 6 modules, all built around contacts: 5 actions and 1 search. This guide shows marketers how to connect the account and run a first scenario, step by step.

Try the Sensorpro integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Sensorpro Make integration do for you?

It lets Make, a visual automation tool, read and write your Sensorpro contacts without code. You build a scenario, the automation itself, from modules: small bricks that each do one job, like adding a contact or looking one up. Sensorpro offers no trigger in Make, so another app or a schedule starts the flow.

New leads land in Sensorpro on their own. Put a form or CRM trigger from another app first, then Create a Contact copies each person into your audience. Nobody retypes an email address again.

Profiles stay current. When a customer changes details in your billing or support tool, Get a Contact finds the matching record and Update a Contact writes the new values over the old ones.

Clean-up follows the rules you set. List Contacts pulls a set of records, and Delete a Contact removes the ones that should go, for example after an unsubscribe request handled elsewhere.

Be aware of one gap: Make's own documentation for Sensorpro is limited, so the page cannot promise field names. You discover them inside each module once the connection works. If a listed module falls short, Make an API Call reaches the rest of the API. Sensorpro may also exist as an n8n node; our n8n vs Make page lays out how the two tools differ. To judge the tool first, read the Make review, or check plan limits on Make pricing.

Connect

How do you connect Sensorpro to Make?

  1. 01

    Add a Sensorpro module

    In a scenario, click the +, type Sensorpro, and pick any module. The connection, meaning your Sensorpro account linked to Make once, gets created from the first module and every other Sensorpro module reuses it.

  2. 02

    Create and name the connection

    Click Create a connection. You can give it a name, which helps when a client account and a test account sit side by side. The name only matters to you, so pick something you will recognize.

  3. 03

    Authorize and save

    Either approve access on the Sensorpro page that opens, or paste the key Sensorpro gives you, depending on what the window asks for. Then click Save. The module can now read your account.

First scenario

Your first scenario: add new leads to Sensorpro

GoalWhen another app records a new lead, Make adds that person to Sensorpro as a contact.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario, and click the +. Add the trigger of the app where leads come in, such as your form tool, and connect that account.

  2. 02

    Add Create a Contact

    Click the + to the right of the first module, search Sensorpro, and choose Create a Contact. Create the connection when Make asks for it.

  3. 03

    Map the lead's data

    Fill the module fields by picking values from the first module: its output shows up as items you can click. Each bundle, one lead passing through, becomes one contact.

  4. 04

    Test with Run once

    Click Run once, send a test entry from the other app, and open the bubble above each module to read the bundle it received. Check the new contact in Sensorpro.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (a new scenario checks every 15 minutes by default) and turn the scenario on. From now on each new lead reaches Sensorpro without you.

Modules

What each Sensorpro module does

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

Sensorpro1

Create a Contact

Action

In Make“Creates a new contact.”

You get a fresh Sensorpro contact built from data another app already holds, so your audience grows without typing. It is the module most scenarios end on.

When to use it
a lead signs up through a form, a webinar tool or a shop, and should appear in Sensorpro right after.
Watch out
it always adds a record; to avoid a double, look the person up first and send known people to Update a Contact.
Sensorpro2

Delete a Contact

Action

In Make“Deletes a specific contact.”

This one removes a specific contact from Sensorpro, which keeps your audience in line with decisions made in other tools. Pair it with a lookup so the right record is targeted.

When to use it
a customer asks for their data to be erased in your support desk, and Sensorpro must follow.
Watch out
a deleted contact is gone from your audience, so test it on a dummy contact with Run once before switching the scenario on.
Sensorpro3

Get a Contact

Action

In Make“Returns a specific contact.”

Hand it one contact and it returns that person's full record, ready for the next module to use. Think of it as opening one profile card rather than browsing the whole list.

When to use it
before an update or a decision, when you need to see what Sensorpro currently stores about one person.
Watch out
it is an action on a single item; when you do not yet know which contact you need, List Contacts is the better start.
Sensorpro4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Here you reach any part of the Sensorpro API the other five modules leave out, using the same connection. It fills gaps instead of forcing you to change tool.

When to use it
you need something Sensorpro can do that no listed module covers, and you can read the Sensorpro API reference.
Watch out
you write the request yourself here; keep it for cases the listed modules cannot handle.
Sensorpro5

Update a Contact

Action

In Make“Updates an existing contact.”

Changes made elsewhere land on an existing Sensorpro contact, so the profile matches your other systems. Only the record you point at is touched.

When to use it
a customer edits their details in your billing or CRM tool, and Sensorpro should carry the same values.
Watch out
the module needs to know which contact to change; place Get a Contact or List Contacts before it to find the right one.
Sensorpro6

List Contacts

Search

In Make“Returns array of contacts.”

Out comes a set of Sensorpro contacts, each one sent on as its own bundle, so the next modules can work through them one by one. It is the search of this app.

When to use it
you want to check, export or clean a group of records rather than a single person.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle, which counts operations on your plan.
Need help

Need help automating Sensorpro with Make?

A person reads every message.

FAQ

Sensorpro and Make: common questions

01Is the Sensorpro Make integration free?
Yes, Sensorpro is a standard app in Make, so you can use it on the Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the minimum interval to 1 minute and allow unlimited active scenarios. Make counts usage in operations, one per module run on one bundle, so a List Contacts step that returns many records uses more of your plan. Your Sensorpro subscription is a separate matter this page does not cover.
02What do you need to connect Sensorpro to Make?
A Sensorpro account and a Make account. Make's documentation lists no special prerequisite for this app. Add any Sensorpro module, click Create a connection, give it a name if you like, then either authorize Make on the Sensorpro page or paste the key Sensorpro provides, and click Save. The same connection then serves all six Sensorpro modules, so the setup happens once. Because the official documentation for Sensorpro is limited, keep your Sensorpro account settings open in case the window asks for a key.
03Does Sensorpro trigger Make scenarios in real time?
No, because Sensorpro has no trigger module in Make: nothing in Sensorpro can start a scenario by itself. You start the flow another way. Either put a trigger from another app first, such as a new form entry or a new CRM record, or let the scenario run on a schedule and begin with List Contacts. Scheduled scenarios run every 15 minutes by default, with a minimum of 15 minutes on the Free plan and 1 minute on paid plans. The Sensorpro modules then act on whatever that first step hands them.
04What if the Sensorpro module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Sensorpro API with the connection you already set up, so you can reach features the five contact modules do not cover. You write the request yourself from the Sensorpro API reference. Also keep in mind that Make's documentation for Sensorpro is limited, so the exact fields of each module are visible only inside the editor once the connection works. When something fails, the Make troubleshooting guide on this site walks through common errors.
05Should you use Make or n8n for Sensorpro?
It depends on how you like to work, since both tools can often automate the same app. On Make, Sensorpro comes with six modules focused on contacts, one connection shared by all of them, and a visual editor where Run once shows each bundle as it passes. Sensorpro may also be available as an n8n node. Compare what each tool offers for your exact use: which contact actions you need, how you want scenarios to start, and which plan limits fit. The n8n vs Make comparison linked above explains the differences between the two tools in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations