Resources · Make integration

Pulseem Make integrationAutomate Pulseem with Make.

Can Make send your Pulseem emails, texts and WhatsApp messages for you? The Pulseem Make integration gives you 16 modules, 14 actions and 2 searches, with no trigger of its own. This guide walks a Pulseem user through the connection and a first working scenario.

Try the Pulseem integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Pulseem Make integration do for you?

The Pulseem Make integration links your Pulseem account to Make, so a scenario (the automation you build, a chain of modules) can add recipients, send email, SMS or WhatsApp messages and read your campaign reports without code. Each module is one brick of that chain: here, an action or a search on Pulseem.

Every new lead gets a text. A form or a shop captures a contact, Add Or Update Recipient files it in Pulseem, and Send SMS greets that person right after. The recipient list stays clean because the same module updates a contact it already knows instead of creating a copy.

Reports land where your team reads them. Get Email Report, Get SMS Report and Get WhatsApp Report fetch the results of a send, which you can then write to a sheet or a CRM, one channel at a time.

Status changes follow your other tools. When a customer asks to stop hearing from you in your helpdesk, Change Recipient Status updates the same person in Pulseem, and Get Recipient Status lets a scenario check first.

Two limits to know. Pulseem has no trigger in Make, so a scenario starts from another app or from a schedule. And Make itself flags its Pulseem documentation as limited, so the fields of each module only show up once your connection exists, and what this page says about each module is read from its name. If you are new to the editor, Make training covers the basics, and Make troubleshooting helps when a run fails. Pulseem may also have an n8n node; n8n vs Make lays out how the two tools differ.

Connect

How do you connect your Pulseem account to Make?

  1. 01

    Open the connection window

    Add any Pulseem module to a scenario and click Create a connection. A connection is your Pulseem account linked to Make once; every Pulseem module of every scenario then reuses it, so you only do this step one time.

  2. 02

    Name it, then authorize

    Give the connection a name if you like, handy when you manage several Pulseem accounts. Then either authorize Make on the Pulseem page that opens, or paste the key Pulseem 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 read your Pulseem account and show the fields and lists it offers. If the fields appear, the connection works and you can carry on building.

First scenario

Your first scenario: welcome every new contact by SMS

GoalWhen a new contact shows up in another app, Make saves it in Pulseem and sends it a welcome SMS.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where new contacts arrive, such as your form tool or your shop, and choose its trigger.

  2. 02

    Add Add Or Update Recipient

    Click the + on the right of that first module, search Pulseem and pick Add Or Update Recipient. Create the connection, then map the contact details coming from the first module.

  3. 03

    Add Send SMS

    Click the + again, choose Send SMS and reuse the same connection. Map the contact from the previous modules and write the welcome text the new recipient will read.

  4. 04

    Test with Run once

    Click Run once with a test contact of your own. Make runs the scenario one time and shows the bundles each module received, a bundle being one item passed along, here one contact.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What each Pulseem module does

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

Pulseem1

Add Client Product

ActionIn the docs only

Its name points to one job: attaching a product to a client record in Pulseem, so your segments can reflect what each customer bought.

When to use it
right after an order is paid in your shop, to tag the buyer with the product before a follow up campaign.
Watch out
Make publishes no field list for it, so run it once on a test client and check what Pulseem stored.
Pulseem2

Add Groups

ActionIn the docs only

This one creates groups in your Pulseem account, the lists you later target with a send, without opening Pulseem by hand.

When to use it
a new event or product launch needs its own audience, and you want the group ready before contacts start flowing in.
Watch out
run List Groups first if you are unsure, since adding a group that already exists may leave you with two lists of the same name.
Pulseem3

Add Or Update Recipient

ActionIn the docs only

You get one clean record per person: as the name says, the module adds a recipient to Pulseem, or updates it when the contact is already there.

When to use it
any time contacts arrive from a form, a CRM or a checkout and you do not want to track who is new and who is known.
Watch out
map the same identifying detail every time, otherwise Pulseem cannot recognize an existing recipient and creates a new one.
Pulseem4

Change Recipient Status

ActionIn the docs only

Keeps Pulseem in step with decisions taken elsewhere by switching the status of a recipient from inside a scenario.

When to use it
a customer asks your support team to stop receiving messages, and Pulseem should reflect it without anyone copying the change by hand.
Watch out
the statuses you can pick are listed only once the connection exists; test on your own address before touching real customers.
Pulseem5

Get Email Report

ActionIn the docs only

Brings the results of a Pulseem email send back into Make, where the next module can store or share them.

When to use it
your team reads performance in a spreadsheet or a dashboard and wants email figures there next to other channels, without exporting them by hand.
Watch out
the report content is not documented, so look at the bundle after Run once before you map anything.
Pulseem6

Get Incoming SMS Report

ActionIn the docs only

Unlike the other SMS module, this one is about replies: it fetches the report of text messages your Pulseem account received.

When to use it
customers answer your SMS campaigns and those answers should reach a helpdesk, a CRM note or a shared inbox.
Watch out
check in the Run once output how replies are grouped, one bundle each or one report, before you add a module that acts on every reply.
Pulseem7

Get Recipient Status

ActionIn the docs only

Tells your scenario where a recipient stands in Pulseem before anything is sent, so the next modules can decide what to do.

