Fleep
CommunicationSend messages, manage conversations and hooks, and search chat history with Fleep, a team messenger with built-in task tracking. Agents post updates into the thread that owns the work.
What This Integration Enables
Fleep's defining trait is that it does not draw a hard line between chat and email. Conversation members are given as email addresses, the way you would write an email To: line, and anyone on that list who does not have a Fleep account still takes part through Fleep's email interoperability. That single design choice is why Fleep suits work that crosses a company boundary: a client, a contractor, or a supplier joins the room without being asked to adopt your chat tool. FlowRunner agents work well against that shape because the flow already knows the email addresses. It does not need to resolve them to workspace user IDs first.
The connector covers the surface around that. Agents send, edit, delete, read, and full text search messages. They create conversations, set topics and alert levels, and mark, hide, leave, or delete them. They add and remove members by email address, and resolve unknown addresses through account lookup. They upload files and attach them to messages, and they manage the incoming and outgoing hooks on a conversation. On New Message gives a flow a way to react to what is said in a watched conversation. One honest note on the connection: Fleep issues no API keys, so the connector signs in with an account's email and password and holds the session. Everything the agent does is attributed to that account, which argues for giving the automation its own account rather than borrowing a person's.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A conversation per engagement, provisioned the moment the deal closes
A deal is marked closed won and the agent creates a Fleep conversation named for the account, sets the topic to the engagement scope, posts the kickoff summary, and attaches the signed statement of work with Upload File and Send Message. It assembles the member list from the CRM record: the internal delivery team, plus the client contacts who will actually be in the room. The internal names go straight in. The external addresses wait for a person. When the room exists on day one, nobody rebuilds context from an email chain in week three.
Support conversation messages become tickets
A shared support conversation is watched with On New Message. When a customer writes in, the agent reads the message, decides whether it is a new issue or a follow up on an open one, and either opens a ticket in Zendesk or appends to the existing one. It replies in the conversation with the ticket number so the customer sees their message landed somewhere. Because Fleep reaches people by email, the customer never had to install anything to be in that conversation.
Engineering activity mirrored into the project room
Pull requests opened in GitHub and cards moved in Trello are posted into the project conversation as they happen, each with a link back to the source. The agent edits its own earlier status message rather than posting a new one for every state change, so the room carries one current picture instead of a trail. When the project closes, a separate flow sets the conversation alerts to never and hides it, leaving the history searchable without leaving it noisy.
Human-in-Loop Highlight
Add Members takes email addresses, and an address that has no Fleep account is not rejected. Fleep reaches that person by email instead. That is the feature, and it is also the risk: adding an address is not adding a name to a list, it is opening a delivery path into somebody's inbox, and from that moment forward every message posted in the conversation goes to them. Remove Members closes the path, but it does not recall anything that already went out. So the agent does the assembly and stops before the write: "The Northwind engagement conversation is created and the internal team is in. The CRM lists four client contacts. Three resolve to existing Fleep accounts. The fourth, [email protected], is not on the signed agreement and has no Fleep account, so everything posted here would be emailed to that address. Add all four, add the three, or hold?" The engagement lead answers on the human-in-the-loop channel they already use, and Add Members runs against the list a person approved. The same care applies to Delete Conversation, which removes the record for the account, and to Configure Hook, which can start delivering a conversation's messages to an outside URL.
Agent Capabilities
24 actionsMessages
5- Send Message Posts a message into a conversation, optionally with attachments produced by Upload File. Used for status updates, escalations, and replies back to the people in the room.
- Edit Message Replaces the text of an existing message, identified by its message number within the conversation. Used to keep one live status message current rather than stacking updates.
- Delete Message Deletes a message from a conversation by its message number. Used for cleanup, and used deliberately, because a message that recorded a decision is part of the record of that decision.
- Get Messages Retrieves messages from a conversation. Used to give the agent surrounding context before it classifies a single line or decides how to reply.
- Search Messages Runs a full text search across the account's conversations. Used to find whether a question has been asked before, or to pull the thread where a decision was made.
Conversations
9- Create Conversation Creates a conversation with an optional topic and an initial member list given as email addresses. Used to provision a room per project, per engagement, or per incident.
- List Conversations Lists the account's conversations, paging with a sync horizon marker. Used to resolve a conversation by topic before posting.
- Get Conversation Retrieves a conversation's header record, including topic, members, and message counters, along with recent activity. Used to confirm the agent has the right room and who is currently in it.
- Set Conversation Topic Changes a conversation's topic. Used to keep the room's title in step with the phase or status of the work it holds.
- Set Conversation Alerts Sets a conversation's alert level, either delivering notifications normally or muting them. Used to wind a room down at the end of a project without deleting it.
- Mark Conversation Read Moves the account's read horizon to the last message. Used to keep the automation account's unread state honest after a flow has processed a room.
- Hide Conversation Hides a conversation from the account's conversation list. Used to archive a finished room while leaving its history searchable.
- Leave Conversation Removes the authenticated account from a conversation. Used when the automation should stop watching a room it no longer serves.
- Delete Conversation Deletes a conversation for the authenticated account. Used in cleanup flows, and worth an approval when the room holds the record of an engagement.
Members and Contacts
5- Add Members Adds members to a conversation by email address. Addresses without a Fleep account are reached through Fleep's email interoperability, which makes this an access decision rather than a list edit.
- Remove Members Removes members from a conversation by email address. Used when someone rolls off a project, noting that removal stops future delivery and does not recall past messages.
- List Contacts Lists the account's contacts, optionally filtered by a search string. Used to resolve a person before opening a conversation with them.
- Get Contact Retrieves a single contact record by account ID. Used to confirm identity before the agent acts on a message from that person.
- Lookup Accounts Resolves lookup strings such as email addresses to Fleep contact records. Used to tell an internal colleague from an outside address before members are added.
Hooks
4- List Hooks Lists the hooks configured on a conversation. Used to audit which external systems can post into or read out of a room.
- Create Hook Creates a hook on a conversation, giving an external system a path to post into it. Used to wire a monitoring tool or a build system directly into a project room.
- Configure Hook Renames a hook, changes its outgoing URL, or enables and disables outgoing delivery. Enabling outgoing delivery starts sending the conversation's messages to an external address, which is a data path worth approving rather than automating.
- Delete Hook Removes a hook from a conversation. Used to cut an integration off when a tool is retired or an engagement ends.
Files
1- Upload File Downloads a file from a URL and uploads it to Fleep, returning a value that Send Message accepts as an attachment. Used to deliver generated reports, signed documents, and exported data into the conversation where they will be discussed.
Triggers
1 triggersEvent Triggers
1- On New Message Fires for each new message posted in the selected conversation. Used to start intake, classification, and routing flows from what people write in a watched room, including messages that arrived by email from members without a Fleep account. The trigger polls rather than using an outgoing hook, because the Fleep API reference documents no schema for the outbound payload, so a real time trigger could not be relied on to behave the same way twice.
Frequently Asked Questions
What can FlowRunner do with Fleep?
FlowRunner agents can run Send Message, Edit Message, and Delete Message in Fleep, plus 21 more actions.
Does connecting Fleep to FlowRunner require OAuth?
No. Fleep connects to FlowRunner with session-based authentication, no OAuth flow required.
Can Fleep trigger a FlowRunner workflow automatically?
Yes. Fleep supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Fleep
$100 in credits. No card required. Connect in minutes.