Missive connector for AI agents

Tools your inbox agent reaches for on Missive, scoped per user.

CALL ANY TOOL

38 tools for shared inbox work in Missive: list and read conversations and messages, create drafts and send messages, add posts and tasks, merge conversations, manage contacts, shared labels, and canned responses, and run analytics reports.

missive_create_analytics_report

Create analytics report

Start generating a Missive analytics report for a time period, with optional team, user, label and account filters. Returns the report id; the data is fetched afterwards with missive_get_analytics_report, usually 5 seconds later. Use missive_create_analytics_report first, then missive_get_analytics_report with the returned id. Requires a Productive or Business plan, and filters require a Business plan. Requires an organization ID plus start and end Unix timestamps.

Parameters

Name

Type

Required

Description

end

integer

Required

End of the report period as a Unix timestamp. Example: 1692371867

organization

string

Required

ID of the organization to report on. Find it with missive_list_organizations. Example: 0d9bab85-a74f-4ece-9142-0f9b9f36ff92

start

integer

Required

Start of the report period as a Unix timestamp. Example: 1691812800

account_types

array

Optional

Account types to include (Business plan): custom, email, instagram, live_chat, messenger, sms or whatsapp. Example: ["email", "sms"]

accounts

array

Optional

Account IDs to include (Business plan). Example: ["716be7a6-fd40-45a2-bfcb-43b9ed38d1f0"]

shared_labels

array

Optional

Shared label IDs to include (Business plan). Example: ["bca0bb8f-8b2f-45f8-a59a-333de84f0184"]

teams

array

Optional

Team IDs to include (Business plan). Example: ["0e24f298-965d-4475-9220-b32636a1e2c3"]

time_zone

string

Optional

IANA time zone used to bucket the report. Example: America/Montreal

users

array

Optional

User IDs to include (Business plan). Example: ["1ce8117e-ae42-4304-b953-c81656da4bd1"]

missive_create_contact

Create contact

missive_create_draft

Create draft

Create an unsent draft email, SMS, WhatsApp, Messenger, Instagram or custom-channel message in Missive, in a new conversation or as a reply to an existing one. Returns the created draft along with the conversation it was placed in; nothing is delivered to the recipient. Use missive_create_draft to prepare a message for review or to schedule it with send_at; use missive_send_message to deliver immediately. Requires a from_field and to_fields for the chosen channel, plus a body; reply by passing conversation or references.

Parameters

Name

Type

Required

Description

account

string

Optional

Account ID for custom channels, Missive Live Chat, Messenger and Instagram. Find it in the channel settings or under Settings > API > Resource IDs in Missive. Example: fbf74c47-d0a0-4d77-bf2c-1b6f6d2e8a3c

add_assignees

array

Optional

User IDs to assign to the conversation; existing assignees stay assigned. Requires organization. Find user IDs with missive_list_users. Example: ["1ce8117e-ae42-4304-b953-c81656da4bd1"]

add_default_signature

boolean

Optional

Set to true to append the sending alias's signature to the body. Email only, and only when the from_field alias has a signature. Example: true

add_shared_labels

array

Optional

Shared label IDs to apply to the conversation. Requires organization. Find label IDs with missive_list_shared_labels. Example: ["9825718b-3407-40b8-800d-a27361c86102"]

add_to_inbox

boolean

Optional

Set to true to move the conversation to the Inbox for everyone who has access to it. Example: true

add_to_team_inbox

boolean

Optional

Set to true to move the conversation to the team inbox. The team field is required when this is true. Example: true

add_users

array

Optional

User IDs to give access to the conversation. Requires organization. Find user IDs with missive_list_users. Example: ["1ce8117e-ae42-4304-b953-c81656da4bd1"]

attachments

array

Optional

Files to attach, up to 25. Each item needs base64_data (base64-encoded file contents) and filename. The whole request must stay under 10 MB. Example: [{"base64_data": "iVBORw0KGgo...", "filename": "logo.png"}]

auto_followup

boolean

Optional

Set to true to discard the scheduled draft if someone replies in the conversation. Requires send_at. Example: false

bcc_fields

array

Optional

Bcc recipients, each an object with address and optional name. Email only. Example: [{"address": "archive@acme.com"}]

body

string

Optional

