FlowRunner
PricingContact
Theme
Start Free

Telnyx

Messaging

Send and track SMS and MMS through Telnyx. Agents deliver transactional messages, check delivery status and cost per recipient, validate numbers and detect line type before sending, and search available numbers by country or area code.

7 actions API key available
Telnyx website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
A new order lands in the storefront with a customer phone number attached
Number Lookup validates the number and confirms the line type is mobile, not a landline or VoIP relay
The agent drafts the confirmation text and verifies the recipient has not opted out
Send Message delivers the SMS from your Telnyx number with the order details
Get Message confirms delivery status and records the per-message cost
The message ID, status, and cost append to an outbound-messaging log
An operator reviews the daily log and rules on any recipient the agent flagged as undeliverable or ambiguous

What This Integration Enables

Telnyx is carrier-grade messaging infrastructure, and the thing that separates disciplined SMS operations from expensive noise is what happens before and after the send. FlowRunner agents use Telnyx the way a careful operator would: look the number up first, send with the right sender identity, then verify the message actually arrived and what it cost. Because Number Lookup is a read-only intelligence call, agents can qualify every phone number that enters your workflows without spending a message segment on a dead line. - Send transactional SMS and MMS from a Telnyx number, short code, or alphanumeric sender ID - Validate numbers and detect line type, carrier, and portability before messaging - Check delivery status, encoding, and per-recipient cost on any sent message - Search purchasable inventory by country, area code, and required features - Audit the numbers and Messaging Profiles configured in your account The number inventory operations round out the picture for teams that treat their sender identities as assets. Search Available Numbers lets an agent scout purchasable inventory by market and required features when a new region or campaign needs local presence, and because it is search-only, the agent can present options without ever committing spend. List Phone Numbers and Get Phone Number keep the audit side honest: which numbers you own, which Messaging Profile each rides on, and whether the configuration behind a workflow still matches what the workflow assumes. Text messages land in pockets, which is exactly why FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate sits in front of anything beyond routine transactional sends. The pattern is consistent across every messaging connector FlowRunner offers, but the mechanics here are Telnyx's own: lookups before sends, statuses after them, and a person in between whenever the audience is a list rather than a customer.

Without FlowRunner

Texts sent blind Messages go to whatever number the form captured, and failures surface as silence
SMS spend is a surprise Per-message costs accumulate invisibly until the invoice arrives
No delivery record Whether the customer actually received the text is anyone's guess

With FlowRunner

Every number validated first Number Lookup confirms line type and carrier before a single segment is spent
Cost tracked per message Each send logs its ID, status, and cost the moment it returns
Delivery is auditable Get Message turns "we sent it" into a status you can show someone

Use Case Scenarios

Order confirmations that only go to real mobiles

A [Shopify](/integrations/shopify) order arrives. The agent runs Number Lookup on the customer's phone number: mobile lines get an SMS confirmation via Send Message, landlines get routed to email instead, and numbers that fail validation get flagged on the order record. No segments wasted on lines that cannot receive them, and the customer who typed their office landline still gets their confirmation somewhere.

The auditable outbound log

Every Send Message call returns an ID, status, and cost. The agent appends each one to [Google Sheets](/integrations/google-sheets) as it happens, then runs Get Message on anything still pending an hour later to capture the final delivery state. Finance sees messaging spend by day and by workflow without waiting for the Telnyx invoice, and support can answer "did we text them?" with a row, not a shrug.

Lead follow-up with a qualified list

A [Typeform](/integrations/typeform) response delivers a new lead with a phone number. The agent validates it with Number Lookup, confirms it is a mobile line, and drafts a follow-up text. Because this is a first outbound touch rather than a transactional receipt, the draft and the recipient go to the sales owner in [Slack](/integrations/slack) for approval before Send Message fires. Approved messages go out within minutes of the form fill; the ones a human vetoes never go out at all.

Human-in-Loop Highlight

Send Message costs money per segment and lands on a person's phone, and neither of those things can be taken back. A mis-targeted batch is not like a bad email blast that folders can absorb: SMS gets read, and a wrong message to a few hundred customers is a reputation event with a line-item cost attached. So when a FlowRunner workflow escalates from one-at-a-time transactional sends to anything batch-shaped, the agent assembles the recipient list, runs Number Lookup across it, prices the send, and presents the whole package to a person: this many recipients, this sender ID, this text, this estimated cost. The batch fires when a human says so. The agent's job is to make that decision take thirty seconds, not to make it.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via email
Human decides
Agent resumes with decision

Agent Capabilities

7 actions

Messaging

3
  • Send Message Sends an SMS or MMS from a Telnyx number, short code, or alphanumeric sender ID to one E.164 recipient. Media URLs turn the send into MMS. Returns the message record with ID, status, direction, cost, and parts. The action this page's human gate exists for.
  • Get Message Retrieves a message by its Telnyx ID to check current delivery status, cost, encoding, and per-recipient detail. The verification step behind every auditable send.
  • List Messaging Profiles Lists the Messaging Profiles that group your numbers and control webhooks, whitelisted destinations, and pooling. Used to confirm the right profile before sends that require one.

Phone Numbers

3
  • List Phone Numbers Lists the numbers your account owns, filterable by partial number, connection, or status. Used to pick the right sender for a given workflow.
  • Get Phone Number Retrieves one owned number's status, connection, messaging profile, billing group, and emergency settings. Used to audit sender configuration before it matters.
  • Search Available Numbers Searches Telnyx inventory for purchasable numbers by country, area code, pattern, locality, and required features. Search only; it never purchases.

Number Intelligence

1
  • Number Lookup Looks up carrier, line type, optional caller name, and portability data for any phone number. The read-only qualification step that keeps sends off landlines and dead numbers.

Frequently Asked Questions

What can FlowRunner do with Telnyx?

FlowRunner agents can run Send Message, Get Message, and List Phone Numbers in Telnyx, plus 4 more actions.

Does connecting Telnyx to FlowRunner require OAuth?

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

Can Telnyx trigger a FlowRunner workflow automatically?

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

Start building with Telnyx

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