Superchat
MessagingRun WhatsApp, SMS, email, Instagram, Facebook Messenger, Telegram, and live chat conversations from one Superchat workspace. Agents keep the thread in one place regardless of where the customer started it.
What This Integration Enables
Superchat has the widest channel surface of any connector in this category: WhatsApp, SMS, email, Instagram, Facebook Messenger, Telegram, Google Business Messaging and Live Chat, all resolving into one workspace with shared inboxes, labels and assignees. Email being in that list is the part worth pausing on. Every other platform in this space treats email as somebody else's problem, which means the customer who emails you and the customer who messages you are two records with two histories. Here they are one conversation object with a channel attribute, and Send Email Message sits in the same action group as Send WhatsApp Template Message.
For a FlowRunner agent that changes what the interesting decision is. Sending is trivial and every connector can do it. The decision that actually matters on a platform this wide is which channel a given reply should leave on, and Superchat gives an agent the data to reason about it. Get Conversation returns the state of the messaging time window for that channel. List Channels returns everything the workspace can reach. List Contact Conversations returns every thread already held with the person, so a flow picks up an existing conversation rather than starting a parallel one. Around those sit the operations that make a shared inbox work under automation. Internal notes are visible to agents and never delivered to customers. Structured contact search resolves someone by phone or email before a flow decides whether to create or update them. Custom attributes keep external data on the contact record, conversations can be exported, and delivery analytics report per message and per template. FlowRunner's connectors are built and verified against each vendor's official API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Inbound message arrives already briefed
On Inbound Message fires. Before a person has seen it, the agent runs Search Contacts on the sender's phone number, pulls the account from HubSpot, and writes what matters into the thread with Create Conversation Note: plan, renewal date, open tickets, last order. It then calls Update Conversation once to set the inbox, apply labels and assign the right user. Notes are visible to agents in the inbox and never delivered to the contact, so the briefing sits beside the chat rather than inside it. The responder opens a thread that already explains itself.
Shipping notifications that respect the window
An order ships in Shopify. Because the customer has not written in recently, free text will not reach them on WhatsApp, so the agent calls List Templates to confirm the shipping template is approved, then Send WhatsApp Template Message with the placeholder values supplied by position. Afterwards it calls Get Message Analytics for the sent message IDs to see deliveries, failures, reads, link clicks and free-form replies. Failed deliveries do not disappear into a log. They come back as a list the agent can retry on another channel or hand to a person.
Contact records that stay worth reading
Customer data changes in the CRM. The agent runs Search Contacts with a structured query on the email address, then Update Contact to write the new custom attribute values, being careful to send the complete handles list because that field is replaced wholesale rather than merged. New attributes the business starts tracking get defined once with Create Custom Attribute. The result is that the person answering a WhatsApp message sees the same account facts the finance team sees, without either team maintaining the other's system.
Human-in-Loop Highlight
The moment a Superchat agent should stop is the moment the free window has closed and it still has something to say. The customer messaged from Instagram several days ago. The answer is ready. Every route out of the workspace now has a different cost attached. A WhatsApp template is the only thing that opens a WhatsApp conversation outside the 24 hour window, it is billed, its wording is fixed by prior approval, and it arrives on a channel the customer never chose. An email through Send Email Message is free and unrestricted, but it lands in an inbox they may not check for a week. Waiting for them to write again is also a decision, just an unvoiced one.
No amount of context makes that a computable choice, because it is a judgment about how much this particular customer wants to be contacted. So the agent brings the decision to the person who owns the thread rather than defaulting to the most expensive option. It calls Get Conversation to read the window state for the channel, List Contact Conversations to check whether another thread with the same person is still open, and List Channels to see what the workspace can actually reach them on. Then it posts into the assigned inbox: "Reply drafted for this contact. The Instagram window has closed. WhatsApp is reachable via the approved order-update template, billed. Email is reachable through the workspace channel. There is an open Live Chat thread from last month. Send on which channel, or hold?" The responder picks one and the agent sends it on the channel they chose, in the thread that already exists. That is human-in-the-loop doing the thing feature lists never capture: not approving a message, but choosing how to reach a person. The same discipline applies to Delete Template, which withdraws the template from the connected WhatsApp Business account as well as the workspace, and to Delete Conversation, which removes a thread and its entire message history permanently.
Agent Capabilities
46 actionsMessaging
5- Send Text Message Sends a plain text message to a single recipient through one of the workspace channels, covering WhatsApp, SMS, Instagram, Facebook Messenger, Telegram, Google Business Messaging and Live Chat. Superchat routes it into the existing conversation for that recipient or opens a new one. WhatsApp only accepts free text inside an open 24 hour customer service window.
- Send Media Message Sends an image, video, audio clip or document to a single recipient. The file must already exist in the workspace, so upload it first and pass the returned file ID. An optional caption is delivered alongside on channels that support it.
- Send Email Message Sends an email through a Superchat email channel, taking an HTML body, a plain text body, or both so clients without HTML support still render it. Attachments reference files already uploaded to the workspace. This is what makes email a peer channel here rather than a separate system.
- Send WhatsApp Template Message Sends an approved WhatsApp template, the only way to start a WhatsApp conversation outside the 24 hour window. Placeholder values are supplied by position, matching the order the variables are defined in.
- List Conversation Messages Returns the messages belonging to a conversation, newest first, with cursor pagination. Used to reconstruct history or to read the latest inbound message before deciding how to reply.
Analytics
2- Get Message Analytics Returns per-message delivery statistics for a set of message IDs, covering sending attempts, deliveries, failures, reads, link clicks and free-form replies. Used to turn a failed send into a follow-up rather than a log line.
- Get Template Analytics Returns aggregated delivery and engagement statistics for templates, so a flow can compare which wording is actually read and replied to.
Contacts
7- List Contacts Returns contacts with their names, handles and custom attribute values, using cursor pagination.
- Create Contact Creates a contact with at least one handle, the phone number or email address Superchat uses to reach them. Custom attribute values can be set at creation so the record is complete from the start.
- Get Contact Retrieves a single contact including every handle registered for the person and the current values of all custom attributes.
- Update Contact Updates a contact's name, gender, handles and custom attribute values. The handles list is replaced wholesale, so include every handle that should remain and keep the existing handle IDs for the ones you are preserving.
- Delete Contact Permanently removes a contact and its handles from the workspace. Conversations previously held with them remain in the inbox.
- Search Contacts Finds contacts matching a structured query, which is the reliable way to look someone up by phone number, email address or custom attribute before deciding whether to create or update them.
- List Contact Conversations Returns every conversation held with a contact across all channels, so a flow continues the most recent thread instead of opening a parallel one.
Contact Lists
5- List Contact Lists Returns the contact lists defined in the workspace. Lists group recipients for campaigns and template broadcasts.
- Get Contact List Retrieves a single contact list by identifier with its name and metadata.
- List Lists Of Contact Returns the lists a specific contact currently belongs to, which is the membership check before adding someone twice.
- Add Contact To List Adds a contact to a list so they are included in future campaigns and broadcasts sent to it.
- Remove Contact From List Removes a contact from a list, keeping the contact in the workspace.
Conversations
6- List Conversations Returns conversations across every connected channel with their status, inbox, labels, assigned users and participating contacts, using cursor pagination.
- Get Conversation Retrieves a single conversation including its status, inbox, labels, assigned users and the state of the messaging time window for that channel. That window state is what makes an informed channel decision possible.
- Update Conversation Changes the workflow state of a conversation: close it as done, mark it as spam, archive it, snooze it until a chosen time, move it to another inbox, assign agents, or replace its labels. Only the fields supplied are changed, so one call can route a thread completely.
- Delete Conversation Permanently deletes a conversation and its message history from the workspace. The contact record is kept.
- Create Conversation Export Starts an export of a conversation over a chosen time range. Exports are produced asynchronously, so the response returns an export ID with a pending status.
- Get Conversation Export Checks the progress of an export created earlier and returns the download link once it is done.
Notes
5- List Conversation Notes Returns the internal notes attached to a conversation. Notes are visible to agents in the inbox and are never delivered to the contact.
- Create Conversation Note Adds an internal note to a conversation, optionally attaching uploaded files. This is how an agent puts context from another system next to the chat rather than into it.
- Get Conversation Note Retrieves a single note including its author and attached files.
- Update Conversation Note Replaces the text and attachments of an existing note. The full content must be supplied because the update overwrites the stored value.
- Delete Conversation Note Removes an internal note. The conversation and its messages are unaffected.
Files
4- Upload File Uploads a file to the workspace by fetching it from a publicly reachable URL. The returned file ID is what the media, email and note operations accept.
- List Files Returns the files stored in the workspace with their names, MIME types and download links, using cursor pagination.
- Get File Retrieves the metadata of a stored file including a link that can be used to download it.
- Delete File Removes a file from the workspace. Messages that already delivered the file are not affected.
Templates
3- List Templates Returns the templates in the workspace, optionally narrowed to one channel, folder or type. WhatsApp templates carry an approval status that must be approved before they can be sent.
- Get Template Retrieves a single template including its full content, approval status and the channels it can be sent on. Read it before sending to confirm how many variables it expects.
- Delete Template Deletes a template from the workspace. WhatsApp templates are also withdrawn from the connected WhatsApp Business account, which makes this a wider action than a workspace cleanup.
Custom Attributes
3- List Custom Attributes Returns the custom attributes defined for contacts with their identifiers, data types and the option values available on select attributes.
- Create Custom Attribute Defines a new custom attribute on contacts so external data can be stored against each person. Select types additionally need their list of option values.
- Delete Custom Attribute Removes an attribute definition and the values stored against it on every contact.
Workspace
6- List Channels Returns the messaging channels connected to the workspace, such as WhatsApp numbers, SMS senders, email addresses and social inboxes. Every send needs one of these channel IDs.
- Get Channel Retrieves a single channel by identifier with its name and the messaging type it carries.
- List Inboxes Returns the shared inboxes configured in the workspace together with the users who have access to each one. Inbox identifiers are what conversation routing expects.
- List Labels Returns the labels defined in the workspace, used to tag conversations during routing.
- List Users Returns the workspace users with their names, email addresses and roles. Used to resolve an assignee before routing a thread to them.
- Get Current Workspace Returns the user and workspace the configured API key belongs to. Used to confirm credentials are valid and that a flow is pointed at the right workspace.
Triggers
2 triggersEvent Triggers
2- On Inbound Message Fires when a contact sends a message to any connected channel, running the flow with the message body, sender and conversation identifier. Because it spans every channel in the workspace, one flow can handle a WhatsApp message, an Instagram DM and an email with the same routing logic.
- On Workspace Event Fires when one of the selected workspace events occurs, covering outbound and failed messages, note creation, contact changes and conversation status changes. Failed messages are the useful one here: a flow can react to a send that did not land instead of assuming it did.
Frequently Asked Questions
What can FlowRunner do with Superchat?
FlowRunner agents can run Send Text Message, Send Media Message, and Send Email Message in Superchat, plus 43 more actions.
Does connecting Superchat to FlowRunner require OAuth?
No. Superchat connects to FlowRunner with an API key, no OAuth flow required.
Can Superchat trigger a FlowRunner workflow automatically?
Yes. Superchat supports 2 triggers that can start a FlowRunner workflow automatically.
Start building with Superchat
$100 in credits. No card required. Connect in minutes.