Body of the message as HTML or plain text. Plain paragraph tags do not add spacing in Missive; use <div> blocks with line breaks for spacing. Example: <div>Hi Paul,</div><div><br></div><div>Thanks for signing up!</div>

cc_fields

array

Optional

Cc recipients, each an object with address and optional name. Email only. Example: [{"address": "boss@acme.com", "name": "Boss"}]

boolean

Optional

Set to true to close the conversation for everyone who has access to it. Example: true

conversation

string

Optional

ID of an existing conversation to add the draft to. Use instead of references when you know the ID. Example: 5bb24363-69e5-48ed-80a9-feee988bc953

conversation_color

string

Optional

Conversation color: a HEX code or one of good, warning or danger. Example: good

conversation_subject

string

Optional

Subject for the conversation when a new one is created. Example: New user!

external_response_id

string

Optional

WhatsApp only: Twilio or Meta ID of the message template to use when starting a conversation with someone you have not talked to in the last 24 hours. Example: 2222222222222222

external_response_variables

object

Optional

WhatsApp only: values for the template placeholders, keyed by placeholder number as strings. Provide a body that matches the interpolated template. Example: {"1": "Philippe", "2": "Order 123"}

force_team

boolean

Optional

Set to true to move the conversation to the given team even if it is already linked to another team. Example: true

from_field

object

Optional

Sender. For email an object with address (must match one of your Missive email aliases) and name. For SMS and WhatsApp an object with phone_number matching one of your account numbers, plus an optional type (signalwire, twilio, twilio_whatsapp or whatsapp). For custom channels an object with id, username and name. Example: {"address": "me@acme.com", "name": "Me"}

organization

string

Optional

ID of the Missive organization the conversation belongs to. Required whenever add_users, add_assignees, remove_assignees or add_shared_labels is used. Find it with missive_list_organizations. Example: 0d9bab85-a74f-4ece-9142-0f9b9f36ff92

quote_previous_message

boolean

Optional

Set to true to include a quoted copy of the last message in the conversation. Be careful: this can leak the previous message's content to the new recipients. Example: false

references

array

Optional

Message-ID strings used to append the draft to an existing conversation. The first matching conversation is used; if none match a new conversation is created. Example: ["<some-reference-123>"]

remove_assignees

array

Optional

User IDs to remove from the conversation's assignees. Requires organization. Example: ["1ce8117e-ae42-4304-b953-c81656da4bd1"]

remove_shared_labels

array

Optional

Shared label IDs to remove from the conversation. Example: ["e4aae78f-e932-40a2-9ece-ed764aa85790"]

send_at

integer

Optional

Unix timestamp at which to send the draft later. Leave empty to leave the draft unsent in Missive. Example: 1684540565

subject

string

Optional

Subject of the email. For replies set it to "Re: <original subject>" so the recipient's mail client threads it correctly. Example: Welcome aboard

team

string

Optional

ID of the team to link the conversation to. Ignored if the conversation already belongs to a team unless force_team is true. Required when add_to_team_inbox is true. Find it with missive_list_teams. Example: 646bb7f1-2066-40be-b8f6-bacb8b3b7419

to_fields

array

Optional

Recipients. For email each item has address and optional name. For SMS and WhatsApp one item with phone_number in +digits format. For Messenger and Instagram one item with id. For custom channels and Missive Live Chat items with id, username and name. Example: [{"address": "paul@acme.com", "name": "Paul"}]

missive_create_post

Post create

Add a post to a Missive conversation, or start a new conversation with one, optionally closing it, assigning users or changing labels at the same time. Returns the post id and the conversation id it was added to. Use missive_create_post for automations that should leave a visible trace in the conversation; use missive_update_conversation for silent state changes and missive_create_draft to send messages. Requires a notification object, plus at least one of text, markdown or attachments.

Parameters

Name

Type

Required

Description

notification

object

Required

Object with title and body strings, used to render the notification for this post. Example: {"title": "New signup", "body": "Paul signed up"}

add_assignees

array

Optional

User IDs to assign to the conversation; existing assignees stay assigned. Requires organization. Find user IDs with missive_list_users. Example: ["1ce8117e-ae42-4304-b953-c81656da4bd1"]

add_shared_labels

array

Optional

