Resources · Make integration

Surense Make integrationAutomate Surense with Make.

Your Surense records can update themselves while you work on something else. The Surense Make integration gives you 39 modules: 32 actions and 7 searches. This page shows how to link your account, build a first scenario and pick the right module.

Try the Surense integration on MakeSee the 39 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Surense Make integration do for you?

The Surense Make integration links your Surense account to Make so that a scenario, the automation you build in Make as a chain of modules, can create, read, update and delete Surense records for you. Each module is one brick of that chain: here, an action or a search on leads, customers, meetings, workflows or reports.

Leads that never sit in an inbox. A form from another app starts the scenario, Create Lead files the person in Surense and Create Activity leaves a trace on the record. Every item that moves from one module to the next is called a bundle: one lead, one contact, one row.

Customer records that stay clean. Search Customers checks whether someone already exists, then Update Customer or Create Customer does the right thing, so account managers stop merging duplicates by hand.

Meetings that close properly. Create Meeting Summary followed by Send Meeting Summary turns the end of a call into a written recap that leaves Surense without anyone copying notes.

What Make does not give you here: Surense has no trigger module, so Surense cannot start a scenario on its own. You start it from a schedule or from another app. Make also flags this app as having limited documentation, so expect to discover fields inside the editor. Every module run counts as one operation, the unit Make bills on your plan; our Make pricing guide explains the plans, and the n8n vs Make comparison helps if you are still choosing a tool. When a scenario misbehaves, Make troubleshooting covers the usual causes.

Connect

How do you connect Surense to Make?

  1. 01

    Add a Surense module

    In your scenario, click the + and search for Surense. Pick any module, for example Search Customers, then click Create a connection. The connection is your Surense account linked to Make once, and every Surense module reuses it.

  2. 02

    Name and authorize it

    Give the connection a name you will recognize later, such as the account it belongs to. Then either authorize Make on the Surense page that opens or paste the key Surense gives you, depending on what the window asks for.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make can now list what it reads from your account, so you pick values from menus instead of typing identifiers. If the lists stay empty, the connection did not go through.

First scenario

Your first scenario with Surense

GoalWhen a new request arrives in another app, Make creates the lead in Surense and logs an activity on it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. Surense has no trigger, so this first bubble belongs to the app where your requests come in.

  2. 02

    Set the starting app

    Search that app by name, pick its trigger and link your account with Create a connection. Fill its fields: Make lists the forms or folders it can read once the connection exists.

  3. 03

    Add Create Lead

    Click the + on the right, search Surense and choose Create Lead. Connect your Surense account, then map the name and contact details coming from the first module into the lead fields.

  4. 04

    Log the activity

    Add Create Activity after it and map the lead returned by the previous module, so the record shows where the request came from.

  5. 05

    Test with Run once

    Click Run once and send a test request. Open the bubble above each module to read the bundles it received, then check the new lead in Surense.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. From now on, each new request becomes a lead without anyone touching it.

Modules

What each Surense module does

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

Surense1

Create Activity

ActionIn the docs only

Create Activity writes an activity into Surense from inside your scenario, so the story of a record builds itself instead of depending on someone remembering to log it.

When to use it
right after another module did something worth tracing, such as a lead arriving from your website form.
Watch out
the doc lists no fields for it, so open the module once and read what it asks before mapping.
Surense2

Create Customer

ActionIn the docs only

Create Customer adds a new customer record to Surense with the details your scenario already holds, which saves a round of retyping after every signed deal.

When to use it
when a contract is marked as signed in another tool and the person needs a proper customer file.
Watch out
run Search Customers first, otherwise the same person can end up with two records.
Surense3

Create Data Proxies Url

ActionIn the docs only

Create Data Proxies Url asks Surense to produce a data proxies URL and hands it to the next module. Make publishes no description of what that URL opens, so treat this one as a module to explore.

When to use it
when your Surense contact has told you that a process needs such a link.
Watch out
click Run once and read the bundle it returns before you send that link anywhere.
Surense4

Create Lead

ActionIn the docs only

Create Lead turns an incoming request into a lead in Surense, so a prospect who fills in a form is in your list before a salesperson even opens their mail.

When to use it
behind a form, a chat or a spreadsheet row that collects prospects in another app.
Watch out
pair it with Search Leads if the same person can submit twice, or your pipeline will count them twice.
Surense5

Create Meeting

ActionIn the docs only

