Sendme
Email MarketingManage contacts and send SMS and email campaigns with Sendme, maintaining a tagged address book with custom fields. Agents keep segmentation driven by live data rather than a periodic upload.
What This Integration Enables
Sendme is a contact book with two delivery channels bolted to it, and the design decision that matters is how it lets you address an audience. There are exactly three scopes: an explicit list of recipients, every contact carrying one of a set of tags, or every active contact in the organization. Send SMS To Contacts, Send SMS By Tags and Send SMS To All Contacts are three operations rather than one operation with a filter, and the email side mirrors them exactly. That is a genuinely good API decision, because it makes the blast radius of a send a property of which operation the workflow called, not a property of a parameter someone might get wrong.
Around that sit tags, custom fields and a message log. Tags are the segmentation primitive, and List Tags With Usage Counts returns how many contacts carry each one, so an agent can size a segment before it sends to it. Custom fields let a workflow store the attributes it filters on later. Sends are queued asynchronously, so the acceptance of a send is not a delivery confirmation, and List Messages is the reconciliation surface that turns a fired campaign into a real delivery report. FlowRunner agents drive all of that on live data, and the two moments where the scope changes irreversibly are the two moments where the flow stops and asks a person.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Rebuilding the address book from the system of record
The authoritative customer list lives in a CRM or a warehouse, and once a month the Sendme address book is rebuilt from it. Before anything is touched, the agent pages the current book out with List Contacts, records the totals with Count Contacts, and captures per-tag coverage with List Tags With Usage Counts. It then compares the incoming file against that snapshot: row counts, tag coverage, how many contacts carry a status other than Active. The comparison is the point. A rebuild is only safe when someone has looked at what the new file does and does not reproduce.
Order confirmation SMS that reaches the right one person
An order is created in Shopify or WooCommerce. The agent calls Create Contact to add the customer to the address book with the tags that describe them, then Send SMS To Contacts with the phone number taken straight from the order. This is the explicit-recipient scope on purpose: a confirmation is addressed to a person, never resolved from a segment. Numbers arriving without an international prefix are normalised using the country code. Later, List Messages filtered to that contact and date range confirms whether the message actually landed, and a failure routes to support rather than disappearing.
A tagged campaign sized before it launches
Marketing wants to reach everyone tagged for a product line. The agent calls List Tags With Usage Counts, sees how many contacts carry the tag today, and only then builds the send. Send SMS By Tags and Send Email By Tags both reach every contact carrying at least one of the supplied tags, which means a tag that has crept across the book turns a segment into a broadcast without any change to the workflow. Afterwards, the agent exports List Messages into Google Sheets so delivery status by country code and provider becomes a report the team actually reads.
Human-in-Loop Highlight
Delete All Contacts wipes the entire address book in one call and cannot be undone. Sendme's own documentation says so plainly, and it is the correct operation to use when a list is being re-imported from scratch, so removing it from the workflow is not the answer. The problem is that the agent can prove what it is about to destroy but it cannot prove that the incoming file replaces it. It can page the book out with List Contacts and it can count the tags, and neither of those tells it whether the file it is holding carries the same people.
So the flow assembles the comparison and stops. It posts to the operations channel: "Address book rebuild. Current book holds 4,890 contacts across 12 tags. The incoming file has 4,180 rows and no tag column, so the 312 contacts currently tagged VIP and the 806 tagged Renewal Q4 will lose those associations. Snapshot exported. Proceed with Delete All Contacts and re-import, import as an update without deleting, or abort?" An operations owner answers in the channel, and the human-in-the-loop step returns that decision to the flow. The 700-contact difference might be a year of churn correctly reflected, or it might be a failed export. The agent is not in a position to know which, and it says so instead of running the call.
Agent Capabilities
23 actionsContacts
7- List Contacts Returns a paginated page of contacts with phone number, email, status, tags and custom field values, filterable by free text, lifecycle status, tags, country code, origin and name. This is the main way an agent builds or verifies an audience before sending.
- Get Contact Retrieves one contact by identifier with its full tag list and every custom field value. Used to enrich a workflow with the current state of a person before deciding what to send them.
- Create Contact Creates a contact, requiring a first name and phone number, with email, last name, birth date, country code, tags and custom field values optional. New contacts default to Active, which is what determines whether the send-to-all operations reach them.
- Update Contact Partially updates a contact, changing only the supplied fields. Supplying tag identifiers replaces the contact's existing tag associations rather than adding to them, so a workflow that means to add a tag sends the full set.
- Delete Contact Deletes one contact and returns the deleted record. The person stops receiving campaigns and direct sends immediately.
- Count Contacts Returns the total number of contacts as a single number without transferring any records. Used for dashboards, quota checks, and as the guard in front of a bulk send.
- Delete All Contacts Deletes every contact in the organization. This is irreversible and wipes the whole address book, so it belongs behind an explicit human confirmation with the current count in front of the person approving it.
Tags
6- List Tags Returns every tag with its name, description and display colour. Tags are the segmentation primitive here, driving both the send-by-tag operations and the contact list filter.
- List Tags With Usage Counts Returns every tag together with how many contacts currently carry it. This is the operation that turns a segment into a number before a campaign is launched against it.
- Get Tag Retrieves one tag by identifier with its description and colour. Useful when a workflow holds only an identifier and needs the human readable name for a message or a log entry.
- Create Tag Creates a tag that can then be attached to contacts and targeted by sends. Only the name is required, with description and colour used for display in the Sendme interface.
- Update Tag Partially updates a tag's name, description or colour. Contact associations are preserved, so renaming a tag does not change who is in the segment.
- Delete Tag Deletes a tag from the organization. The contacts survive but lose the association, which means any automation targeting that tag silently stops matching them.
Custom Fields
2- List Custom Fields Returns the organization's custom fields with their input element type, stored data type and option lists for choice-style fields. The returned identifiers are what a contact write pairs its values against.
- Create Custom Field Defines a new custom field on contacts, where the element type controls how it renders and the data type controls how it is stored. Choice-style element types such as Dropdown or Radio Buttons are paired with an option list.
Messaging
8- Send SMS To Contacts Queues an SMS to an explicit list of phone numbers. This is the scope for transactional sends such as order confirmations and one-time passwords, because the recipients are supplied directly rather than resolved from the address book.
- Send SMS To All Contacts Queues an SMS to every active contact in the organization. Inactive and blocked contacts are excluded and there is no other filter, which makes the audience size worth confirming before it runs in production.
- Send SMS By Tags Queues an SMS to every contact carrying at least one of the supplied tags. This is the segmented alternative to the broadcast, and it should be preceded by a sizing call so the segment's real reach is known.
- Send Email To Contacts Queues an email to an explicit list of addresses using the organization's configured sender. The body accepts HTML or plain text, so the same operation serves receipts and formatted announcements.
- Send Email To All Contacts Queues an email to every active contact holding an email address. A broadcast with no segmentation, and the same sizing discipline applies.
- Send Email By Tags Queues an email to every contact carrying at least one of the supplied tags and holding an address. The usual way to run an email campaign against a saved audience.
- List Messages Returns a paginated log of messages sent from the account with delivery status, recipient details, country code and campaign association. Filterable by status, content type, campaign, contact, provider or date range, which makes it the reconciliation surface for an asynchronous send.
- List Channels Returns the messaging channels available to the organization, such as SMS or email. Checked before building a send step so a workflow does not target a route the account has not enabled.
Frequently Asked Questions
What can FlowRunner do with Sendme?
FlowRunner agents can run List Contacts, Get Contact, and Create Contact in Sendme, plus 20 more actions.
Does connecting Sendme to FlowRunner require OAuth?
No. Sendme connects to FlowRunner with an API key, no OAuth flow required.
Can Sendme trigger a FlowRunner workflow automatically?
Sendme doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Sendme
$100 in credits. No card required. Connect in minutes.