Shared label IDs to apply to the conversation. Requires organization. Find label IDs with missive_list_shared_labels. Example: ["9825718b-3407-40b8-800d-a27361c86102"]

add_to_inbox

boolean

Optional

Set to true to move the conversation to the Inbox for everyone who has access to it. Example: true

add_to_team_inbox

boolean

Optional

Set to true to move the conversation to the team inbox. The team field is required when this is true. Example: true

add_users

array

Optional

User IDs to give access to the conversation. Requires organization. Find user IDs with missive_list_users. Example: ["1ce8117e-ae42-4304-b953-c81656da4bd1"]

attachments

array

Optional

Attachments: formatted blocks (color, pretext, author_name, title, title_link, text, markdown, image_url, timestamp, footer, fields) or files with base64_data and filename. The whole request must stay under 10 MB. Example: [{"title": "Plan", "text": "Pro", "color": "good"}]

boolean

Optional

Set to true to close the conversation for everyone who has access to it. Example: true

conversation

string

Optional

ID of an existing conversation to add the post to. Use instead of references when you know the ID. Example: 5bb24363-69e5-48ed-80a9-feee988bc953

conversation_color

string

Optional

Conversation color: a HEX code or one of good, warning or danger. Example: good

conversation_icon

string

Optional

Image URL used as the icon in the conversation list. Example: https://example.com/icon.png

conversation_subject

string

Optional

Subject for the conversation when a new one is created. Example: New user!

force_team

boolean

Optional

Set to true to move the conversation to the given team even if it is already linked to another team. Example: true

markdown

string

Optional

Markdown content of the post, up to 8000 characters. At least one of text, markdown or attachments is required. Example: Paul signed up for the **Pro** plan.

organization

string

Optional

references

array

Optional

Message-ID strings used to append the post to an existing conversation. The first matching conversation is used; if none match a new conversation is created. Example: ["<some-reference-123>"]

remove_assignees

array

Optional

User IDs to remove from the conversation's assignees. Requires organization. Example: ["1ce8117e-ae42-4304-b953-c81656da4bd1"]

remove_shared_labels

array

Optional

Shared label IDs to remove from the conversation. Example: ["e4aae78f-e932-40a2-9ece-ed764aa85790"]

reopen

boolean

Optional

Set to true to keep a closed conversation closed when this post is added, instead of reopening it. Example: true

team

string

Optional

text

string

Optional

Plain-text content of the post, up to 8000 characters. At least one of text, markdown or attachments is required. Example: Paul signed up for the Pro plan.

username

string

Optional

Name shown as the post author instead of the token owner's name. Example: Billing Bot

username_icon

string

Optional

Image URL shown as the post author's avatar. Example: https://example.com/bot.png

missive_create_response

Create response

Create a canned response (reply template) in Missive, shared with an organization or personal to one user. Returns the created response with its id and fields. Use missive_create_response to add a template; use missive_update_response to change an existing one. Requires either an organization ID or a user ID (not both).

Parameters

Name

Type

Required

Description

attachments

array

Optional

Files to attach, each with base64_data and filename, and an optional temporary id for inline images referenced by data-missive-attachment-id in the body. The whole request must stay under 10 MB. On update, send every attachment to keep. Example: [{"base64_data": "iVBORw0KGgo...", "filename": "logo.png"}]

bcc_fields

array

Optional

Default Bcc recipients, each with address and optional name. Example: [{"address": "archive@example.com"}]

body

string

Optional

HTML content of the response. Example: Hello!

cc_fields

array

Optional

Default Cc recipients, each with address and optional name. Example: [{"address": "manager@example.com"}]

external_id

string

Optional

Identifier from another system, for syncing. When set, external_source is required. Example: template-001

external_source

string

Optional

Name of the system the external_id comes from. Required with external_id. Example: knowledge-base

organization

string

Optional

Organization ID for a shared response. Provide either organization or user, not both. Example: 0d9bab85-a74f-4ece-9142-0f9b9f36ff92

share_with_team

string

Optional

Team ID to share the response with. Requires organization. Example: 646bb7f1-2066-40be-b8f6-bacb8b3b7419

shared_labels

array

Optional

Shared label IDs to attach to the response. Requires organization. Example: ["9825718b-3407-40b8-800d-a27361c86102"]

