Flock
CommunicationPost messages, manage channels, and look up people with Flock. Agents deliver workflow notifications and route questions to the person who can answer them.
What This Integration Enables
Most chat connectors are built to read what was said. Flock's is built to notice what changed. That is not a positioning claim, it is what the API supports: Flock publishes no endpoint that lists a channel's recent history, so Fetch Messages takes explicit message identifiers, a limited number per call. Meanwhile both triggers fire on structure rather than speech. On New Channel fires when the token owner is added to or creates a channel. On New Channel Member fires when someone joins a channel you are watching. Flock is a good surface for governing a workspace and a poor one for mining it, and knowing which of those you are building matters more than any feature list.
So FlowRunner agents use Flock for two jobs. First, delivery: send messages to a user or a channel with text, FlockML, or an attachment, so the flow's output lands where the team is already looking. Second, workspace shape: create channels, list and change their membership, resolve people through contacts and public profiles, and react when either the channel list or a channel's membership moves. The human-in-the-loop step is what keeps the second job safe, because acting on membership means acting on people. One practical detail worth knowing early: Flock identifiers are prefixed, u: for users and g: for channels, and both the pickers and free text accept them.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Access drift caught the moment it happens
A finance channel is governed by a list of who may be in it. On New Channel Member fires when anybody joins. The agent pulls the joiner's public profile, compares them against the list, and where the two disagree it does not remove anyone. It direct messages the channel moderator with the person, the channel, when they joined, and what the access list says. Removal happens only if the moderator says so. Quarterly access reviews become a thing that happens continuously and quietly, and the only human effort is a yes or a no.
Project channels provisioned and staffed from a record
A new project row appears in Airtable with a client, a start date, and a named team. The agent calls Create Channel, resolves each team member through List Contacts, adds them with Add Channel Members, and posts the kickoff message with the scope and the key dates. When someone rolls onto the project mid stream, the same flow adds them and posts a short catch up in the channel so they are not starting from nothing.
Engineering events delivered where the team is looking
Pull requests opened in GitHub, failed builds, and deploys land in the owning team's Flock channel as they happen, each with a link back to the source. The agent renders the payload as an attachment or FlockML rather than as raw text so the message is readable at a glance, noting that Flock renders one attachment per message, so a summary plus a link beats trying to pack everything into one card.
Human-in-Loop Highlight
Remove Channel Members is a quiet action with a loud effect. The person disappears from the member list, loses the room where the work is being coordinated, and receives no explanation, because Flock does not send one. When an agent is watching a governed channel with On New Channel Member, it will find mismatches, and most of them will not be intrusions. They will be a contractor who was legitimately added by a manager, a transfer whose access list row has not been updated yet, or someone invited for one meeting. An agent that removes on rule will be technically correct and repeatedly wrong about people. So it stops: "Priya Raghavan joined the AP Close channel eleven minutes ago. She is not on the access list for this channel. Her profile shows her in Treasury, and she was added by Daniel, who is a moderator here. Keep her, remove her, or add her to the list?" The moderator answers, and Remove Channel Members runs only if they chose remove. The agent finds the drift. A person decides whether it was drift.
Agent Capabilities
11 actionsMessaging
2- Send Message Sends a message to a Flock user or channel on behalf of the token owner and returns the new message identifier. Accepts text, FlockML, or an attachment, and renders one attachment per message. Used for alerts, status updates, and direct escalations to a named person.
- Fetch Messages Retrieves specific messages by their unique message identifiers, a limited number per call. Flock publishes no endpoint that lists a channel's recent history, so this reads messages the flow already has identifiers for rather than browsing a room.
Channels
3- List Channels Lists every channel the token owner belongs to with identifier, name, member count, and profile image. Used to resolve a channel by name before posting or provisioning.
- Get Channel Info Retrieves a single channel's metadata, including its member count. Used to confirm the agent has the right room, and to check size before sending something that will interrupt everyone in it.
- Create Channel Creates a channel with a name and an initial member list, returning its identifier. Used to provision a room per project, per client, or per incident from an upstream record.
Membership
3- List Channel Members Lists a channel's members with each member's identifier and affiliation, moderator or member. Used for access reviews and to work out who to escalate to inside a room.
- Add Channel Members Adds one or more users to a channel. Used to staff a new project room and to bring people in as they roll onto the work.
- Remove Channel Members Removes one or more users from a channel. The removal is immediate, visible in the member list, and carries no explanation to the person removed, so it belongs behind a moderator's decision rather than behind a rule.
People
3- List Contacts Lists the public profiles of every contact associated with the token owner, including identifier, name, avatar, and whether the contact is a guest. Used to resolve names to Flock identifiers before messaging or adding anyone.
- Get Current User Returns the full user record behind the configured token, including identifier, team, email, name, and timezone. Works only for users who installed the app the token belongs to. Used as a connection check and to establish the agent's own identity.
- Get Public Profile Looks up any Flock user's publicly visible profile by identifier, returning name, avatar, and guest flag. Used to identify a person the agent did not add and therefore cannot read through Get Current User.
Triggers
2 triggersEvent Triggers
2- On New Channel Fires when the token owner is added to, or creates, a Flock channel. Used to notice a workspace growing: register the new channel in an inventory, post a charter message, or start a governance flow that asks who owns it.
- On New Channel Member Fires when a user joins the selected channel. Used for continuous access review on governed rooms, for onboarding a joiner with a catch up message, and for keeping an external system's membership record in step with Flock. Both triggers poll. Flock's outgoing webhooks are created only in the developer dashboard and the API documents no method to create or delete one, so a real time trigger could not clean up after itself when it was disabled.
Frequently Asked Questions
What can FlowRunner do with Flock?
FlowRunner agents can run Send Message, Fetch Messages, and List Channels in Flock, plus 8 more actions.
Does connecting Flock to FlowRunner require OAuth?
No. Flock connects to FlowRunner with an API key, no OAuth flow required.
Can Flock trigger a FlowRunner workflow automatically?
Yes. Flock supports 2 triggers that can start a FlowRunner workflow automatically.
Start building with Flock
$100 in credits. No card required. Connect in minutes.