Create Meeting books a meeting in Surense from data that arrives elsewhere, so the appointment shows up in the record without being copied from a calendar by hand.

When to use it
when a prospect picks a slot in a booking tool and you want Surense to know about it too.
Watch out
keep the meeting identifier it returns; Update Meeting and Delete Meetings will need it later.
Surense6

Create Meeting Summary

ActionIn the docs only

Create Meeting Summary stores a written recap for a meeting in Surense, which gives the next person on the file a quick read instead of a vague memory.

When to use it
once notes exist somewhere, for instance typed in a form after the call, and should live next to the meeting.
Watch out
this module records the summary; sending it is the job of Send Meeting Summary.
Surense8

Create Report

ActionIn the docs only

Create Report has Surense generate a report from your scenario, which spares you from rebuilding the same export by clicking through menus.

When to use it
when an event in another app, like a closed file or a manager request, should produce a fresh report.
Watch out
creating the report does not deliver it; chain Send Report if someone should receive it.
Surense9

Create Workflow

ActionIn the docs only

Create Workflow opens a new workflow in Surense, which lets an outside event kick off the internal process your team already follows there.

When to use it
when a new customer or a new request should start the same sequence of tasks every time, without someone launching it manually.
Watch out
the doc says nothing about workflow settings, so build one test workflow and run it once first.
Surense10

Delete Contacts

ActionIn the docs only

Delete Contacts removes contacts from Surense, useful for keeping your address book tidy when people leave or ask to be forgotten.

When to use it
when a removal request arrives through a form and has to reach Surense as well.
Watch out
a deletion does not come back. Put a Search Contacts step before it and test on a dummy contact with Run once.
Surense11

Delete Customers

ActionIn the docs only

Delete Customers erases customer records from Surense, the heaviest clean-up gesture of the whole app.

When to use it
only for a clear case, such as a duplicate you have confirmed or a test record created while you built the scenario.
Watch out
nothing undoes it. Add a filter between Search Customers and this module so only the records you mean can reach it.
Surense12

Delete Employers

ActionIn the docs only

Delete Employers removes employer records from Surense, which keeps the list you pick from short and current.

When to use it
after Search Employers has found an entry that no longer matches any company you work with.
Watch out
check what is still linked to that employer in Surense before you delete it, because the scenario will not ask for confirmation.
Surense13

Delete Leads

ActionIn the docs only

Delete Leads clears leads out of Surense, handy when junk submissions or test entries clutter the pipeline your sales team reads.

When to use it
behind Search Leads, once you have a reliable rule for spotting leads that should go, like a test email address.
Watch out
a search can return several leads at once, and each one becomes a deletion.
Surense14

Delete Meetings

ActionIn the docs only

Delete Meetings takes meetings off Surense, so a cancelled appointment stops showing on the record and nobody prepares for it.

When to use it
when a cancellation in your booking tool should be mirrored in Surense.
Watch out
you need the identifier of the right meeting; store it when Create Meeting runs, rather than guessing it from a date later.
Surense15

Delete Workflows

ActionIn the docs only

Delete Workflows removes workflows from Surense, which is how a scenario can close the loop on a process that was opened by mistake.

When to use it
when a request that started a workflow gets withdrawn in the source app.
Watch out
use Get Workflow to confirm you hold the right one; a wrong identifier means a wrong deletion that cannot be reversed.
Surense16

Download Har Bituach

ActionIn the docs only

Download Har Bituach pulls a Har Bituach item out of Surense so the next module can store or forward it. Make gives no further detail on its content, so see it as a download step to test.

When to use it
when your team already works with Har Bituach data in Surense and wants a copy elsewhere.
Watch out
on the Free plan, files above 5 MB will not pass.
Surense17

Get Customer

ActionIn the docs only

Get Customer fetches one customer record from Surense so later modules can use its details, like writing a personal email or filling a document.

When to use it
when you already hold the customer identifier, for example from an earlier step, and want everything Surense knows about that person.
Watch out
without an identifier, start with Search Customers instead.
Surense18

Get Customer Portfolio History

ActionIn the docs only

Get Customer Portfolio History retrieves the history of a customer's portfolio from Surense, giving an account manager the full picture before a review call.

When to use it
when a meeting is booked and you want that history ready in a document or a message.
Watch out
the doc does not describe what the history contains, so run it once on a real customer and read the bundle first.
Surense19

Get Lead