subject

string

Optional

Subject line of the response, up to 500 characters. Example: Welcome!

title

string

Optional

Title of the canned response, up to 500 characters. Example: Welcome email template

to_fields

array

Optional

Default To recipients, each with address and optional name. Example: [{"address": "support@example.com", "name": "Support"}]

user

string

Optional

User ID for a personal response. Provide either user or organization, not both. Example: a41a00fd-453d-49d7-a487-9765c35a3b70

missive_create_shared_label

Create shared label

missive_delete_draft

Delete draft

missive_delete_post

Post delete

missive_delete_response

Delete response

missive_get_analytics_report

Get analytics report

missive_get_contact

Get contact

missive_get_conversation

Get conversation

missive_get_message

Get message

missive_get_response

Get response

missive_list_contact_books

List contact books

missive_list_contact_groups

List contact groups

missive_list_conversation_comments

List conversation comments

missive_list_conversation_drafts

List conversation drafts

missive_list_conversation_posts

List conversation posts

missive_list_conversations

List conversations

List conversations in a Missive mailbox, shared label or team inbox, newest activity first. Returns conversation id, subject, authors, assignees, shared labels, team, message and task counts, last_activity_at and web_url. Use missive_list_conversations to browse or filter by mailbox, label, team or contact; use missive_get_conversation to fetch one conversation by ID. Requires at least one mailbox filter (inbox, all, assigned, closed, snoozed, flagged, trashed, junked, drafts, shared_label, team_inbox, team_closed or team_all).

Parameters

Name

Type

Required

Description

all

boolean

Optional

Set to true to list conversations in the All mailbox.

assigned

boolean

Optional

Set to true to list conversations assigned to the token owner.

closed

boolean

Optional

Set to true to list conversations in Closed.

contact_organization

string

Optional

Contact organization or contact group UUID. Returns conversations with contacts in that organization or group. Mutually exclusive with email and domain. Example: 0d9bab85-a74f-4ece-9142-0f9b9f36ff92

domain

string

Optional

Email domain without the at sign. Returns conversations with contacts from that domain in the From, To, Cc, Bcc or Reply-To headers. Mutually exclusive with email and contact_organization. Example: example.com

drafts

boolean

Optional

Set to true to list conversations in Drafts.

string

Optional

Email address. Returns conversations where this address appears in the From, To, Cc, Bcc or Reply-To headers. Mutually exclusive with domain and contact_organization. Example: user@example.com

flagged

boolean

Optional

Set to true to list starred (flagged) conversations.

inbox

boolean

Optional

Set to true to list conversations in the Inbox. One mailbox filter is required.

junked

boolean

Optional

