Groove

Work the Groove shared inbox from AI agent workflows. Agents list and triage support conversations, reply to customers, add internal notes, look up contacts, and run raw GraphQL queries against Groove's v2 API for anything the dedicated actions don't cover.

6 actions API key available

Groove website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

The morning triage run starts on a schedule, before the support team logs in

List Conversations pulls everything in the Unread state from the shared inbox

Get Conversation reads each thread's full message history and primary contact

The agent classifies each conversation: routine question, billing issue, or angry escalation

Create Note attaches the classification and suggested response to each conversation as internal context

Create Reply saves the agent's drafted answer as a draft on routine conversations

A support agent reviews each draft, edits where needed, and sends, and escalations get a person from the first touch

What This Integration Enables

Groove is a shared inbox for small teams, and the honest constraint of a small team is that nobody is spare. The work an agent can absorb is everything around the reply: reading the thread, pulling the history, classifying the issue, drafting the answer, and leaving the internal note that saves the next teammate ten minutes of scrollback. FlowRunner agents do that continuously against Groove's GraphQL API, and where the dedicated actions stop, Run GraphQL Query reaches anything else in the schema. - Triage the shared inbox by listing conversations filtered by state - Draft customer replies from workflow context, delivered or saved as drafts - Attach agent-only notes for hand-offs, context, and reminders - Sync Groove contacts into a CRM or reporting spreadsheet - Reach any uncovered operation through raw GraphQL queries The economics matter here. A five-person company cannot hire a support team, but it can give its one support-owner an agent that reads every thread first. The owner's day changes shape: instead of processing a queue top to bottom, they review prepared work, approve the routine, and spend their actual attention on the conversations where a human voice changes the outcome. That is the difference between automation that replaces care and automation that funds it. The dividing line FlowRunner draws is the one that matters in support: agents prepare the words, and a person decides which words a customer actually receives. That is [human-in-the-loop](/concepts/human-in-the-loop) as Groove's own draft mechanism intends it, and it is why the draft flag on Create Reply is the most load-bearing parameter in this connector.

Without FlowRunner

The inbox greets you cold The team starts each day reading threads from scratch to figure out what each one even is

Context lives in heads The person who handled the thread last knows the history, and nobody else does

Speed and care trade off Answering fast means templated replies; answering well means the queue grows

With FlowRunner

Triage happens before coffee Every unread conversation arrives classified, with history summarized in an internal note

Hand-offs carry their context Agent-only notes travel with the thread, so any teammate can pick it up mid-story

Drafts wait, humans send The agent writes the routine answers as drafts; a person approves what the customer reads

Use Case Scenarios

The queue that triages itself overnight

At 6 a.m., the agent lists Unread conversations, reads each with Get Conversation, and sorts them: password resets and shipping questions get drafted replies queued as drafts via Create Reply; anything mentioning refunds, cancellations, or legal words gets a Create Note flag with the reason spelled out and jumps the queue. When the team logs in, the easy half of the inbox needs only a read-and-send, and the hard half is already ranked with context attached. The first hour of the day goes to customers instead of to sorting.

Support intelligence without the copy-paste

Weekly, the agent walks List Conversations across states and appends each ticket's number, subject, state, and age to [Google Sheets](/integrations/google-sheets). The same run pulls List Contacts and syncs new customers into [HubSpot](/integrations/hubspot) so the CRM knows who has been writing in. The founder reads a real support backlog trend line instead of a gut feeling, and sales stops discovering support history mid-call, because the CRM record now carries it.

The escalation that arrives pre-briefed

A message in [Slack](/integrations/slack) flags a customer issue that started in Groove. The agent finds the conversation, reads the full thread, and posts a summary to the channel: who, what, how long, what was already promised. When the account owner takes over, Create Note logs their plan on the conversation itself, so the support team sees the hand-off in the tool they already work in. The customer never repeats their story, and neither team works blind, because the thread itself carried the hand-off.

Human-in-Loop Highlight

Create Reply delivers to the customer the moment it fires, and a support reply is the company speaking on the record: a wrong refund promise, a tone-deaf line under an angry thread, a confident answer that is factually wrong, all of it lands in a customer's inbox with your name on it. This is why the action's draft option is the most important parameter in this connector. FlowRunner agents write every customer-facing response as a draft by default, with Create Note carrying the agent's reasoning alongside it. A support agent reads the draft in Groove, edits or approves, and sends. Immediate delivery is reserved for the narrow cases a human has explicitly pre-approved as templates. The agent's speed shows up in how fast drafts appear, never in how little a person saw before the customer did.

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

6 actions

Conversations

List Conversations Lists shared-inbox conversations most recent first, with paging and an optional state filter across Unread, Opened, Closed, Snoozed, Spam, and Deleted. The read behind every triage pass.
Get Conversation Retrieves one conversation by node ID with its number, subject, state, primary contact, and full message thread. The context pull before any classification or draft.
Create Reply Adds a reply to a conversation, delivered to the customer immediately or saved as a draft. The customer-facing send this page's human gate exists for.
Create Note Adds an internal, agent-only note to a conversation for context, hand-offs, and reminders. Never visible to the customer.

Contacts

List Contacts Lists customers with node ID, name, and email, paged by cursor. Used for CRM sync and for resolving a contact before conversation work.

Escape Hatch

Run GraphQL Query Executes an arbitrary GraphQL query or mutation against the Groove v2 API with your own query string and variables. The path to anything the dedicated actions do not cover.

Frequently Asked Questions

What can FlowRunner do with Groove?

FlowRunner agents can run List Conversations, Get Conversation, and List Contacts in Groove, plus 3 more actions.

Does connecting Groove to FlowRunner require OAuth?

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

Can Groove trigger a FlowRunner workflow automatically?

Groove doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Groove

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

Start Building Free Talk to us