SimpleTexting
MessagingRun US SMS marketing from AI agents through SimpleTexting. Agents send SMS and MMS messages, create and update contacts, and organize contact lists so campaigns stay in sync with your CRM.
What This Integration Enables
SimpleTexting is list-based US SMS marketing, and the two things that discipline it are consent and credits. Every contact on a list is someone who agreed to hear from you, and every Send Message call consumes credits from a finite balance and reports exactly how many. That accounting is a feature, and FlowRunner is built to take it seriously: agents keep the lists synced with the systems where customers actually change, price each campaign before it fires, and put a person between the draft and a few thousand phones. - Sync leads and customers from forms, storefronts, and CRMs into contacts, with partial updates that never wipe untouched fields - Build a list per campaign with Create List, so audiences map to real offers instead of one bloated master list - Estimate and log credit consumption per send, turning the balance into a budget instead of a surprise - Sweep sent and received messages into reporting, and route replies that need judgment to a person - Gate every campaign send behind [human-in-the-loop](/concepts/human-in-the-loop) review of draft, audience, and cost
Without FlowRunner
With FlowRunner
Use Case Scenarios
A lead texts in from the form and gets a confirmation, not silence
A prospect submits a [Typeform](/integrations/typeform) that offers SMS updates. The agent calls Create Contact with the phone number, name, and email, adding them to the campaign's list by ID. A confirmation text goes out through Send Message from the account number, using a message the campaign owner approved when the flow was built. Get Contact verifies the record landed with the right list membership. The lead hears back while the form is still open in their browser, and the list grows only with people who asked to be on it.
Segments built from purchase behavior, not guesswork
When the quarter's win-back campaign kicks off, the agent calls Create List to make a fresh segment, then pulls lapsed buyers from [Shopify](/integrations/shopify) and syncs each into the new list with Create Contact and Update Contact. Because Update Contact is partial, syncing list membership never overwrites names or emails SimpleTexting already holds. The campaign owner gets the finished segment with a contact count from List Contact Lists, reviews the draft and credit estimate, and fires when ready.
The reply channel becomes a queue someone actually works
Every fifteen minutes, an agent pages List Messages for new inbound texts. Routine confirmations file straight into the [Google Sheets](/integrations/google-sheets) log. Anything that reads like a question, a complaint, or a buying signal posts to [Slack](/integrations/slack) with the contact's name from Get Contact and the recent thread for context. The person who replies has the history in front of them, and no customer's "does this come in a medium?" dies in an unwatched inbox.
Human-in-Loop Highlight
Send Message in a loop is where a SimpleTexting workflow gets expensive in two currencies at once. Each call consumes credits from a finite balance, and each message lands on a US phone number where texting someone without consent is not a tone problem but a TCPA problem. A misresolved list ID is all it takes: the agent meant the 80-person VIP segment and pulled the full house list instead. So the send never fires on the agent's own authority. It reports first: "Win-back draft ready. List: Lapsed Buyers Q3, 1,214 contacts. Mode: SMS only. Estimated credits: 1,214 against a balance of 5,000. Send, edit, or shrink the audience?" The campaign owner answers, and only then does the loop run, logging message IDs and credits consumed as it goes. The math ran at machine speed. The spend, and the decision to reach 1,214 phones, belonged to a person.
Agent Capabilities
8 actionsMessaging
2- Send Message Sends a single SMS or MMS to one contact. Takes the recipient phone, the message text, and your sending account number, with Delivery Mode to force SMS, force MMS, or let SimpleTexting choose. Returns the message ID and credits consumed, which is what makes campaign-level cost logging possible.
- List Messages Retrieves sent and received messages, most recent first, with direction, text, contact phone, and timestamps. The feed behind reply triage and campaign reporting.
Contacts
4- List Contacts Retrieves contacts with pagination, optionally filtered to a single contact list. The step that turns a list ID into an actual recipient set.
- Create Contact Creates a contact from a phone number, with optional name, email, and list membership by ID. The write that moves a lead from a form into a textable audience.
- Get Contact Retrieves one contact by phone number with name, email, and list membership. Used to verify writes and to give humans context on inbound replies.
- Update Contact Updates a contact by phone number. Only supplied fields change, which makes it the safe choice for recurring syncs from a CRM or storefront.
Lists
2- List Contact Lists Retrieves the account's contact lists with ID, name, and contact count. The resolution and audience-sizing step before any campaign.
- Create List Creates a new contact list by name and returns its ID. The step that gives each campaign its own segment instead of another blast at the master list.
Frequently Asked Questions
What can FlowRunner do with SimpleTexting?
FlowRunner agents can run Send Message, List Messages, and List Contacts in SimpleTexting, plus 5 more actions.
Does connecting SimpleTexting to FlowRunner require OAuth?
No. SimpleTexting connects to FlowRunner with an API key, no OAuth flow required.
Can SimpleTexting trigger a FlowRunner workflow automatically?
SimpleTexting doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SimpleTexting
$100 in credits. No card required. Connect in minutes.