Set to true to list conversations in Spam (Missive's UI calls it Spam; some email providers call it Junk).

limit

integer

Optional

Maximum number of results to return. Missive's default is 25; the maximum is 50. Example: 25

organization

string

Optional

Organization ID. Restricts results to conversations shared with that organization. Not useful together with shared_label or the team_* filters. Example: 0d9bab85-a74f-4ece-9142-0f9b9f36ff92

shared_label

string

Optional

Shared label ID. Lists the conversations that carry this shared label. Find IDs with missive_list_shared_labels. Example: 9825718b-3407-40b8-800d-a27361c86102

snoozed

boolean

Optional

Set to true to list conversations in Snoozed.

team_all

string

Optional

Team ID. Lists conversations in that team's All mailbox. Example: 0e24f298-965d-4475-9220-b32636a1e2c3

team_closed

string

Optional

Team ID. Lists conversations in that team's Closed mailbox. Example: 0e24f298-965d-4475-9220-b32636a1e2c3

team_inbox

string

Optional

Team ID. Lists conversations in that team's Inbox. Find IDs with missive_list_teams. Example: 0e24f298-965d-4475-9220-b32636a1e2c3

trashed

boolean

Optional

Set to true to list conversations in Trash.

until

integer

Optional

Unix timestamp used to paginate. Pass the last_activity_at of the oldest conversation from the previous page to get the next (older) page. Example: 1692371867

missive_list_organizations

List organizations

missive_list_responses

List responses

missive_list_tasks

List tasks

missive_list_teams

List teams

missive_merge_conversations

Merge conversations

missive_send_message

Send message

Send an email, SMS, WhatsApp, Messenger, Instagram or custom-channel message through Missive immediately, as a new conversation or a reply. Returns the created message and conversation; the message is delivered to the recipients right away and outgoing rules run. Use missive_send_message to deliver now; use missive_create_draft to prepare a message without sending it. Requires a from_field and to_fields for the chosen channel, plus a body; reply by passing conversation or references.

Parameters

Name

Type

Required

Description

account

string

Optional

add_assignees

array

Optional

User IDs to assign to the conversation; existing assignees stay assigned. Requires organization. Find user IDs with missive_list_users. Example: ["1ce8117e-ae42-4304-b953-c81656da4bd1"]

add_default_signature

boolean

Optional

Set to true to append the sending alias's signature to the body. Email only, and only when the from_field alias has a signature. Example: true

add_shared_labels

array

Optional

Shared label IDs to apply to the conversation. Requires organization. Find label IDs with missive_list_shared_labels. Example: ["9825718b-3407-40b8-800d-a27361c86102"]

add_to_inbox

boolean

Optional

Set to true to move the conversation to the Inbox for everyone who has access to it. Example: true

add_to_team_inbox

boolean

Optional

Set to true to move the conversation to the team inbox. The team field is required when this is true. Example: true

add_users

array

Optional

User IDs to give access to the conversation. Requires organization. Find user IDs with missive_list_users. Example: ["1ce8117e-ae42-4304-b953-c81656da4bd1"]

attachments

array

Optional

bcc_fields

array

Optional

Bcc recipients, each an object with address and optional name. Email only. Example: [{"address": "archive@acme.com"}]

body

string

Optional

cc_fields

array

Optional

Cc recipients, each an object with address and optional name. Email only. Example: [{"address": "boss@acme.com", "name": "Boss"}]

boolean

Optional

Set to true to close the conversation for everyone who has access to it. Example: true

conversation

string

Optional

ID of an existing conversation to add the draft to. Use instead of references when you know the ID. Example: 5bb24363-69e5-48ed-80a9-feee988bc953

conversation_color

string

Optional

Conversation color: a HEX code or one of good, warning or danger. Example: good

conversation_subject

string

Optional

Subject for the conversation when a new one is created. Example: New user!

external_response_id

string

Optional

WhatsApp only: Twilio or Meta ID of the message template to use when starting a conversation with someone you have not talked to in the last 24 hours. Example: 2222222222222222

external_response_variables

object

Optional

WhatsApp only: values for the template placeholders, keyed by placeholder number as strings. Provide a body that matches the interpolated template. Example: {"1": "Philippe", "2": "Order 123"}

force_team

boolean

Optional

Set to true to move the conversation to the given team even if it is already linked to another team. Example: true

from_field

object

Optional

organization

string

Optional

quote_previous_message

boolean

Optional

Set to true to include a quoted copy of the last message in the conversation. Be careful: this can leak the previous message's content to the new recipients. Example: false

references

array

Optional

Message-ID strings used to append the draft to an existing conversation. The first matching conversation is used; if none match a new conversation is created. Example: ["<some-reference-123>"]

remove_assignees

array

Optional

User IDs to remove from the conversation's assignees. Requires organization. Example: ["1ce8117e-ae42-4304-b953-c81656da4bd1"]

remove_shared_labels

array

Optional

Shared label IDs to remove from the conversation. Example: ["e4aae78f-e932-40a2-9ece-ed764aa85790"]

subject

string

Optional

Subject of the email. For replies set it to "Re: <original subject>" so the recipient's mail client threads it correctly. Example: Welcome aboard

team

string

Optional

to_fields

array

Optional

missive_update_contact

Update contact

Update an existing Missive contact; only the fields you pass are changed. Returns the updated contact with its infos and memberships. When infos or memberships are passed, items left out of the list are deleted. Use missive_update_contact to edit a contact; use missive_create_contact to add a new one. Requires a contact ID from missive_list_contacts.

Parameters

Name

Type

Required

Description

contact_id

string

Required

ID of the contact to update. Example: ee31f156-db95-4158-923f-b26450e0dbf7

contact_book

string

Optional

ID of the contact book to move the contact to. Leave empty to keep it where it is. Example: 551b8675-11e9-49c3-aac0-01fb8510d862

file_as

string

Optional

Name the contact is filed under. Example: Missive

first_name

string

Optional

Contact's first name. Example: Philippe

gender

string

Optional

Gender of the contact. Example: Male

infos

array

Optional

Contact details such as emails, phone numbers and addresses. Each item needs a kind (email, phone_number, twitter, facebook, physical_address, url or custom) and a label, plus a value (or name for facebook, or street, city and similar fields for physical_address). On update, send the full list because omitted items are deleted. Example: [{"kind": "email", "label": "work", "value": "phil@missiveapp.com"}]

last_name

string

Optional

Contact's last name. Example: Lehoux

memberships

array

Optional

Links to organizations or groups. Each item has a group object with kind (organization or group) and name, and for organizations may also have title, department, location and description. On update, send the full list because omitted items are deleted. Example: [{"title": "CEO", "group": {"kind": "organization", "name": "Missive"}}]

middle_name

string

Optional

Contact's middle name. Example: Antoine

nickname

string

Optional

Nickname. Example: Phil

notes

string

Optional

Free-form notes about the contact. Example: Cool prospect!

prefix

string

Optional

Name prefix. Example: Mr.

starred

boolean

Optional

Set to true to star the contact. Example: true

suffix

string

Optional

Name suffix. Example: Jr.

missive_update_conversation

Update conversation

Update a Missive conversation silently without adding a post: rename, recolor, close, reopen, move to an inbox, assign users or change labels and team. Returns the updated conversation object with its current id, subject, assignees, shared labels and team. Use missive_update_conversation to change state with no visible trace; use missive_create_post when the change should leave a visible note in the conversation. Requires a conversation ID; organization is also required when adding users, assignees or labels.

Parameters

Name

Type

Required

Description

conversation_id

string

Required

ID of the conversation to update. Example: 6d3c9b1c-7067-4a28-8ea6-ea91340b67cc

add_assignees

array

Optional

User IDs to assign to the conversation; existing assignees stay assigned. Requires organization. Find user IDs with missive_list_users. Example: ["1ce8117e-ae42-4304-b953-c81656da4bd1"]

add_shared_labels

array

Optional

Shared label IDs to apply to the conversation. Requires organization. Find label IDs with missive_list_shared_labels. Example: ["9825718b-3407-40b8-800d-a27361c86102"]

add_to_inbox

boolean

Optional

Set to true to move the conversation to the Inbox for everyone who has access to it. Example: true

add_to_team_inbox

boolean

Optional

Set to true to move the conversation to the team inbox. The team field is required when this is true. Example: true

add_users

array

Optional

User IDs to give access to the conversation. Requires organization. Find user IDs with missive_list_users. Example: ["1ce8117e-ae42-4304-b953-c81656da4bd1"]

boolean

Optional

Set to true to close the conversation for everyone who has access to it. Example: true

color

string

Optional

Conversation color: a HEX code or one of good, warning or danger. Example: danger

force_team

boolean

Optional

Set to true to move the conversation to the given team even if it is already linked to another team. Example: true

organization

string

Optional

remove_assignees

array

Optional

User IDs to remove from the conversation's assignees. Requires organization. Example: ["1ce8117e-ae42-4304-b953-c81656da4bd1"]

remove_shared_labels

array

Optional

Shared label IDs to remove from the conversation. Example: ["e4aae78f-e932-40a2-9ece-ed764aa85790"]

reopen

boolean

Optional

Set to true to reopen the conversation for everyone who has access to it. Example: true

subject

string

Optional

New subject for the conversation. Example: Refund approved

team

string

Optional

missive_update_response

Update response

Update an existing Missive canned response; only the fields you pass are changed. Returns the updated response. When attachments are passed, any attachment left out is removed. Responses created by external integrations cannot be updated. Use missive_update_response to edit a template; use missive_create_response to add a new one. Requires a response ID from missive_list_responses.

Parameters

Name

Type

Required

Description

response_id

string

Required

ID of the response to update. Example: 75ad834a-9bd6-4008-b9e6-fc9fa2e7770b

attachments

array

Optional

bcc_fields

array

Optional

Default Bcc recipients, each with address and optional name. Example: [{"address": "archive@example.com"}]

body

string

Optional

HTML content of the response. Example: Hello!

cc_fields

array

Optional

Default Cc recipients, each with address and optional name. Example: [{"address": "manager@example.com"}]

external_id

string

Optional

Identifier from another system, for syncing. When set, external_source is required. Example: template-001

external_source

string

Optional

Name of the system the external_id comes from. Required with external_id. Example: knowledge-base

organization

string

Optional

Organization ID for a shared response. Provide either organization or user, not both. Example: 0d9bab85-a74f-4ece-9142-0f9b9f36ff92

share_with_team

string

Optional

Team ID to share the response with. Requires organization. Example: 646bb7f1-2066-40be-b8f6-bacb8b3b7419

shared_labels

array

Optional

Shared label IDs to attach to the response. Requires organization. Example: ["9825718b-3407-40b8-800d-a27361c86102"]

subject

string

Optional

Subject line of the response, up to 500 characters. Example: Welcome!

title

string

Optional

Title of the canned response, up to 500 characters. Example: Welcome email template

to_fields

array

Optional

Default To recipients, each with address and optional name. Example: [{"address": "support@example.com", "name": "Support"}]

user

string

Optional

User ID for a personal response. Provide either user or organization, not both. Example: a41a00fd-453d-49d7-a487-9765c35a3b70

missive_update_shared_label

Update shared label

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Missive tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["missive"], toolNames: [
    "missive_list_conversations",
    "missive_list_conversation_messages",
    "missive_create_draft"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Draft replies to open conversations in the Support team inbox" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["missive"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Draft replies to open conversations in the Support team inbox" }],
  tools,
});

