SendPulse Make integrationAutomate SendPulse with Make.

Switching one website subscriber on or off from Make keeps your SendPulse website audience in line with what happens elsewhere. You point to the subscriber by ID and choose the new state.

Push campaigns can be launched straight from a scenario with this action, so a message goes out when something happens rather than when someone remembers. The content can come from any earlier module.

Your HTML becomes a reusable SendPulse template with this action, ready for later sends. It saves you pasting code into the SendPulse editor each time a design changes.

One contact gets saved in SendPulse whether it is new or already there: the action creates it or updates it. That spares you a separate search step for most sign-up flows.

Adding people to a mailing list, or refreshing those already in it, is what this action handles. It writes into the list you pick, which keeps your segments tidy.

Pulling the details of one campaign by its ID lets you reuse them further down the scenario, for a report or a message to the team.

Information about one of your SendPulse websites comes back with this action, found by its Website ID. Handy when one scenario serves several sites and has to know which one it is handling right now.

A phone number is often the only thing you have about a WhatsApp contact; this module turns it into the matching SendPulse contact, ready for the next steps.

Anything the SendPulse API offers but the listed modules miss can still be reached here, with the connection you already set up. It is the escape hatch of the integration.

A chatbot flow you built in SendPulse can be started for a given contact from a scenario, so the conversation begins at the right moment instead of waiting for the person to write.

A text campaign reaches every subscriber of the bot you choose when this action runs. Use it for news that concerns the whole bot audience at once.

Here the email is written inside the scenario, subject and body mapped from earlier modules, and SendPulse delivers it. Good for messages that change every time.

Reusing a template you already keep in SendPulse, this action sends a consistent email without rebuilding the design in Make. The marketing team edits the template, the scenario keeps working.

With this action, one of your SendPulse Instagram bots writes a free message to a chosen contact. It lets a scenario answer on Instagram with data from any other app.

A plain text message goes to one chatbot contact you specify. It is the simplest way to reach a single person through a SendPulse bot from Make.

Only a phone number in hand? Your WhatsApp bot can still message that person, since this action addresses the number directly instead of a contact ID.

A WhatsApp template message, sent by your bot to a contact picked by ID, is what this action delivers. Templates keep the wording you prepared, which suits recurring notices.

Storing a value on a bot contact, such as a plan name or a last order, makes it available to your SendPulse flows later. The contact is picked by ID.

Tags on a bot contact are how SendPulse sorts people, and this action assigns them from Make, contact picked by ID. Your segments then follow what happens in other tools.

Removing someone from a mailing list happens here, so a request made anywhere, a form, a support ticket, is honored in SendPulse too.

A single address gets checked by SendPulse before you rely on it. Placed early in a scenario, it keeps doubtful addresses out of your lists.

Looking up a contact by email returns what SendPulse knows about that person, ready to use in later modules. As a search, it can return zero, one or several bundles.

The bounces from the last 24 hours come back as a list, each address its own bundle. It is a quick way to see which emails did not arrive.

Your campaigns come back one bundle each, which lets a scenario loop over them or pick the one it needs.

Every contact of a mailing list, found by its List ID, flows out of this search as separate bundles. Handy to copy a list to another tool.

For a chosen bot, this search returns every contact carrying a given tag. It turns a SendPulse segment into items a scenario can act on.

Pick a bot and a variable ID, and this search returns every contact of that bot sharing the variable. In practice, it reads back what Set a Variable to a Contact stored earlier, so your segments built in Make become usable lists.

The subscriptions of your SendPulse websites come back one bundle each, so you can inspect or sync them elsewhere.

Starting from an email address, this search finds the matching bot contact in SendPulse. Use it when email is the key your other tools share.

Contacts get matched on the value of a variable with this search, not on their email. Useful when your own customer ID or plan is stored as a variable.