Gmelius
EmailManage shared inboxes, kanban boards, and email sequences with Gmelius. Agents triage a shared mailbox, move work onto a board, and keep sequences aligned with what the thread actually says.
What This Integration Enables
Gmelius sits on top of Gmail, and that is the fact everything else on this page follows from. The shared inboxes are real Gmail mailboxes, the conversations are real threads, the drafts are real drafts, and Reply to Conversation sends a real email from an address a customer already recognises. It is not a ticketing system with an email connector bolted on the side. It is your existing mail, with a shared layer of assignment, status, tags, notes and kanban wrapped around it, which is why teams pick it and why an agent working here is working directly on live customer correspondence rather than on a copy. If your flows also need message-level access to the underlying mailbox, the Gmail connector covers that side.
The surface splits into three. Shared folders and conversations are the inbox layer. An agent lists conversations with filters on date range, assignee and tags, then reads a thread in full with its messages and internal notes. From there it can assign the thread, set its ticketing status to open, pending or closed, and apply tags. It can also add notes that teammates see and participants never do, stage a shared draft, or send a reply. Boards, columns and cards are the work layer, where a card can be created against an existing Gmail message by its RFC message ID so the thread and the card are genuinely the same piece of work. Sequences are the outbound layer, with enroll and disenroll carrying template variables, and Gmelius applying its own rate limit on enrollment to stay inside Gmail's sending limits. Three webhook-backed triggers cover board changes, conversation changes and sequence activity, each registering a Gmelius webhook on the specific board, folder or sequence you name and removing it on teardown. Gmelius restricts API access to its Growth and Enterprise plans, with credentials visible to admins and managers.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Shared inbox triage that ends in a person, not a send
A message lands in the support inbox and On Conversation Event fires. The agent reads the full thread, classifies the request, applies the right tag, sets the status to open and assigns the teammate who owns that product area. It then stages a reply with Create Draft on Conversation, marked as a shared draft so anyone on the team can see it, and adds an internal note explaining why it classified the thread the way it did and what it based the draft on. The teammate opens Gmail, finds the thread already sorted with a draft waiting, and sends it. Nothing reached the customer without a person pressing send.
Board cards and email threads that stay one thing
A ticket is created in Jira. The agent calls Create Card on the delivery board, linking it to the originating Gmail message by its RFC message ID, and applies a tag matching the ticket type. When the Jira ticket resolves, the agent moves the card with Update Card and calls Update Conversation Status to close the email conversation in the same step. On Board Event covers the other direction, so a card someone drags to Done in Gmelius can trigger the outbound update. The engineer works in Jira, the customer sees an email thread, and neither has to know about the other.
Sequences that stop when the person actually replies
A new lead is created in HubSpot. The agent calls Enroll in Sequence with the lead's display name and the template variables the sequence expects. On Sequence Event fires as the sequence executes each step. When the lead replies in the shared inbox, On Conversation Event fires and the agent immediately calls Disenroll from Sequence, so the next scheduled email never goes out. The single most common way outbound email annoys people is continuing after they answered, and closing that gap is a matter of two triggers and one action.
Human-in-Loop Highlight
Reply to Conversation sends an email from the shared team address, and it offers a choice that deserves more attention than it usually gets: reply to the last sender only, or reply to all participants. Shared threads accumulate people. A customer, their colleague who was copied once, a partner who was pulled in for one question, someone who has since left that company and whose address still forwards. An agent replying to all on a thread it classified correctly but read shallowly can put a pricing exception, an escalation summary or an internal-sounding sentence in front of an audience nobody chose. Email has no recall, and the shared address is precisely the one your customers have learned to trust.
Gmelius supplies the gate itself, which is why FlowRunner leans on it rather than inventing one. Create Draft on Conversation stages the reply as a shared draft that a teammate can see and edit. Add Note to Conversation records the agent's reasoning where teammates can read it and participants can never see it. Assign Conversation puts a name on the thread. So the agent triages, drafts, annotates and assigns, then stops and posts to the team channel: "Thread from Renata at Colvin Freight, classified as a billing dispute over the March invoice. Draft reply is staged on the conversation and assigned to you. Note that four addresses are on this thread including their external accountant, so a reply-to-all sends them the credit terms. Send as drafted, edit, or reply to Renata only?" The teammate decides and sends. Everything upstream of the send is automated, and the send itself belongs to a person.
Agent Capabilities
41 actionsAccount
1- Get Current User Returns the Gmelius profile of the connected account: the OpenID subject identifier, email address and display name. Used as a connection check and to resolve the acting identity before other steps.
Boards
5- List Boards Lists every kanban board the connected user can access, including each board's owner, type and the users it is shared with. Used to resolve a board by name before working on it.
- Create Board Creates a new kanban board linked to a team, returning the board with its generated identifier. Used to stand up a workspace for a new project or queue.
- Get Board Retrieves a single board by identifier, including owner and shared-user details.
- Update Board Renames an existing board. The name is the only property the API allows updating.
- Delete Board Permanently deletes a board by its identifier. Used only in cleanup flows, and worth confirming before it runs given what a board contains.
Columns
5- List Board Columns Lists all columns of a board with their names and positions. Used to resolve a target column before moving a card.
- Create Column Adds a column to a board, appended as the last column when no index is given.
- Get Column Retrieves a single column by identifier, including its board, name and position.
- Update Column Renames a column and moves it to a new position. Only the fields supplied are changed.
- Delete Column Deletes a column. The cards it holds can be archived instead of deleted, and the response lists the archived card identifiers.
Cards
5- List Column Cards Lists the cards in a column with pagination. The vertical row index selects the normal or pending sub-category of the column.
- Get Card Retrieves a single card. The Full format additionally returns the card's notes.
- Create Card Creates a card in a column, optionally creating a new Gmail conversation for it or linking it to an existing message by its RFC message ID. That link is what keeps a board card and an email thread the same piece of work.
- Update Card Updates a card's subject, snippet, due date, status or assignee. Only the fields supplied are changed, and leaving the assignee email empty keeps the current assignee.
- Delete Card Permanently deletes a card by its identifier.
Shared Folders
2- List Shared Folders Lists the shared inboxes and shared labels of the connected user with pagination and an optional name filter, selecting between folders the user owns and all folders linked to them.
- Get Shared Folder Retrieves a single shared folder by identifier, including the users it is shared with. Used to confirm who can see a conversation before an agent acts on it.
Conversations
7- List Conversations Lists the conversations of a shared folder with cursor pagination and optional filters by creation date range, assignee email and tag names. Used to sweep a queue for unassigned or ageing threads.
- Get Conversation Retrieves a single shared conversation. The Full format additionally returns the conversation's messages and notes, which is what an AI classification step should read rather than the subject line alone.
- Reply to Conversation Sends an email reply on a shared conversation, either to the last sender only or to all participants. This leaves the building from the shared team address with no recall, so it belongs behind an approval rather than at the end of a classification step.
- Create Draft on Conversation Creates an email draft on a shared conversation, optionally shared with teammates, replying to the last message unless a specific message ID is referenced. This is the staged alternative to sending, and the action most triage flows should end on.
- Add Note to Conversation Adds an internal note to a shared conversation. Notes are visible to teammates and never sent to the email participants, which makes them the right place for an agent to record why it classified or routed a thread.
- Assign Conversation Assigns a shared conversation to a teammate by email, or unassigns it when the email is left empty. Used to put a name on a thread the moment it is classified.
- Update Conversation Status Sets the ticketing status of a shared conversation to open, pending or closed. Used to close the loop when the underlying work resolves elsewhere.
Tags
4- Add Tag to Card Applies a tag to a board card, either creating a new tag by name with an optional colour or applying an existing tag by ID.
- Remove Tag from Card Removes a tag from a board card. The tag itself remains in the subscription.
- Add Tag to Conversation Applies a tag to a shared conversation, either creating a new tag by name or applying an existing one by ID. Used to make an agent's classification visible in the inbox itself.
- Update Tag Renames a tag or changes its colour across the whole subscription. Only the fields supplied are changed, and the change is subscription-wide rather than local to one board.
Notes
3- Create Note Creates an internal note on a Gmail thread or on a board card. Provide exactly one of a thread ID or a card ID. The author can be matched to a subscription user by full name.
- Update Note Replaces the body of an existing internal note.
- Delete Note Permanently deletes an internal note by its numeric identifier.
Sequences
4- List Sequences Lists the email sequences of the connected user with pagination and an optional name filter, including each sequence's settings and template variables. Used to discover which variables an enrollment must supply.
- Get Sequence Retrieves a single sequence by identifier, including its settings, shared users and template variables.
- Enroll in Sequence Enrolls a recipient in a sequence, optionally with a display name and values for the sequence's template variables. Gmelius applies a dedicated rate limit to enrollments to stay within Gmail sending limits.
- Disenroll from Sequence Removes a recipient from a sequence so no further sequence emails reach them. Used the moment a reply arrives, which is the difference between a follow-up and a nuisance.
Webhooks
5- List Webhooks Lists the webhooks registered on the current grant with pagination, including each webhook's model, callback URL and activity status.
- Create Webhook Registers a webhook on a board, shared folder or sequence. Gmelius validates the callback URL with an HTTP HEAD request that must return 200 before creation, and signs deliveries with an RS256 JWT in a dedicated header.
- Get Webhook Retrieves the configuration of a single webhook registered on the current grant.
- Delete Webhook Deletes a webhook so no further events reach its callback URL.
- List Webhook Events Lists the historical events delivered to a webhook within a timestamp window, with offset pagination. Each event carries the previous attributes alongside the changed entity, which makes this the action to reach for when reconstructing what a flow reacted to.
Triggers
3 triggersEvent Triggers
3- On Board Event Fires when something changes on a chosen board: cards created, updated or deleted, columns changed, card notes changed, or board settings updated. Used to drive outbound updates when a person moves work on the board. Gmelius registers a webhook on the board and removes it on teardown.
- On Conversation Event Fires when a conversation in a chosen shared folder changes: created, updated, a reply added, or a note created or deleted. Used to triage arriving mail and to detect the reply that should stop an outbound sequence. Gmelius registers a webhook on the shared folder and removes it on teardown.
- On Sequence Event Fires when a chosen email sequence executes an action or a recipient is disenrolled. Used to keep a CRM in step with what the sequence actually did rather than what it was scheduled to do.
Frequently Asked Questions
What can FlowRunner do with Gmelius?
FlowRunner agents can run Get Current User, List Boards, and Create Board in Gmelius, plus 38 more actions.
Does connecting Gmelius to FlowRunner require OAuth?
Yes. Gmelius connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Gmelius trigger a FlowRunner workflow automatically?
Yes. Gmelius supports 3 triggers that can start a FlowRunner workflow automatically.
Start building with Gmelius
$100 in credits. No card required. Connect in minutes.