// Execute the tool call with the user's vaulted Missive access token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["missive"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Draft replies to open conversations in the Support team inbox" }],
  tools,
});

// Tool call runs with the user's vaulted Missive access token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["missive"] }, pageSize: 100,
});

const agent = new Agent({
  name: "inbox_agent",
  model: "gemini-2.5-pro",
  instruction: "Missive tools scoped to this user",
  tools,
});

await agent.run("Draft replies to open conversations in the Support team inbox");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Missive tool. Click to copy, paste into your agent, done.

Conversations

Copy the prompt

Copied

List open conversations in the Support team inbox.

Copy the prompt

Copied

Show the full message thread for the Acme login issue.

Copy the prompt

Copied

Merge the two Globex billing conversations into one.

Replies and drafts

Copy the prompt

Copied

Draft a reply to the latest Acme email using our Refund Policy canned response.

Copy the prompt

Copied

Send an SMS to +14155550123: Your ticket is resolved.

Copy the prompt

Copied

Add a post to the Acme conversation noting the fix shipped.

Tasks and contacts

Copy the prompt

Copied

Create a task to follow up with Globex on Friday.

Copy the prompt

Copied

Add Priya Shah from Initech to our main contact book.

Copy the prompt

Copied

Run an analytics report for the Support team for last week.