ActionIn the docs only

Get Lead reads a single lead from Surense and passes its details along, so the rest of your scenario works with current data rather than a stale copy.

When to use it
before updating a lead or notifying a salesperson, when the lead identifier is already in hand.
Watch out
if you only know a name or an email, Search Leads is the module to reach for.
Surense20

Get Meeting

ActionIn the docs only

Get Meeting returns one meeting stored in Surense, including what your scenario needs to prepare a reminder or a follow-up.

When to use it
ahead of Create Meeting Summary, to pull the context of the right meeting.
Watch out
it works on one meeting whose identifier you already know; for a list of meetings, use Search Meetings.
Surense21

Get Workflow

ActionIn the docs only

Get Workflow reads one workflow from Surense, which tells your scenario where a process stands before it decides what to do next.

When to use it
before Update Workflow or Delete Workflows, as a safety check that the identifier points to the process you think.
Watch out
the doc lists no status values, so check the bundle after a Run once before you build a filter on them.
Surense22

Make an API Call

ActionIn the docs only

Make an API Call lets your scenario reach any endpoint of the Surense API with the connection you already set up, which covers whatever the named modules leave out.

When to use it
when you need an operation that no named module offers.
Watch out
you must know the endpoint and its parameters yourself, since Make documents very little about Surense.
Surense23

Search Contacts

SearchIn the docs only

Search Contacts looks through your Surense contacts and returns the ones that match, so your scenario can decide whether to update someone or create them.

When to use it
before Update Contact, to find the right person from an email or a name received elsewhere.
Watch out
a search may return zero, one or several bundles, and each bundle runs the modules that follow.
Surense24

Search Customers

SearchIn the docs only

Search Customers finds existing customers in Surense, which is the guard that stops your automations from creating duplicates.

When to use it
at the start of any flow that could create or change a customer, with a router or filter deciding between Create Customer and Update Customer.
Watch out
when nothing matches, the modules after it do not run at all, so plan that path.
Surense25

Search Customers Having Birthdays Today

SearchIn the docs only

Search Customers Having Birthdays Today returns the customers whose birthday falls on the day the scenario runs, ready for a greeting sent by another app.

When to use it
as the first Surense step of a scenario whose schedule you set yourself, followed by an email or messaging module.
Watch out
if the scenario runs more than once on the same day, customers get the same greeting twice.
Surense26

Search Employers

SearchIn the docs only

Search Employers lists the employers recorded in Surense that match your criteria, so you can attach people to the right company.

When to use it
when an incoming form mentions a company and you want to reuse the existing employer rather than type a new one.
Watch out
spelling variations can hide a match, so test with Run once on a few real company names.
Surense27

Search Leads

SearchIn the docs only

Search Leads scans your Surense leads and returns those that fit, which lets a scenario check for a prospect before acting on them.

When to use it
ahead of Create Lead, so a person who submits a second form updates their lead instead of creating another.
Watch out
several matches mean several bundles, and every following module then runs once per lead.
Surense28

Search Meetings

SearchIn the docs only

Search Meetings brings back the Surense meetings that match what you ask, a starting point for reminders or follow-up messages.

When to use it
when you need all meetings tied to one customer or one period, not a single known meeting.
Watch out
each meeting found costs an operation on every module after it, so keep the search narrow to protect your plan.
Surense29

Search Workflows

SearchIn the docs only

Search Workflows finds the Surense workflows that match your criteria, so your scenario can see which processes are open before it touches them.

When to use it
when a customer calls about a request and you want every related workflow listed for the person handling it.
Watch out
the doc gives no filter list, so open the module to see which criteria it offers.
Surense30

Send Meeting Summary

ActionIn the docs only

Send Meeting Summary sends the recap of a meeting from Surense, so what was agreed leaves Surense as a clear written trace.

When to use it
right after Create Meeting Summary, in the same scenario, once the notes are saved.
Watch out
the doc does not say who receives it or through which channel, so send the first one to yourself with Run once.
Surense31

Send Report

ActionIn the docs only

Send Report dispatches a Surense report from the scenario, which saves someone from downloading and forwarding it by hand.

When to use it
after Create Report, when a manager or a customer should receive the result without logging in.
Watch out
test the recipient on your own address first, since the doc does not describe the delivery settings.
Surense32

Submit Swiftness E9100 Event

ActionIn the docs only

