Pulseem

Pulseem is an Israeli multi-channel messaging platform for transactional email, SMS and WhatsApp Business. Agents send messages across all three channels, manage suppression lists, and administer reseller sub-accounts.

19 actions API key available

Pulseem website Platform Documentation Capability data verified 2026-08-19

A scheduled sweep runs against the last hour of inbound replies

Get Incoming SMS Report and Get Incoming WhatsApp return what people sent back

Get Client Status reads the current contactability of every number in the reply set

Agent separates opt-out language from ordinary replies and from support questions

Change Client Status suppresses the numbers that clearly asked to stop

The ambiguous replies post to the messaging owner with the exact object the agent would send

The owner approves or rejects each proposed re-enable before any number goes back on the list

What This Integration Enables

Pulseem is built for teams that send to Israeli audiences across email, SMS and WhatsApp Business from one account, and its API makes an assumption most messaging platforms do not: recipients and content are parallel arrays matched by position. Recipient one gets subject one and body one. FlowRunner agents work with that shape rather than around it, sending either a single value used for everybody or exactly one value per recipient, so a personalized send cannot quietly hand the wrong body to the wrong person. Agents also read the per message and summary reports, poll the inbound SMS and WhatsApp reports, submit WhatsApp templates for Meta approval and check their status, and administer reseller sub accounts and credit balances.

The part worth building carefully is the contactability surface. Get Client Status, Change Client Status and Get Removed Clients are consent data, and Pulseem types the write as a bare object without publishing its shape. That is exactly the kind of operation FlowRunner's human-in-the-loop design exists for: the agent can read, classify and propose at machine speed, and the write that decides who may be contacted waits for a person who can see what is about to be sent.

Without FlowRunner

Replies land nowhere Inbound texts sit in a report nobody opens, so opt-outs are found weeks later

Suppression by spreadsheet The do-not-contact list lives in an export that drifts from the platform that enforces it

Content matched by hand Personalized sends are assembled in a spreadsheet where one shifted row shifts everyone

With FlowRunner

Replies read on a schedule The inbound reports are polled continuously and classified before the next send goes out

Suppression reconciled at the source The agent reads contactability from Pulseem itself and writes back to the same place

Alignment enforced before the call The recipient list and its content arrays are length checked before anything leaves

Use Case Scenarios

Transactional sends that stay aligned

An order confirmation or appointment reminder arrives from the system of record, perhaps Shopify or a scheduling tool. The agent builds one Recipients list and one matching set of Subjects, Bodies and References, then calls Send Email or Send SMS. Because the counts are checked before the request leaves, a template that produced four bodies for five recipients is refused rather than delivered scrambled. Afterward the agent calls Get Email Report or Get SMS Report against the External Reference it set at send time, and writes delivery state back to the order record so support can answer without opening a second tool.
Keeping a WhatsApp template ready before the window closes

WhatsApp only allows a free form message inside an open twenty four hour conversation window, and outside it an approved template is the only option. The agent calls Get Incoming WhatsApp to see whether a recipient's window is still open. If it is, Send WhatsApp Chat carries the reply. If it is not, the agent checks Get WhatsApp Template Status and sends with Send WhatsApp Template instead. New wording goes through Submit WhatsApp Template well ahead of a campaign, because approval belongs to Meta rather than to Pulseem and can come back rejected. A digest of pending and rejected templates posts to Slack so the marketing owner is never surprised by a template that cannot ship.
Reconciling suppression before an import

Before a contact list is imported into another platform, a reconciliation flow calls Get Removed Clients for the period and Get Client Status for the addresses and numbers in the incoming file. Anything Pulseem has already removed from contact is stripped from the import rather than carried in with it, and the result is written to a sheet in Google Sheets alongside the reason. The agent never widens the contactable set on its own. Everything it does here narrows it.

Human-in-Loop Highlight

Change Client Status is the operation this page's gate exists for, and the direction matters. Suppressing a number after somebody replies with stop language is a narrowing write the agent can own. Putting a number back on the contactable list is not, for two reasons that are specific to this API. The first is consequence: a re-enabled number receives real messages, and a message cannot be recalled. The second is shape. Pulseem types both fields of this operation as a bare object and does not publish their structure, so a wrong payload can be accepted silently rather than refused. The agent therefore reads the exact shape its own account returns from Get Client Status, builds the proposed write to mirror it, and posts the literal object alongside the reply that prompted it: "This number replied with a question rather than a stop, and Get Removed Clients shows it was suppressed on the fourteenth. Re-enable it? Here is exactly what I would send." A person answers. Only then does the write happen.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

19 actions

Email

Send Email Sends email to a recipient list, with subjects, bodies, names and references supplied either as one value for everybody or as exactly one value per recipient. The alignment check happens before the request leaves.
Get Email Report Reads the per message email report. Both the Send ID and the External Reference are values the flow set at send time, so a workflow that wants to find its own messages later has to have set one.
Get Email Report Summary Reads the same email report aggregated into totals. The cheaper call when a flow only needs counts rather than per message detail.

SMS

Send SMS Sends text messages, with texts and references lined up against the recipient list by position. The Callback URL for delivery reports is set per send rather than per account.
Get SMS Report Reads the outgoing SMS report for a period or a specific send.
Get Incoming SMS Report Reads text messages people sent in, which is how replies and keyword opt-ins arrive. There is no webhook for these, so a flow that reacts to replies polls this on a schedule.

Send WhatsApp Chat Sends a free form WhatsApp message, which the platform allows only inside an open twenty four hour conversation window. Unlike the email and SMS sends, this one carries a single text for the whole recipient list.
Send WhatsApp Template Sends an approved template message, which is the only kind allowed once the conversation window has closed. Variables fill the template placeholders in order.
Submit WhatsApp Template Submits a template for approval. Approval belongs to Meta rather than to Pulseem, takes time, and can be rejected, so campaign flows submit well ahead of the send date.
Get WhatsApp Template Status Lists templates and where each one stands: Pending, Received, Approved or Rejected. Only an Approved template can be sent.
Delete WhatsApp Template Deletes a template. Any send referencing it begins failing, and a replacement has to go back through Meta's approval.
Get WhatsApp Report Reads the outgoing WhatsApp report.
Get Incoming WhatsApp Reads inbound WhatsApp messages. This is also what tells a flow whether a recipient's conversation window is still open, which decides whether a free form message can be sent at all.

Contactability

Get Client Status Reads whether given addresses and numbers are still contactable. The suppression check to run before any send, and the way to learn the payload shape this account returns.
Change Client Status Changes whether addresses and numbers may be contacted. This is consent data, and the operation this page's human gate is built on.
Get Removed Clients Lists the addresses and numbers removed from contact in a period. The list to reconcile against before importing contacts anywhere else.

Account and Credits

Get Credit Balance Reads remaining sending credit. Leaving the sub account name empty reads the account the key belongs to; naming one reads that sub account instead.
Create Sub Account Creates a reseller sub account with login credentials chosen by the caller, optionally moving credits into it. The password supplied here becomes a real account password.
Transfer Credits Moves sending credit between accounts. The target is named by its API key rather than by name, so this operation takes a second account's secret as an ordinary parameter, and credits leave the source balance immediately.

Frequently Asked Questions

What can FlowRunner do with Pulseem?

FlowRunner agents can run Send Email, Get Email Report, and Get Email Report Summary in Pulseem, plus 16 more actions.

Does connecting Pulseem to FlowRunner require OAuth?

No. Pulseem connects to FlowRunner with an API key, no OAuth flow required.

Can Pulseem trigger a FlowRunner workflow automatically?

Pulseem doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Pulseem

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us