SlickText (v2)
MessagingSend SMS and MMS and manage contacts through SlickText's modern brand-scoped v2 developer API. Agents discover brands, create and look up contacts, send messages, and browse lists across every SlickText account they can access.
What This Integration Enables
SlickText's v2 developer API scopes everything to a brand: contacts, messages, and lists all live under an account, and every operation carries a Brand ID. That design is built for the operators who need it most, agencies and multi-location businesses running SMS for several audiences from one seat, and it makes scope the thing that must never be guessed. FlowRunner agents treat the Brand ID as a resolved fact, not a default: discover the brand, verify it, then write and send inside it. - Route new customers from storefronts and CRMs into the correct brand's audience, with opt-in status carried honestly from the source - Send transactional and marketing texts scoped to the brand the recipient actually opted into - Sweep per-brand message history and list counts into consolidated reporting across every account the token can reach - Filter contacts by opt-in status to build segments from consent, not from list size - Gate cross-brand operations with [human-in-the-loop](/concepts/human-in-the-loop) confirmation, because scope errors are customer-facing
Without FlowRunner
With FlowRunner
Use Case Scenarios
Three locations, three brands, zero mixups
A retailer runs a SlickText brand per city. When a customer buys from the Austin store in [Shopify](/integrations/shopify), the agent calls List Brands, matches the order's location to the Austin brand, and verifies it with Get Brand. Create Contact writes the buyer under that brand with their opt-in status from checkout. The welcome text waits for the Austin manager's approval, then Send Message fires from the Austin number. The customer hears from the store they walked into, not from headquarters or the wrong coast.
The agency rollup that used to take a morning
An agency manages SMS for a roster of clients, each a separate brand. Every Monday, an agent iterates List Brands, and for each brand pulls List Messages for the week and List Lists for current subscriber counts. The results consolidate into one [Google Sheets](/integrations/google-sheets) workbook, one tab per client, and a digest posts to [Slack](/integrations/slack) with each account's send volume and list growth. Client reporting stops being a morning of logging in and out of sub-accounts.
Segments built from consent, not from the whole list
Before a campaign, the agent calls List Contacts filtered by opt-in status under the target brand, splitting the audience into subscribed contacts, pending confirmations, and everyone else. The subscribed segment feeds the campaign. The pending list goes to a person as a follow-up queue. Nothing is ever sent to a contact whose status says they did not ask for it, and the campaign's reach number reflects real consent instead of raw list size.
Human-in-Loop Highlight
Send Message is brand-scoped, and when the Brand ID is omitted it silently falls back to the one in the service configuration. That fallback is convenient right up until an agent built for one client runs against another, and a text leaves the wrong business's number: a coffee roaster's promo arriving from a dental clinic's line, to a person who opted into neither. The message cannot be recalled, and the apology comes from your client. So in multi-brand workflows, FlowRunner agents never let a send inherit its scope. The agent posts: "Welcome text ready for the number ending 0417. Sending brand: Harbor Coffee Roasters, resolved from the Shopify location, not the configured default. Body attached. Confirm brand and send?" The manager confirms, the text goes out from the right number, and the log records the brand that a person, not a fallback, chose.
Agent Capabilities
8 actionsBrands
2- List Brands Lists the brands accessible to the API token, each with the brand ID that scopes every other operation. The discovery step that turns "which account?" into a verified fact.
- Get Brand Retrieves a single brand's name, status, and configuration by ID, falling back to the configured brand when none is supplied. Used to verify scope before writes and sends.
Contacts
3- List Contacts Lists contacts within a brand with mobile number, name, email, opt-in status, and custom fields, with filtering by opt-in status and cursor pagination. The segmentation step that builds audiences from consent.
- Create Contact Creates a contact under a brand from a mobile number, with optional name, email, birthdate, and opt-in status. The write that moves a buyer or signup into the correct brand's audience.
- Get Contact Retrieves a single contact's full profile within a brand. Used to check status and history before a send or a human review.
Messages
2- Send Message Sends an SMS or MMS from a brand to a single recipient number. Delivery respects the recipient's opt-in status and carrier rules, and the brand scope decides which number the message leaves from, which is why this action sits behind the page's human gate.
- List Messages Lists sent and received messages within a brand, with direction, body, status, channel, and timestamps, filterable by direction. The per-brand audit trail behind agency reporting.
Lists
1- List Lists Lists the contact lists defined within a brand with ID, name, and contact count. The feed for growth snapshots and campaign targeting per account.
Frequently Asked Questions
What can FlowRunner do with SlickText (v2)?
FlowRunner agents can run List Brands, Get Brand, and List Contacts in SlickText (v2), plus 5 more actions.
Does connecting SlickText (v2) to FlowRunner require OAuth?
No. SlickText (v2) connects to FlowRunner with an API key, no OAuth flow required.
Can SlickText (v2) trigger a FlowRunner workflow automatically?
SlickText (v2) doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SlickText (v2)
$100 in credits. No card required. Connect in minutes.