# Missive integrations: conversations and drafts

> Update conversations, create a draft and create a message in Missive, and start a workflow when Missive sends “Incoming email”.

**Canonical page:** https://tray.ai/connectors/missive-integrations/
**Categories:** Communication
**Connects through:** HTTP Connector

## Overview

Missive is a shared team inbox that combines email, SMS and chat channels with internal comments, assignments and tasks on each conversation. Tray.ai connects to Missive through the HTTP Connector, so your workflows can call the Missive API alongside the rest of your stack.

## Use cases

### Conversations

Read and update conversations in Missive from any Tray.ai workflow. The Missive API covers calls such as list conversations and get a conversation.

- List conversations
- Get a conversation
- Update conversations

### Drafts

Create and delete drafts in Missive from any Tray.ai workflow. The Missive API covers calls such as create a draft and send a message.

- Create a draft
- Send a message
- Delete a draft

### Messages

Read and create messages in Missive from any Tray.ai workflow. The Missive API covers calls such as create a message and get a message.

- Create a message
- Get a message
- List messages

### Contacts

Read, create, and update contacts in Missive from any Tray.ai workflow. The Missive API covers calls such as create contacts and update contacts.

- Create contacts
- Update contacts
- List contacts

### Tasks

Read, create, and update tasks in Missive from any Tray.ai workflow. The Missive API covers calls such as list tasks and get a task.

- List tasks
- Get a task
- Create a task

### Posts

Create and delete posts in Missive from any Tray.ai workflow. The Missive API covers calls such as create a post and delete a post.

- Create a post
- Delete a post

## Challenges Tray.ai solves

### Keeping Missive credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Missive credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Missive API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Missive API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Missive?

Yes. Tray.ai connects to Missive through the HTTP Connector, which calls the Missive API directly. Any call the Missive API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Missive?

The Missive API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Missive connector?

Missive runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Missive connector from the Missive API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/