SlickText
MessagingRun keyword-based SMS marketing through SlickText's v1 API. Agents add and unsubscribe contacts, browse textwords and lists, and send and review SMS messages to keep subscriber engagement in sync with your other systems.
What This Integration Enables
SlickText's model is the textword: a keyword a subscriber texts to your number to join a list. That keyword is not a technical detail, it is the unit of consent, and everything this connector does is anchored to it. FlowRunner agents grow the lists by subscribing signups from forms and CRMs into the right textword, where the list's own confirmation flow keeps the opt-in explicit. They audit what the account actually sent and received, and they carry opt-outs across systems so the person who said stop in one place stops hearing from you everywhere. - Subscribe web and CRM signups into a specific textword with Create Contact, preserving the keyword-anchored consent model - Mirror opt-outs from helpdesks, email platforms, and CRMs into SlickText, gated by a person because removal is permanent - Sweep sent and received messages into spreadsheets for campaign audit and reply triage - Enumerate textwords and lists with subscriber counts for growth reporting across every keyword - Put [human-in-the-loop](/concepts/human-in-the-loop) review in front of every operation that cannot be taken back
Without FlowRunner
With FlowRunner
Use Case Scenarios
Web signups join the keyword list without texting the keyword
A [Typeform](/integrations/typeform) signup form offers SMS updates. For each respondent, the agent calls List Textwords to resolve the campaign's keyword, checks List Contacts scoped to that textword so nobody is subscribed twice, and calls Create Contact with the mobile number and the textword. SlickText runs the list's confirmation flow, so the subscriber still confirms by text and the opt-in trail stays clean. The list grows from every channel, and consent stays anchored to the keyword.
The campaign audit that runs itself
Every night, an agent pages List Messages and appends the day's traffic to [Google Sheets](/integrations/google-sheets): direction, body, number, status, timestamp. Inbound replies that look like questions or complaints post to [Slack](/integrations/slack) with the sender's record from Get Contact attached. When compliance asks what was sent to whom in March, the answer is a filter on a spreadsheet, not a support ticket to the SMS vendor.
Growth reporting across every keyword
On Monday mornings, the agent calls List Textwords and List Lists, captures each keyword's subscriber count, and appends the snapshot to a tracking sheet. The week-over-week delta per keyword posts to [Slack](/integrations/slack). The team sees which textwords actually recruit subscribers, which lists are stagnant, and where the next campaign should point, without anyone logging into the dashboard to copy numbers.
Human-in-Loop Highlight
Unsubscribe Contact on this connector does more than suppress: it opts the contact out and deletes their record, and SlickText's API is explicit that the action cannot be undone. The subscriber's history, list membership, and identity leave the account with them. That is exactly right for honoring a real opt-out and exactly wrong for a mismatched one, because a wrong match erases a subscriber who never asked to leave and whose consent you cannot quietly restore. So the mirroring agent never removes anyone on inference alone. It posts: "Helpdesk ticket 4821 requests SMS opt-out for Sam Ortega. Matched SlickText contact ending 0417, subscribed to VIPDEALS since March, 12 messages received. Confirm removal?" The list owner confirms, the agent deletes, and the compliance log records who approved it. The lookup ran at machine speed. The unrecoverable step waited for a person.
Agent Capabilities
8 actionsTextwords and Lists
2- List Textwords Lists the keywords configured on the account, with IDs, the keyword string, and the associated number and status. The anchor step before subscribing contacts or scoping sends.
- List Lists Lists the contact lists on the account with IDs, names, and subscriber counts. The feed behind growth snapshots and campaign targeting.
Contacts
4- List Contacts Lists subscribers, optionally scoped to a single textword, with IDs, phone numbers, names, and subscription status. The dedup check before every subscribe and the lookup behind every opt-out match.
- Create Contact Subscribes a new contact into a given textword by mobile number, with optional name. Typically kicks off the list's confirmation flow, which keeps the opt-in explicit even when the signup came from the web.
- Get Contact Retrieves a single contact by ID with phone, name, status, and list membership. The context-gathering step before a human confirms a removal.
- Unsubscribe Contact Opts a contact out and deletes their record by contact ID. Cannot be undone, which is why it sits behind this page's human gate.
Messages
2- Send Message Sends an SMS to a single contact by contact ID or raw phone number, with a textword to identify the sending list when required. Long bodies split into segments, so drafts are checked before dispatch.
- List Messages Lists sent and received messages with direction, body, numbers, status, and timestamps. The audit trail behind campaign review and reply triage.
Frequently Asked Questions
What can FlowRunner do with SlickText?
FlowRunner agents can run List Textwords, List Contacts, and Create Contact in SlickText, plus 5 more actions.
Does connecting SlickText to FlowRunner require OAuth?
No. SlickText connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can SlickText trigger a FlowRunner workflow automatically?
SlickText doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SlickText
$100 in credits. No card required. Connect in minutes.