When to use it
place it just before Send Email or Send SMS and add a filter so people who opted out are skipped.
Watch out
checking a long list means one operation per contact on your plan.
Pulseem8

Get SMS Report

ActionIn the docs only

Pulls the outcome of an outgoing SMS send from Pulseem, the text counterpart of Get Email Report.

When to use it
you want delivery results of a text campaign written to a sheet or posted to your team chat once the send is done.
Watch out
Make lists no fields for this report; run the module on a real send and read the bundle to see what you can map.
Pulseem9

Get WhatsApp Report

ActionIn the docs only

Fetches the results of your WhatsApp sends from Pulseem, completing the reporting trio with email and SMS.

When to use it
WhatsApp has become a main channel for your customers and its numbers belong in the same report as the rest of your campaigns.
Watch out
compare its output with the email and SMS reports after Run once, as the three may not return the same structure.
Pulseem10

List Client Data

SearchIn the docs only

A search module: it returns client data from Pulseem as zero, one or several bundles, one per item found.

When to use it
you need to copy Pulseem contacts into a CRM or a sheet, or look up a client before updating it.
Watch out
every bundle it returns runs the next modules once, so a large result multiplies the operations counted on your plan.
Pulseem11

List Groups

SearchIn the docs only

Gives you every group of your Pulseem account as separate bundles, the second of the two searches in this app.

When to use it
before Add Groups, to avoid duplicates, or to mirror your Pulseem lists in another tool your team uses.
Watch out
an empty result stops the modules after it for that run, so test with an account that already holds at least one group.
Pulseem12

Make an API Call

ActionIn the docs only

Your way out when the 15 other modules fall short: it calls any endpoint of the Pulseem API with the connection you already set up.

When to use it
you need a Pulseem feature no listed module covers and you have the API reference of Pulseem at hand.
Watch out
Make gives no Pulseem API guide, so the path and body come from Pulseem itself; test with Run once on harmless data.
Pulseem13

Send Email

ActionIn the docs only

Sends an email through your Pulseem account from a scenario, triggered by whatever happened in the app before it, so the customer hears from you without anyone typing it.

When to use it
a quote is signed, an order ships or a form is filed, and the customer should get an email through Pulseem right away.
Watch out
Run once really sends the message, so point your test at your own address first.
Pulseem14

Send SMS

ActionIn the docs only

Puts a text message on its way from Pulseem the moment the scenario reaches this module, short and hard to miss.

When to use it
an appointment is booked or a delivery changes, and a quick text beats an email that may sit unread.
Watch out
each run sends a real SMS; add a filter before it so a test or a duplicate bundle does not text a customer twice.
Pulseem15

Send Template WhatsApp Message

ActionIn the docs only

Judging by its name, this module sends a WhatsApp message built on a template from your Pulseem account, rather than free text.

When to use it
the message follows a fixed pattern, an order confirmation or a reminder, and only details like the name change.
Watch out
the templates on offer come from your Pulseem account, so create them there before building the scenario.
Pulseem16

Send WhatsApp Chat

ActionIn the docs only

For free text on WhatsApp: the module sends a chat message written in the scenario, next to its template counterpart.

When to use it
a conversation is already going with the customer and a tailored answer fits better than a template.
Watch out
Make does not document when free chat is allowed rather than a template; check the error in the Run once output if a message is refused.
Need help

Need help automating Pulseem with Make?

A person reads every message.

FAQ

Pulseem and Make: common questions

01Is the Pulseem Make integration free?
Yes, Pulseem is a standard app, so you can use it on the Free plan of Make. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in credits per month. Your Pulseem subscription is a separate matter that Make does not cover.
02What do you need to connect Pulseem to Make?
A Pulseem account and a Make account are enough to start, as the Make documentation lists no other prerequisite. You add a Pulseem module, click Create a connection, name it if you wish, then authorize Make on the Pulseem page or paste the key Pulseem gives you, and save. Make flags its Pulseem documentation as limited, so if a key is requested, get it from your Pulseem account first. One connection then serves every Pulseem module in all your scenarios.
03Does the Pulseem Make integration react in real time?
Not on its own, because Pulseem has no trigger in Make. A scenario must start elsewhere. The first option is a schedule: Make runs the scenario at the interval set on the first module, every 15 minutes by default, down to 1 minute on paid plans. The second is an instant trigger from another app, which calls Make through a webhook as soon as something happens there, a new form entry for example. Pulseem modules then act right after that trigger in the same run.
04What if a Pulseem module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Pulseem API with the connection you already have, so you are not limited to the 14 actions and 2 searches listed. Keep in mind that Make describes its own Pulseem documentation as limited, which means the endpoints and their parameters must come from the Pulseem side. Test each call with Run once on a harmless record before it touches real contacts, and read the returned bundle to see what you can map.
05Should you use Make or n8n for Pulseem?
It depends on your criteria rather than on a winner. In Make, Pulseem comes with 16 modules covering recipients, groups, sends on three channels and reports, plus Make an API Call for the rest. The same app often has an n8n node too, so check what that node offers for the tasks you have in mind. Compare the modules each tool lists for your exact use, the editor your team is comfortable with, and how each tool counts usage on its plans.
Same platform

Other docs you might need on this stack.

Browse all integrations