SleekFlow
MessagingConnect AI agents to SleekFlow's omnichannel inbox. Agents create, search, and update contacts, send messages over WhatsApp, SMS, and social channels, read conversation threads, and segment customers with labels for targeted broadcasts.
What This Integration Enables
SleekFlow unifies the channels where your customers actually answer: WhatsApp, SMS, Facebook Messenger, Instagram, and the rest of the social messaging stack. That reach cuts both ways. Messages there get read because they land next to conversations with friends, and they burn trust twice as fast when they are wrong, late, or unwanted. FlowRunner agents work both sides of the inbox: they keep the contact book synced with the CRM and store, read threads to feed inbound requests into downstream workflows, and send outbound messages under rules that respect what the channel is. The connector defines no triggers; a webhook configured in SleekFlow pointing at a FlowRunner endpoint gives you the real-time inbound path. - Send order, shipping, and support notifications over WhatsApp, SMS, and social channels - Sync contacts between SleekFlow and your CRM, store, or spreadsheet, deduplicated on phone and email - Read conversation threads to route inbound requests into tickets, sheets, and escalations - Segment contacts with labels and target broadcasts at audiences a person has approved - Look up any customer by name, email, or phone before touching their record or their thread
Without FlowRunner
With FlowRunner
Use Case Scenarios
Order confirmations where customers actually look
A [Shopify](/integrations/shopify) order comes in. The agent runs Search Contacts on the buyer's phone number, creates the contact if new, and sends the confirmation with tracking link over WhatsApp via Send Message. When the customer replies "when will it arrive," the webhook hands the thread to the flow, the agent answers from live carrier data, and only an unhappy tone escalates to a person. The support inbox stays quiet because the questions got answered where they were asked.
The lead that exists in every system by lunchtime
A new lead lands in [HubSpot](/integrations/hubspot). The agent mirrors them into SleekFlow with Create Contact, applies the right segment with Add Label to Contact, and the welcome sequence begins on the channel the lead actually uses. When the lead replies, Get Conversation Messages feeds the exchange back to the CRM as an activity, so the sales rep opens the record and sees the whole relationship, not half of it.
Support threads that become tickets, not screenshots
A customer raises a product defect over Instagram DM. The sweep classifies the thread, pulls the full history with Get Conversation Messages, and opens a ticket in [Zendesk](/integrations/zendesk) with every message attached in order. The conversation also logs to [Google Sheets](/integrations/google-sheets) for the weekly quality review. Nobody screenshots a DM into an email chain again, and the helpdesk metrics finally include the social channels where half the volume lives.
Human-in-Loop Highlight
The dangerous operation in SleekFlow is not a delete, it is Send Message pointed at a labeled segment. Labels drive targeting, and Add Label to Contact is exactly the kind of call an agent makes hundreds of times a day, which means one bad labeling rule quietly builds a wrong audience. Fire a promotional broadcast at that audience over WhatsApp and the mistake is delivered into personal message threads, where recipients do not shrug, they block, and blocks degrade your standing on the channel itself. WhatsApp also has hard rules of its own: outside the 24 hour customer service window, an approved template is required. So FlowRunner workflows split the work at the audience line. Agents build segments, apply labels, and draft the message. A person reviews the audience count, spot-checks who is in it, and confirms the template situation before the send loop runs. One approval, thirty seconds, and the difference between a campaign and an apology.
Agent Capabilities
12 actionsContacts
6- List Contacts Pages through the contact book with names, phone numbers, emails, and profile details. The full-book read behind syncs and audits.
- Get Contact Retrieves one contact's complete profile: labels, custom fields, and channel identities. The context call before messaging or updating anyone.
- Search Contacts Free-text search across name, email, and phone. The matching step that keeps automations from creating duplicates or messaging the wrong person.
- Create Contact Creates a contact with at least a phone number or email so they can be messaged and deduplicated, with optional labels applied at birth. The entry point for CRM and store sync.
- Update Contact Changes only the fields you supply on an existing contact. The default write for keeping profiles current across systems.
- Delete Contact Permanently removes a contact from the account. Cannot be undone, so cleanup flows verify the ID and present the list before this fires.
Messaging
1- Send Message Delivers a message to a contact over the chosen channel, WhatsApp, SMS, Facebook Messenger, or Instagram, using their registered identity there. Outside WhatsApp's 24 hour service window an approved template is typically required. The action every scenario on this page ends with, and the one the broadcast gate protects.
Conversations
2- List Conversations Pages through inbox threads, filterable to open or closed, with contact, assigned staff, status, and last-message details. The sweep's entry point.
- Get Conversation Messages Reads a thread's messages in order with direction, channel, sender, and timestamps. The action that turns an inbox into workflow input.
Labels
2- List Labels Lists the account's contact labels with IDs, names, and colors. The reference read before any segmentation logic runs.
- Add Label to Contact Attaches existing labels to a contact; labels already present are left unchanged. The segmentation write that quietly determines who future broadcasts reach, which is why audiences get reviewed downstream.
Companies
1- List Companies Pages through companies grouping related contacts under one organization. Plan-gated: accounts without the feature may get an empty result, so workflows treat it as optional enrichment.
Frequently Asked Questions
What can FlowRunner do with SleekFlow?
FlowRunner agents can run List Contacts, Get Contact, and Search Contacts in SleekFlow, plus 9 more actions.
Does connecting SleekFlow to FlowRunner require OAuth?
No. SleekFlow connects to FlowRunner with an API key, no OAuth flow required.
Can SleekFlow trigger a FlowRunner workflow automatically?
SleekFlow doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SleekFlow
$100 in credits. No card required. Connect in minutes.