Missive is a collaborative email and chat application designed to streamline team communication and task management.
Missive is a collaborative email and chat application designed to streamline team communication and task management. On Nagent, Missive is exposed as a fully-configurable email integration that any agent can call — 40 actions, and API key authentication. No code is required to wire Missive into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Missive to automate the kinds of tasks email teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Missive into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Missive, with input parameters and output schema. Drop these into any step of an agent built in Helix.
MISSIVE_CREATE_ANALYTICS_REPORTTool to create an analytics report. Use when you need to generate a report over a specific time range with optional filters. Returns a report ID for later retrieval.
Input parameters
Report specifications including organization, period, and optional filters
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_CREATE_CONTACTSTool to create one or more contacts in a Missive contact book. Use when you need to add new contacts with detailed information including name, email, phone, addresses, and organization memberships.
Input parameters
Array of contact objects to create. Each contact must include contact_book UUID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_CREATE_DRAFTTool to create a new draft in Missive. Use after preparing message details to save a draft (email, SMS, WhatsApp, or Live Chat) for later editing or scheduling.
Input parameters
HTML or text body of the draft. Use '<br>' for paragraphs.
Send the draft immediately upon creation
Team ID to link the draft's conversation
Close the conversation after draft creation
Account ID for custom channels or live chat
Unix timestamp to schedule sending (cannot combine with send)
Subject for email drafts
List of user IDs to grant access to the conversation (requires organization)
CC recipients for email drafts
List of recipients (one only for SMS/WhatsApp)
BCC recipients for email drafts
Force association to the specified team even if already linked
Sender information (email, phone, or custom channel)
Message-ID references for threading into existing conversations
List of file attachments (up to 25, total payload <=10MB)
Move the draft's conversation to everyone's inbox
Conversation ID to append the draft to
Organization ID to scope or link the conversation
List of user IDs to assign to the conversation (requires organization)
Auto-cancel scheduled draft if a reply arrives (requires send_at)
Shared label IDs to add to the conversation
Move the draft's conversation to team inbox (requires team)
HEX color code or 'good'/'warning'/'danger' for the conversation
Subject for new conversation when using references
WhatsApp template ID when initiating new WhatsApp conversation
Shared label IDs to remove from the conversation
Include quoted text of the last message in an existing conversation
Variables for WhatsApp template interpolation
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_CREATE_POSTTool to create a post in a Missive conversation. Posts can add comments, close conversations, assign users, apply labels, and trigger other actions. Recommended approach for managing conversations from integrations and automations.
Input parameters
Plain text content of the post
Close the conversation after creating the post
Reopen the conversation if it was previously closed
Unix timestamp to snooze the conversation until
Markdown-formatted content of the post
Move the conversation to inbox
Conversation ID to create the post in
Notification settings with title and body (both required)
Organization ID - required when using add_assignees parameter
User IDs to assign to the conversation
User IDs to unassign from the conversation
Shared label IDs to add to the conversation
Shared label IDs to remove from the conversation
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_CREATE_RESPONSETool to create one or more canned responses (templates) in Missive. Use when you need to save reusable message templates for the organization or user.
Input parameters
Array of response objects to create
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_CREATE_SHARED_LABELTool to create one or more shared labels at the organization level. Use when you need to create new labels that can be shared across the organization.
Input parameters
Array of shared label objects to create (at least one required)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_CREATE_TASKTool to create a task in Missive. Use when you need to create standalone tasks, conversation-linked subtasks, or team tasks. You can find or create parent conversations using message references (like email Message-IDs).
Input parameters
Team ID (required for standalone tasks unless assignees specified)
Task state enum.
Task title (max 1000 chars)
Unix timestamp for due date
Subject for new conversation when using references
Whether this is a subtask within a conversation
User IDs to add to parent conversation for subtasks
Array of user IDs (required for standalone tasks unless team specified)
Message references (like email Message-IDs) to find/create parent conversation
Task description (max 10000 chars)
Conversation ID for subtasks
Organization ID where the task will be created
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_CREATE_TEAMTool to create a new team in an organization. Use when you need to set up a new team with active members and optional observers. The API token must belong to an organization admin.
Input parameters
Array of team objects to create (typically one team per request)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_CREATE_WEBHOOKTool to create a webhook subscription. Use after choosing event type and target URL.
Input parameters
The webhook URL to receive event notifications.
Event type to subscribe to.
(new_comment only) Only trigger for comments by this user ID.
(incoming_email only) Only trigger for messages from this exact address.
(new_comment only) Only trigger for comments on tasks.
(new_comment only) Only trigger when this user ID is mentioned.
Organization ID to scope the subscription. Omit for personal webhooks.
Only trigger when content contains this substring.
(incoming_email only) Only trigger when email subject contains this text.
Only trigger when content ends with this substring.
Only trigger when content starts with this substring.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_DELETE_DRAFTTool to delete a draft from a conversation by draft ID. Use after confirming the draft ID; this operation cannot be undone.
Input parameters
Unique identifier of the draft to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_DELETE_POSTTool to delete a post from a conversation by post ID. Use when you need to remove a specific post; this operation cannot be undone.
Input parameters
Unique identifier of the post to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_DELETE_RESPONSESTool to delete one or more saved responses by ID. For organization responses, the API token must belong to an admin. Use after confirming the response ID(s); this operation cannot be undone.
Input parameters
Response ID to delete. To delete multiple responses, provide comma-separated IDs (e.g., 'id1,id2,id3').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_DELETE_WEBHOOKTool to delete a webhook subscription by webhook ID. Use after confirming the webhook ID; this operation cannot be undone.
Input parameters
Unique identifier of the webhook to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_GET_ANALYTICS_REPORTTool to fetch a completed analytics report using its ID. Use when you need to retrieve analytics data after creating a report. Reports typically complete within 2-3 seconds but may take up to 30 seconds. Reports expire 60 seconds after completion and return 404 if incomplete, expired, or non-existent.
Input parameters
Report ID returned by Create Analytics Report request (UUID format)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_GET_CONTACTTool to fetch a specific contact using the contact ID. Use when you need detailed contact information including names, contact info, and organizational memberships. Returns 404 for deleted contacts.
Input parameters
The unique identifier of the contact to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_GET_CONVERSATIONTool to fetch full conversation metadata (assignees/users/labels/team/org) for a specific conversation ID. Use when you need conversation-level details for assignment, labeling, or workflow purposes.
Input parameters
The ID of the conversation to retrieve. Note: Missive may return a different conversation ID if conversations were merged.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_GET_CONVERSATION_MESSAGESTool to list messages belonging to a Missive conversation (newest first). Use when you need to retrieve message metadata including participants and attachments references for a specific conversation.
Input parameters
The conversation identifier
Number of messages returned. Default: 10. Min: 2. Max: 10
Timestamp value in Unix time used to paginate. Use the delivered_at of the oldest message from previous page
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_GET_MESSAGETool to fetch full message details including headers, HTML body, and attachments. Use when you need complete message content with download URLs for attachments.
Input parameters
Message ID (can pass multiple comma-separated IDs to retrieve multiple messages)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_GET_RESPONSETool to fetch a specific saved response using the response ID. Use when you need to retrieve the full content and metadata of a saved response template.
Input parameters
Response ID (UUID format) to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_GET_TASKTool to get a single task by ID with full details including assignees, team, and conversation info. Use when you need to retrieve complete information about a specific task.
Input parameters
Task ID
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_CONTACT_BOOKSTool to list contact books the authenticated user has access to. Use when you need contact book IDs for creating contacts programmatically.
Input parameters
Number of contact books to return. Min: 1. Max: 200. Default: 50.
Offset for pagination. Default: 0.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_CONTACT_GROUPSTool to list contact groups or organizations linked to a contact book. Use when you need to retrieve groups for organizing contacts or organizations for linking contacts to businesses.
Input parameters
Type of contact group to list: group for contact labels or organization for business entities.
Number of contact groups to return. Max: 200. Default: 50.
Offset for pagination. Use to fetch subsequent pages of results.
Contact book ID to list groups from.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_CONTACTSTool to list contacts from a contact book. Use when syncing Missive contacts to another service or finding contacts based on search terms. Supports pagination via offset and filtering by modification date.
Input parameters
Number of contacts returned. Default 50, Max 200.
Order by field for listing contacts.
Offset for pagination. Use to skip N contacts.
Search term to filter contacts by name, email, or other fields.
Contact book ID to list contacts from. Required.
Unix timestamp to filter contacts modified since this time.
Include deleted contacts when using modified_since. Only works with modified_since parameter.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_CONVERSATION_COMMENTSTool to list comments in a Missive conversation ordered from newest to oldest. Use when you need to retrieve comments with author info, attachments, and task data for a specific conversation.
Input parameters
The conversation identifier
Number of comments returned. Default: 10. Max: 10
Unix timestamp for pagination. Use created_at of the oldest comment from previous page
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_CONVERSATION_DRAFTSTool to list draft messages in a Missive conversation (newest first). Use when you need to retrieve unsent drafts for a specific conversation including author and recipient details.
Input parameters
The conversation identifier
Number of drafts returned. Default: 10. Max: 10
Unix timestamp for pagination. Use delivered_at of the oldest draft from previous page
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_CONVERSATION_POSTSTool to list posts in a Missive conversation ordered by newest first. Use when you need to view automation traces or post history for a specific conversation. Posts are the recommended approach for automations as they leave a visible trace.
Input parameters
The conversation identifier
Number of posts returned
Unix timestamp for pagination. Use created_at from the oldest post of previous page
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_CONVERSATIONSTool to list conversations visible to the authenticated user ordered by newest activity first. Use when you need to retrieve inbox, all, assigned, closed, or other mailbox conversations. Must filter by at least one of: mailbox flag, shared label, or team parameter.
Input parameters
Pass true to list conversations in the All mailbox.
Filter conversations by email address. Returns conversations where this email appears as sender or recipient.
Pass true to list conversations in the Inbox.
Number of conversations to return. Min: 2. Max: 50. Default: 25.
Unix timestamp for pagination. Use last_activity_at from the oldest conversation of previous page.
Pass true to list conversations in Closed.
Filter conversations by domain. Returns conversations where any sender/recipient email belongs to this domain.
Pass true to list conversations in Drafts.
Pass true to list conversations in Spam.
Pass true to list conversations in Starred.
Pass true to list conversations in Snoozed.
Pass true to list conversations in Trash.
Pass true to list conversations assigned to the user.
Team ID to list conversations in team's All mailbox.
Team ID to list conversations in team's Inbox.
Team ID to list conversations in team's Closed mailbox.
Organization ID. Filter conversations to only those shared with the organization.
Shared label ID to list conversations in that label.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_MESSAGESTool to fetch messages matching an email Message-ID header. Use when you need to find a specific message by its Message-ID. Most of the time, only one message matches a given Message-ID.
Input parameters
Email Message-ID header value to search for. Most of the time, only one message matches a given Message-ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_ORGANIZATIONSTool to list organizations the authenticated user is part of. Use when you need to retrieve all organizations accessible to the current user.
Input parameters
Number of organizations to return. Max: 200. Default: 50.
Offset for pagination. Default: 0.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_RESPONSESTool to list saved responses (canned responses/templates) for the authenticated user. Use when you need to retrieve available response templates for composing messages.
Input parameters
Number of responses to return. Use for pagination.
Number of responses to skip. Use for pagination.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_SHARED_LABELSTool to list shared labels (organization-level labels) available to the authenticated user. Use when you need to retrieve labels for filtering conversations or understanding label structure.
Input parameters
Number of labels to return. Use for pagination.
Offset for pagination. Number of labels to skip before returning results.
Organization ID to filter labels. If not specified, returns labels from all organizations the user is part of.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_TASKSTool to list tasks accessible to the authenticated user. Use when you need to retrieve tasks by state, organization, or team. Tasks can be standalone, conversation-linked, or team tasks.
Input parameters
Team ID to filter tasks by team.
Number of tasks to return. Must be between 1 and 100.
Task state values.
Offset for pagination. Use to skip a number of tasks.
Organization ID to filter tasks by organization.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_TEAMSTool to list all teams. Use when you need to retrieve and enumerate all teams available in Missive. Returns an empty array for accounts with no teams configured; this is a valid response, not an error.
Input parameters
Number of teams to return. Max: 200. Default: 50.
Offset for pagination. Default: 0.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_LIST_USERSTool to list all users. Use after authentication when you need to retrieve all users in the organization.
Input parameters
Number of users to return. Max: 200. Default: 50.
Offset for pagination. Default: 0.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_MERGE_CONVERSATIONSTool to merge multiple conversations into one. Combines messages, posts, and other content from the source conversation into the target conversation. Use when you need to consolidate related conversations.
Input parameters
Source conversation ID to merge from. This conversation will be merged into the target conversation.
Target conversation ID to merge into. The source conversation will be merged into this conversation.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_UPDATE_CONTACTTool to update one or more contacts in Missive. Use when you need to modify contact attributes. Only pass fields you want to update. CRITICAL: infos and memberships arrays must include ALL items when passed - omitted entries will be permanently deleted.
Input parameters
Array of contact objects with id and attributes to update. Only include fields you want to change.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_UPDATE_RESPONSETool to update one or more saved responses in Missive. Use when you need to modify existing response templates by changing title, body, subject, or other attributes. Returns the updated responses.
Input parameters
Response ID to update. Can pass multiple comma-separated IDs for bulk update
Array of response objects to update. Each must include the 'id' field and the attributes to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_UPDATE_SHARED_LABELSTool to update one or more shared labels in Missive. Use when you need to modify label names or colors. Returns the updated shared labels.
Input parameters
Shared label ID in the path. Can pass multiple comma-separated IDs to update multiple labels.
Array of shared label objects with id and attributes to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_UPDATE_TASKTool to update an existing task's attributes in Missive. Use when you need to modify a task's description, change its state, update the due date, or reassign it to different users.
Input parameters
The ID of the task to update
Task attributes to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MISSIVE_UPDATE_TEAMTool to update one or more teams in Missive. Use when you need to modify team attributes like name, color, or initials. The API token must belong to an organization admin.
Input parameters
Team ID or comma-separated list of team IDs to update
Array of team objects with id and attributes to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 70 agents privately built on Nagent that already use Missive.
Build on Nagent
Connect Missive to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Missive, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Missive is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Missive is connected, you configure its 40 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Missive steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Missive event fires, the agent kicks off automatically.
Every Missive action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Missive ships with 40 pre-built email actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Missive together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Missive-based workflows tailored to your business.