FlowRunner
PricingContact
Theme
Start Free

TextMagic

Messaging

Send business SMS through TextMagic. Agents text individuals, saved contacts, or entire lists, monitor inbound replies and opt-outs for follow-up, manage the address book, and check account balance before a campaign goes out.

11 actions API key available
TextMagic website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
Tomorrow's appointment schedule exports from the booking system overnight
Get User confirms the account balance covers the batch before anything is queued
List Replies sweeps recent inbound for STOP messages, and matching numbers come off the batch
The operations owner reviews the batch summary, recipient count, a rendered sample, and the balance impact, before anything sends
Send Message texts each confirmed recipient their reminder, numbers in E.164 format
List Message Sessions records the session grouping the batch for the audit trail
The delivery summary posts to the team channel with any failures called out

What This Integration Enables

SMS is the channel that gets read, which is exactly why it deserves more process than a dashboard send button. A text lands on a phone within seconds, cannot be recalled, and costs real credit from a finite balance; a text to someone who opted out is a compliance problem, not a typo. FlowRunner treats TextMagic as governed infrastructure: agents send to individuals, saved contacts, or entire lists, keep the address book synced from your other systems, watch inbound replies for opt-outs and follow-ups, and check the balance before a campaign goes out. - Trigger transactional texts, order updates, appointment reminders, confirmations, from any workflow event - Send to phone numbers, contact IDs, or whole lists from one action - Sync leads and customers into the address book, segmented into lists - Monitor replies for STOP opt-outs and customer responses that need a human - Put bulk sends behind [human-in-the-loop](/concepts/human-in-the-loop) approval, with balance checked first

Without FlowRunner

Reminders are a morning chore Someone works through a spreadsheet of appointments, sending texts one at a time or not at all
Opt-outs live in an unread inbox STOP replies sit in the reply log, and the next campaign texts those numbers anyway
Balance surprises kill campaigns A send fails partway because nobody checked the credit before launching

With FlowRunner

Batches assemble and verify themselves Agents build the recipient set, scrub opt-outs, and check balance before a person approves the send
Replies become follow-ups Inbound responses route to the team within minutes, and opt-outs are honored automatically
Every send has a session record Bulk sends group into auditable sessions with text, recipient count, and timestamp

Use Case Scenarios

Order updates the customer actually sees

A new order fires from [Shopify](/integrations/shopify). The agent sends the order-received text with Send Message, then follows with a shipping notification when the fulfillment event lands. Each message is one recipient, one event, fully transactional, so it runs without a gate. Get Message confirms delivery status afterward, and undelivered messages surface in the daily exceptions digest instead of vanishing.

Lead capture straight into the right list

A form response with a phone number arrives from [Typeform](/integrations/typeform). The agent runs Create Contact with the number and the campaign's list ID, since every TextMagic contact must belong to a list, then Send Message delivers the confirmation text. When a new campaign needs its own segment, Create List spins it up first. The address book stops being a stale export and starts reflecting the funnel as it actually is.

The reply loop that keeps you compliant

Every fifteen minutes, the agent pages through List Replies. STOP messages get logged to [Google Sheets](/integrations/google-sheets) and the sender's number is flagged so every future batch scrubs against it. Real customer responses, questions, reschedule requests, complaints, post to [Slack](/integrations/slack) with the sender's contact details pulled via Get Contact, so a person answers within minutes. The reply inbox stops being a liability nobody reads and becomes a queue somebody owns.

Human-in-Loop Highlight

Send Message accepts list IDs as recipients, which means one action call can text an entire list, spending per-message credit from a prepaid balance and landing on hundreds of phones with no recall. That is the operation FlowRunner gates. Before a list-wide send, the agent assembles the evidence: recipient count, the rendered message, the balance from Get User, and confirmation that the batch was scrubbed against recent STOP replies from List Replies. The operations owner approves that exact package, and only then does the batch fire, with List Message Sessions capturing the session for audit. Single transactional messages triggered by a customer's own action flow straight through. A blast to a list is a spend and a reputation event, and it waits for a person.

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

11 actions

Messages

5
  • Send Message Sends an SMS to one or more recipients: comma-separated phone numbers in E.164 format, saved contact IDs, or entire list IDs, with an optional sender ID. Returns the created message or session identifier.
  • List Messages Retrieves sent outbound messages, newest first, with page-based pagination and optional text search.
  • Get Message Retrieves a single sent message by ID, including recipient, delivery status, sender, cost, and timestamps.
  • List Message Sessions Retrieves message sending sessions. Each session represents one send request, bulk or individual, with the original text, recipient count, and timestamp. The audit record for bulk activity.
  • List Replies Retrieves inbound replies received on your TextMagic numbers, newest first, with sender, text, and timestamp. The read behind opt-out compliance and follow-up routing.

Contacts

3
  • List Contacts Retrieves address book contacts with pagination, text search, and filtering by contact list.
  • Create Contact Creates a contact with a phone number and at least one contact list, since TextMagic organizes every contact into lists. Optionally includes first and last name.
  • Get Contact Retrieves a single contact's details by ID: name, phone, email, country, and list memberships.

Lists

2
  • List Lists Retrieves the account's contact lists with pagination and text search. Lists group contacts for segmented messaging.
  • Create List Creates a new contact list for segmenting campaigns. Returns the created list's ID.

Account

1
  • Get User Retrieves the authenticated account, including balance, currency, timezone, and subscription status. The check that runs before every campaign so sends never fail partway on empty credit.

Frequently Asked Questions

What can FlowRunner do with TextMagic?

FlowRunner agents can run Send Message, List Messages, and Get Message in TextMagic, plus 8 more actions.

Does connecting TextMagic to FlowRunner require OAuth?

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

Can TextMagic trigger a FlowRunner workflow automatically?

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

Start building with TextMagic

$100 in credits. No card required. Connect in minutes.