GroupMe

Read and post group chat messages and manage bots, members, and blocks with GroupMe. Agents deliver updates into the group that already coordinates the work.

1 trigger 21 actions API key available

GroupMe website ↗ Platform Documentation ↗ Capability data verified 2026-08-03

On New Group Message fires when a volunteer posts that they cannot make Saturday

Agent pulls the shift, the date, and the member name from the message and the group roster

Agent finds who on the standby list is free and has covered this shift before

Agent posts the open shift into the group with Send Bot Message, clearly labeled as the bot

Agent confirms nobody claimed the shift inside the window the coordinator set

The coordinator approves the direct ask before the agent posts it under their own account with Send Message

What This Integration Enables

GroupMe is not a workspace product, and pretending otherwise is the fastest way to build the wrong flow. There is no admin console, no company tenant, no org owned identity. A group is a room of people, and the access token belongs to one of them. That makes GroupMe the right surface for the coordination that happens outside a corporate directory: volunteer rotas, sports and league schedules, field and delivery crews, franchise shift groups, campus and community organizations, and on call rotations for teams too small to buy anything heavier.

The connector reflects that honestly. FlowRunner agents can list groups and read their full membership, pull message history in pages, post as the token owner, like and unlike messages, remove members, update a nickname, and manage the token owner's own blocks and profile. Crucially it can also register bots: Create Bot puts a named automated member into a group, and Send Bot Message posts as that bot rather than as a human. If you want the group to know which messages are automated, that is not a convention you have to invent, it is an action you call. The human-in-the-loop step covers the rest, because in a room of real people the question is usually not what to say but whether it should come from a person.

Without FlowRunner

One person holds the group Coverage, reminders, and follow ups all run through whoever set the chat up

Nothing leaves the chat The roster lives in the scroll, so there is no record to reconcile against

Automation looks like a person Scripted messages post under a member's name and the group cannot tell what is automated

With FlowRunner

The routine runs itself Open shifts, reminders, and confirmations are posted without anyone chasing them

The chat feeds the record Messages are archived to a sheet the coordinator can search and count

Automation is labeled Routine posts come from a named bot, and anything in a person's voice is approved by that person

Use Case Scenarios

Shift coverage handled in the group people already use

A crew member posts that they cannot make their Saturday shift. On New Group Message fires, the agent parses the shift and date, checks the roster, and posts the open slot into the group as the bot with a clear ask for a volunteer. If nobody claims it inside the window, the agent works out who on the standby list is free and has covered that shift before, and hands the coordinator a suggested direct ask to approve. Nobody installed a scheduling app. The rota still got covered.

A searchable archive of a chat that has no search worth using

Every message in a group is appended to a row in Google Sheets or a record in Airtable with sender, timestamp, and text. Coordinators get something GroupMe does not give them: a searchable, countable history they can use to settle who said what and when, to count how often a shift went uncovered, or to hand a committee a clean record at the end of a season. The chat stays where the people are; the record lives somewhere it can be queried.

Roster reconciliation without a surprise removal

A membership system, an event registration, or a signup sheet is the source of truth for who belongs in the group. The agent reads the group with Get Group, compares the member list against the source, and reports the differences: people in the group who are no longer registered, and registered people who never joined. It posts the join link for the second set and hands the first set to the coordinator as a list, because removing someone from a group chat in a small community is a social act, not a data cleanup.

Human-in-Loop Highlight

The token this connector uses belongs to a person, and Send Message posts as that person. To everyone in the group, a message from the flow and a message the coordinator typed on their phone are indistinguishable. There is no delete action in this connector either, so a sentence the agent puts in the coordinator's mouth stays in the coordinator's mouth. That is the gate, and it is about identity rather than access. Routine, obviously mechanical posts go out as the bot through Send Bot Message with no ceremony. Anything that will read as a personal statement stops first: "Nobody has claimed Saturday's 6am shift. Marcus has covered it four times and is not on this week's rota. I can post the ask as the bot, or send it in your name, which will read as you asking him personally. Which?" The coordinator answers on the human-in-the-loop channel they already use. Ask the group as a bot, ask a person as a person.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

