Missive
CommunicationConnect AI agents to Missive shared inboxes. Agents read conversations, send email drafts, post internal comments and notifications, manage contacts and contact books, apply shared labels, and route work to the right team, across 20 actions.
What This Integration Enables
Missive's defining idea is that the customer-facing thread and the team's private conversation about it live in one place. That split is exactly the seam an agent should work: everything internal, the context gathering, the triage note, the drafted reply, runs at machine speed, while the one operation that reaches a customer stays with a person. FlowRunner agents read conversations and full message bodies, post internal comments and notifications into shared inboxes, prepare outgoing email as drafts, keep contact books synced from source systems, and organize the queue with shared labels and team routing. The [human-in-the-loop](/concepts/human-in-the-loop) posture is native here, because Missive already treats the draft as a first-class team object. - Read conversations, messages, and internal comment threads across mailbox scopes - Push alerts and system context into shared inboxes as posts only the team can see - Prepare replies as drafts inside the right conversation, assigned and labeled for review - Sync contacts, groups, and organizations from the systems where customers actually originate
Without FlowRunner
With FlowRunner
Use Case Scenarios
Order events that land inside the conversation
A new order fires in [Shopify](/integrations/shopify). The agent calls Create Post to push the order summary into the team's shared inbox as a notification, labeled and routed to the right team. When the same customer later writes in, the thread already carries the order context as internal posts, so the assignee answers from the conversation instead of tab-hopping. New customers flow through Create Contact into the shared book and sync onward to [HubSpot](/integrations/hubspot), so the book and the CRM stop disagreeing.
Draft-first support replies
For each open thread, the agent reads the history with List Conversation Messages and Get Message, then checks List Conversation Comments so its suggestion never contradicts what a teammate already decided privately. It writes the proposed reply with Create Draft Email into the existing conversation, assigns it, and labels it ready for review. The assignee edits and sends. Response quality stays human, response latency stops depending on who is at their desk.
A queue that triages itself
On a schedule, the agent sweeps List Conversations across Inbox and Snoozed scopes, classifies each thread from its latest message, and applies the team's shared label taxonomy, built once with Create Shared Label as a hierarchy like Support/Billing and Support/Shipping. Threads matching escalation patterns get a Create Post notification naming the on-call teammate, resolved via List Users and List Teams. The morning queue arrives pre-sorted, and the labels feed reporting that reflects what the inbox actually contained.
Human-in-Loop Highlight
Create Draft Email can send immediately, and an email that leaves a connected mailbox reaches a customer with the company's name on it and cannot be recalled. So customer-facing sends are never the agent's call: the draft is the deliverable, the send is the decision. The contact operations carry their own edges. Delete Contact is permanent, and Update Contact fully replaces the contact info array when provided, meaning an update that omits entries silently erases every phone number and address the team had for that person. Agents therefore fetch the current record with Get Contact, merge rather than overwrite, and route deletions through a person with the full record displayed.
Agent Capabilities
20 actionsConversations
4- List Conversations Lists conversations from a mailbox scope such as Inbox, Assigned to Me, Closed, Snoozed, Flagged, Trashed, or Drafts, ordered by recent activity, with filtering by contact email, domain, or organization and cursor pagination.
- Get Conversation Retrieves one conversation with subject, assignees, participants, shared labels, message and draft counts, and last activity.
- List Conversation Messages Lists a conversation's email and chat messages, newest first, with sender and recipient fields, previews, and attachment metadata. Bodies come from Get Message.
- List Conversation Comments Lists the internal team comments in a conversation, including author, mentions, and any linked task. The private half of the thread customers never see.
Messages
1- Get Message Retrieves a single message with its full HTML or plain-text body, the only endpoint that returns it, plus sender, recipients, subject, and attachments.
Drafts
1- Create Draft Email Creates an outgoing email as a draft, optionally sending immediately or scheduling. Replies into an existing conversation by id, sets From, To, CC, BCC, subject, and body, and can assign teammates and apply labels. Sending requires the From address to be a mailbox connected to the Missive account.
Posts
1- Create Post Creates a comment, note, or notification in a conversation, or starts a new one. Supports Markdown, notification titles, labeling, closing, and assignment. The channel for pushing system context into the inbox without emailing anyone.
Contacts
7- List Contacts Lists contacts in a chosen contact book with search, ordering, and pagination, including modified-since filtering for incremental syncs.
- Get Contact Retrieves one contact with all info entries, notes, starred status, and group or organization memberships.
- Create Contact Creates a contact in a book with name fields, notes, and an array of emails, phones, addresses, URLs, and social handles.
- Update Contact Updates provided fields on a contact. Supplying the contact info array replaces it entirely, so agents merge with the existing record first.
- Delete Contact Permanently deletes a contact. Cannot be undone, which is why it sits behind confirmation.
- List Contact Books Lists accessible contact books with owner, organization, and sharing settings. Book ids scope all contact operations.
- List Contact Groups Lists a book's groups or organization records, for tagging contacts and modeling companies.
Shared Labels
3- List Shared Labels Lists an organization's shared labels, the team-wide tags that structure shared inboxes.
- Create Shared Label Creates a shared label, optionally nested under a parent for hierarchies like Support/Billing, with color and sharing scope.
- Update Shared Label Renames, recolors, reparents, or reshapes the sharing of an existing label.
Organization
3- List Teams Lists an organization's teams, which group users and their shared inboxes. The lookup behind routing.
- List Organizations Lists the organizations the account belongs to. Organization ids scope teams and labels.
- List Users Lists users with id, name, email, and avatar, optionally filtered by organization. Used to resolve assignees before routing a conversation.
Frequently Asked Questions
What can FlowRunner do with Missive?
FlowRunner agents can run List Conversations, Get Conversation, and List Conversation Messages in Missive, plus 17 more actions.
Does connecting Missive to FlowRunner require OAuth?
No. Missive connects to FlowRunner with an API key, no OAuth flow required.
Can Missive trigger a FlowRunner workflow automatically?
Missive doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Missive
$100 in credits. No card required. Connect in minutes.