Rav Messer
Email MarketingRav Messer, sold in English as Responder, is an Israeli email and SMS marketing platform. Agents manage lists and subscribers, personal fields and tags, maintain both suppression lists, and register webhooks for subscriber events.
What This Integration Enables
Rav Messer, sold in English as Responder, is an Israeli email and SMS marketing platform, and the most interesting thing about its API is what it refuses to combine. A subscriber carries two separate consent flags, one for email and one for SMS, and setting one does not set the other. The account carries two separate suppression lists, one of addresses and one of phone numbers, and suppressing somebody's address does not suppress their number. That is not an oversight. Somebody who asked you to stop texting has not necessarily asked you to stop mailing, and a platform that collapses the two either over-suppresses a channel the person was happy with or under-suppresses one they were not.
FlowRunner agents work with that grain rather than against it. They manage lists and subscribers, resolve the account's personal fields once and reuse the numeric IDs those fields are keyed by, apply and read tags across the three separate namespaces the platform keeps for lists, subscribers and messages, and write to both suppression lists. Tags are a good example of why an agent helps here: a single read returns list, subscriber and message tags mixed together, and picking the right kind out of that answer is exactly the sort of mechanical care a flow does reliably and a person does not.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
One signup, two consents, recorded honestly
A form submission carries an address, a phone number and two separate checkboxes. The agent calls Create Subscriber onto the right list, and writes the two consent decisions independently rather than treating one tick as permission for both. It resolves the account's personal fields with Get Personal Fields first, so the values land on the numeric field IDs the platform expects, and a date field goes in as the day, month and year object the API asks for rather than as a string that would be rejected. The record in HubSpot gets the same two flags so the two systems cannot drift.
-
Suppression that survives the next import
Every import is a chance to re-add somebody who asked to leave. Before a new file is written, the agent reads Get Unwanted Emails and Get Unwanted Phones and removes matching rows from the incoming set, so the suppression lists act as a gate on the write rather than a cleanup afterward. Bounces and complaints collected elsewhere are pushed the other way: the agent calls Add Unwanted Email for confirmed hard bounces, which stops all mail to that address regardless of which list it sits on. The reconciliation posts to Slack.
-
A support conversation that ends in the right operation
A customer writes in through Zendesk and asks to be removed. The agent reads the ticket, resolves the subscriber, and then chooses between three operations that look alike and are not. Remove Subscriber From List takes them off one list and leaves them on the account. Unsubscribe marks them unsubscribed. Delete Subscriber removes them from the account entirely. Which one is correct depends on what the person actually asked for, so the agent proposes one, quotes the sentence it based the proposal on, and waits. FlowRunner's human-in-the-loop step is what makes that pause a designed part of the flow rather than a failure in it.
Human-in-Loop Highlight
A reply comes back to a text message: "please stop." The agent can act on that with complete confidence in one channel. It calls Add Unwanted Phone, the number goes onto the phone suppression list, and no further SMS reaches it. What it cannot do is decide whether the sentence also covers email, because Rav Messer deliberately keeps that as a separate promise on a separate list, and nothing in the message resolves it. Guessing wide silently ends a channel the customer may value, and guessing narrow keeps mailing somebody who thinks they told you to stop. So the agent does the unambiguous half and posts the rest: "Number ending 4417 suppressed after an SMS stop request. The same subscriber is opted in to email and opened three of the last four campaigns. Their message read 'please stop.' Suppress the address as well, or leave email consent in place?" A person answers, and the answer gets recorded on the list it belongs to. The channel the customer named is closed immediately. The channel they did not name waits for someone who can read intent.
Agent Capabilities
36 actionsAccount
1- Get Account Reads the account the credentials belong to. The cheapest way to confirm all three credential parts are accepted, because it exercises the token exchange as well as the call.
Lists
8- Get Lists Lists the account's subscriber lists.
- Get List Reads one list.
- Create List Creates a subscriber list. The double opt in setting decides whether joiners must confirm and cannot be assumed, because a list created without it subscribes people immediately. The sender setting picks which verified sender the list mails from, and the notifications object requires its three parts together.
- Get List Fields Reads a list's own fields together with every account wide personal field. That combination is the point, because the list-only read returns a different answer.
- Get List Personal Fields Reads only the personal fields belonging to one list.
- Get List Subscribers Lists the subscribers of one list.
- Update List Subscriber Changes a subscriber's membership of one list: whether they are inactive or pending there, and when they joined. This does not touch the subscriber record itself.
- Remove Subscriber From List Takes a subscriber off one list. The subscriber stays in the account; Delete Subscriber is what removes them entirely.
Subscribers
8- Create Subscriber Creates a subscriber on one or more lists. An override option updates an existing subscriber rather than failing, and a rejoin option resets their join date; without either, an existing address is left as it stands. Personal fields are keyed by field ID and a date field takes a day, month and year object. Tags may be given as IDs or as names, in two different fields.
- Get Subscriber Reads one subscriber by ID or by email address. The same path segment takes either, so a numeric looking address would be read as an ID.
- Search Subscribers Searches one list for a keyword. All four parameters are required by the vendor, offset and size included, so there is no unpaged form of this call.
- Update Subscriber Changes a subscriber. Email consent and SMS consent are separate fields here and setting one does not set the other. The personal fields on this route are the ones associated with every list on the account.
- Delete Subscriber Removes a subscriber from the account entirely, not from one list. Remove Subscriber From List is the narrower call.
- Remove Subscriber Tag Takes one tag off one subscriber.
- Subscribe Marks a subscriber as subscribed again. The vendor publishes no body schema for this route, only the prose that it takes the subscriber's email, phone or ID, so this action sends whichever is given and exposes a hatch for anything else.
- Unsubscribe Unsubscribes a subscriber. As with Subscribe, the vendor publishes no body schema and documents only that it takes an email, a phone or a subscriber ID.
Personal Fields
3- Get Personal Fields Reads the account's personal fields. This is where the numeric field IDs come from that the subscriber write routes key their values by, and where a select field's option IDs come from.
- Create Personal Field Creates a personal field, either on the whole account or on one list. Leaving the list empty makes it account wide; naming one scopes it to that list. A date field's default is three separate numbers rather than a date string, and options are only meaningful for the two select types.
- Update Personal Field Changes a personal field. Name and type are both required by the vendor even when only one is changing, so send the current type if the type is staying as it is. An option being edited must carry its own ID, and an option without one is created.
Tags
4- Get Tags Reads every tag on the account, of all three kinds together. A type field tells them apart, because tags belonging to lists, to subscribers and to messages share one answer and a tag meant for subscribers has to be picked out of it.
- Get Subscriber Tags Reads only the tags of the subscriber kind. List and message tags are left out.
- Get Subscriber Tag Reads one subscriber tag. A tag ID belonging to a list or a message is not returned here, because this route only serves the subscriber kind.
- Create Subscriber Tag Creates a tag of the subscriber kind. It will not appear in the list or message tag panels, because the three kinds are separate namespaces.
Email Suppression
5- Get Unwanted Emails Reads the suppression list of email addresses. Nothing on it can be mailed.
- Get Unwanted Email Reads one entry on the email suppression list by subscriber ID, which is the subscriber's ID rather than an ID belonging to the suppression entry.
- Add Unwanted Email Puts an address on the email suppression list, which stops all mail to it.
- Remove Unwanted Email By Address Takes an address off the email suppression list, keyed on the address itself. The vendor publishes two forms of this removal and this is the one that matches on the address.
- Remove Unwanted Email By ID Takes one entry off the email suppression list by subscriber ID.
Phone Suppression
5- Get Unwanted Phones Reads the suppression list of phone numbers. It is a separate list from the email one: suppressing an address does not suppress that person's number.
- Get Unwanted Phone Reads one entry on the phone suppression list by subscriber ID.
- Add Unwanted Phone Puts a number on the phone suppression list. The old system identifier is the vendor's migration key and is only meaningful for accounts carried over from its previous platform.
- Remove Unwanted Phone By Number Takes a number off the phone suppression list, keyed on the number.
- Remove Unwanted Phone By ID Takes one entry off the phone suppression list by subscriber ID.
Webhooks
2- Create Webhook Attaches a webhook to one list. Only three events exist and their IDs are 1, 2 and 5, so the numbering gap is not a mistake to correct. The merges object names which subscriber fields to include in the callback body, the body type decides whether the callback arrives as a form post or as JSON, and an array switch decides whether it is wrapped. The vendor publishes no route to list webhooks, so keep the returned ID: it is the only way to delete this one later.
- Delete Webhook Removes a webhook by its ID.
Frequently Asked Questions
What can FlowRunner do with Rav Messer?
FlowRunner agents can run Get Account, Get Lists, and Get List in Rav Messer, plus 33 more actions.
Does connecting Rav Messer to FlowRunner require OAuth?
No. Rav Messer connects to FlowRunner with session-based authentication, no OAuth flow required.
Can Rav Messer trigger a FlowRunner workflow automatically?
Rav Messer doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Email Marketing integrations
Start building with Rav Messer
Free plan, no card required. Connect in minutes.