21 actions

Groups and Members

List Groups Lists the groups the authenticated user currently belongs to, newest activity first. Used to resolve a group by name before reading or posting.
List Former Groups Lists groups the authenticated user has left but can still rejoin. Used in audits and in flows that need to re enter a seasonal group.
Get Group Retrieves a single group with its full membership list, share URL, and a preview of the most recent message. Used for roster reconciliation and to grab the join link for people who should be in the room.
Get Member Add Results Retrieves the outcome of an asynchronous member add request using the results identifier it returned. Used to confirm which invitations actually landed rather than assuming they all did.
Remove Member Removes a member from a group, or removes the authenticated user themselves. Needs the membership identifier rather than a user identifier, which the member picker supplies. Removing someone from a community group is visible and unexplained, so it belongs behind a coordinator's decision.
Update Nickname Changes the authenticated user's own display nickname inside a specific group. Used to label the automation account clearly in a group where it posts.

Messages

List Messages Retrieves messages from a group, newest first by default, in pages. Used to build an archive, to reconstruct context around a single message, or to count activity over a period.
Send Message Posts a message to a group as the authenticated user. The group sees it as coming from that person, which is why anything written in a personal voice should be approved by that person first.
List Direct Message Chats Lists the authenticated user's one to one conversations, sorted by recent activity. Used to find the direct thread with a specific person before following up.
Like Message Adds the authenticated user's like to a message. Used as a lightweight acknowledgement that a request was seen without adding another message to the room.
Unlike Message Removes the authenticated user's like from a message. Used to reverse an acknowledgement applied by an earlier rule.

Bots

Create Bot Registers a bot as an automated member of a group and returns the identifier that Send Bot Message needs. Used to give a flow its own visible identity in the room instead of borrowing a person's.
List Bots Lists every bot the authenticated user has created, across all groups, with its identifier, group, avatar, and callback URL. Used to audit what automation is currently sitting in which groups.
Send Bot Message Posts a message into a group as a registered bot rather than as the authenticated user. This is the right action for routine, scheduled, and mechanical posts, because the group can tell at a glance that no person wrote it.
Delete Bot Permanently removes a bot the authenticated user created, which also removes it from its group. Used to decommission an automation cleanly at the end of a season or a project.

Account

Get Current User Returns the profile of the account the access token belongs to, including identifier, name, email, and phone. Used as a connection check and to establish whose voice Send Message will carry.
Update Profile Updates attributes on the authenticated user's own GroupMe account. Used to keep the automation account's name and avatar clearly identifiable.

Blocks

List Blocked Users Lists the contacts the authenticated user has blocked from direct messaging them. Used in audits of the automation account's own state.
Check Block Checks whether a block exists between the authenticated user and another user, in either direction. Used before a flow tries to open a direct message that would silently fail.
Block User Blocks another user so they can no longer direct message the authenticated user. Used after a person, not a rule, has decided the block is warranted.
Unblock User Removes an existing block, restoring the other user's ability to send direct messages. Used to reverse a block once the situation behind it is resolved.

Triggers

1 triggers

Event Triggers

On New Group Message Fires whenever any member posts a message in the selected group. Used to start intake, coverage, archival, and routing flows from what people actually write. The trigger works by registering a callback bot in the chosen group, because that is GroupMe's only documented delivery mechanism: the bot appears in the member list while the trigger is enabled and is removed when it is disabled. Messages authored by bots are ignored, so a flow that posts into the group it is watching cannot trigger itself.

Frequently Asked Questions

What can FlowRunner do with GroupMe?

FlowRunner agents can run List Groups, List Former Groups, and Get Group in GroupMe, plus 18 more actions.

Does connecting GroupMe to FlowRunner require OAuth?

No. GroupMe connects to FlowRunner with an API key, no OAuth flow required.

Can GroupMe trigger a FlowRunner workflow automatically?

Yes. GroupMe supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with GroupMe

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us