Submit Swiftness E9100 Event sends a Swiftness event of type E9100 through Surense. Make publishes no explanation of that event, so this module mostly serves teams who already use it.

When to use it
when your Surense setup already relies on these events and you want a scenario to submit them.
Watch out
test on a sample record before connecting it to real files.
Surense33

Update Contact

ActionIn the docs only

Update Contact changes an existing contact in Surense, so a new phone number given in a form reaches the record without anyone retyping it.

When to use it
after Search Contacts has found the person, whenever another app holds fresher details.
Watch out
map only the fields you want to change; an empty value mapped by mistake may overwrite good data.
Surense34

Update Customer

ActionIn the docs only

Update Customer edits a customer file in Surense with the data your scenario brings in, keeping the record in line with your other tools.

When to use it
when a customer changes address or email in your billing tool and Surense should follow.
Watch out
you need the customer identifier, so place Search Customers or Get Customer just before it.
Surense35

Update Lead

ActionIn the docs only

Update Lead brings a Surense lead up to date, for instance when a prospect answers a second form or a salesperson qualifies them in another tool.

When to use it
after Search Leads finds an existing lead, instead of creating a duplicate.
Watch out
run it once on a test lead to see which fields it exposes, since the doc does not list them.
Surense36

Update Meeting

ActionIn the docs only

Update Meeting modifies a meeting already stored in Surense, so a rescheduled appointment shows the new details on the record.

When to use it
when a customer moves a slot in your booking tool and Surense should follow without a manual edit.
Watch out
without the meeting identifier kept from Create Meeting, use Search Meetings to find it first.
Surense37

Update Workflow

ActionIn the docs only

Update Workflow changes a Surense workflow from outside, which lets an event in another app move an internal process forward.

When to use it
when a document is signed or a payment clears elsewhere and the matching workflow should reflect it.
Watch out
read the workflow with Get Workflow first, then test the change with Run once on a sample process.
Surense38

Upload Document

ActionIn the docs only

Upload Document places a file into Surense from your scenario, so attachments received by email or through a form land next to the right record.

When to use it
when a customer sends a signed document and it should be filed without anyone downloading it.
Watch out
on the Free plan, Make handles files up to 5 MB, so larger scans need a paid plan.
Surense39

Upload Har Bituah File (deprecated)

ActionIn the docs only

Upload Har Bituah File sends a Har Bituah file to Surense, but Make marks this module as deprecated, which means it is on its way out.

When to use it
only to keep an older scenario running while you plan its replacement.
Watch out
do not build anything new on it; look at Upload Document or Make an API Call for new scenarios.
Need help

Need help automating Surense with Make?

A person reads every message.

FAQ

Questions about Surense and Make

01Is the Surense Make integration free?
Yes. Surense is a standard app in Make, so you can use it on the Free plan. That plan comes with 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 lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run, so a scenario that handles many records consumes more of your monthly allowance.
02What do you need to connect Surense to Make?
A Surense account and a Make account are enough to start. Make's documentation lists no special prerequisite and no official connection steps for Surense, so you follow the generic path: add a Surense module, click Create a connection, give it a name, authorize Make on the Surense page or paste the key Surense provides, then click Save. Once saved, the same connection serves all 39 modules. If you do not know where to find a key, ask whoever administers Surense in your company.
03Can Surense start a Make scenario automatically?
Not by itself. Surense has no trigger module in Make, so nothing in Surense can launch a scenario. You have two ways around that. The first is a schedule: the clock on the first module runs the scenario every 15 minutes by default, and a search such as Search Leads can open the flow. The second is to start from another app's trigger, a form or an email for instance, and use Surense modules as the following steps.
04What if the Surense module you need is missing?
Use Make an API Call. It reaches any endpoint of the Surense API with the connection you already created, so it covers what the named modules do not. The catch is documentation: Make states that it has limited information on Surense, so you need the endpoint details from Surense itself. If a module you use is marked deprecated, such as Upload Har Bituah File, plan a move to another module or to an API call before it disappears.
05Should you use Make or n8n for Surense?
It depends on the tool your team already runs. On Make, Surense comes with 39 ready modules covering leads, customers, meetings, workflows and reports, plus an API call for the rest, and this page walks through each of them. The same app often has an n8n node as well, so check it before deciding. Compare the two on what matters for your case: which actions you need, who maintains the scenarios and which editor your team finds easier to read.
Same platform

Other docs you might need on this stack.

Browse all integrations