SEE HOW AUTH WORKS

Each user connects their own Missive access token once, and Scalekit sends it with every call. Access tokens stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Missive

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Missive

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Missive

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Missive

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other communication and collaboration connectors.

Support and Ops Teams

Support triage agent

Fetches new Zendesk tickets, classifies them by type and urgency, searches the Notion knowledge base for an answer, and routes what it cannot resolve to Slack. Every call runs on the support agent's own delegated OAuth.

Engineering Teams

Slack triage

Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.

Support and Ops Teams

Support ticket automation agent

Fetches new Zendesk tickets, drafts a reply from Notion knowledge base articles, digests what it cannot answer to Slack, and archives the rest, acting as the support agent rather than a shared API key.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Missive access token looks fine in a demo. In production every reply and conversation change looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Missive today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Missive as the user or through a shared access token?

As the user. Each user connects their own Missive access token once, and Scalekit sends it with every call. Audit logs attribute every message, post, and task to that user, not a shared service account.

Where is the Missive access token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new access token. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Missive?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example missive_create_draft without missive_send_message, so a person reviews every reply before it goes out. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Missive access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Which channels can the agent send on through Missive?

missive_send_message and missive_create_draft cover email, SMS, WhatsApp, Messenger, Instagram, and custom-channel messages, using the accounts connected to the user's Missive organization.