Feature Requests

When a task is created via the API, it's title is shown as plaintext. We'd have to manually edit the task title (without doing any actual changes) to make it render the markdown properly (i.e links).

Currently, the meta object returned by the List Conversation Comments endpoint only includes metadata in the body of a comment. While helpful, this information can already be extracted by parsing the body manually. To support richer interactions — particularly for bot integrations — it would be immensely helpful to have native support for reactions in the API. We’d greatly appreciate the addition of the following capabilities: 1- Retrieve reactions on a comment or post Ideally, this could be part of the response from the List Conversation Comments endpoint. However, since posts created via the API aren’t retrievable through that endpoint, there should also be a dedicated endpoint such as: GET /posts/{post_id}/reactions or GET /posts/{post_id} (with reactions included in the response) This would be especially useful for collecting user feedback — particularly when combined with a webhook rule (when reacted to a post / comment , enabling seamless and automated feedback workflows. However, it should definetely be available for post , not only for comment 2- React to a comment or post This would allow bots to engage with users more meaningfully — for example, adding a 👀 reaction to a mention. 3- Remove a reaction (optional but nice-to-have) Endpoints like DELETE /posts/{post_id}/reactions/{reaction_id} would round out the feature set. All in all , the following endpoints: GET /posts/{post_id}/reactions POST /posts/{post_id}/reactions DELETE /posts/{post_id}/reactions

Currently, the Missive API does not expose the parent-child relationship between comments — there is no way to determine which comment a given comment is replying to. Additionally, the create post endpoint does not support creating a comment or post as a reply to an existing one. For our bot integration, these features would be extremely valuable for maintaining context and enabling threaded conversations. We’d greatly appreciate support for: 1- Including a parent_id or similar field in the comments API response. 2- Allowing create post to specify a parent_id to create replies programmatically.

Right now the Missive API only supports createTask and updateTask, but there’s no way to retrieve tasks. It would be great to have some basic task read endpoints to make it easier to build integrations and automation around tasks. Some examples of what would be useful: getTaskById(taskId) – fetch a specific task getTasksForUser(userId) – get tasks assigned to a user getTasksInConversation(conversationId) – list tasks for a conversation getTasks(filters?) – retrieve all tasks with optional filters Use case: I’m building a bot that interacts with Missive, and not being able to read tasks is a blocker. These endpoints would open up a lot of possibilities for task-related workflows, reporting, or even simple task viewers. Would love to see this added—thanks! PS: I'd also appreicate if a category for API was created.

Add colors or highlight tasks for better sorting.

Often, I need to read all conversation from beginning to end. But for this purpose, I have to scroll the mouse wheel manually during all conversation to reach beginning of conversation. For some long conversations, it takes very long time. I would love to have a keyboard shortcut to reach beginning of the conversation with one click.

Add more search functions like Tag: (add label/tag to search for) To: and From: (then write the e-mail you want to search for)

Ability to use message data from inbound messages when creating tasks from rules. For example, a rule identifies a message type (sales, customer service, etc) and can apply a label, assign pertinent user and create a task with text like "CUSTOMER SERVICE - {Email Subject}

To get the best out of the CRM we use we sometimes need to forward mails that have come into Missive first. It would be great if it was possible to forward with the original mail from sender so that the CRM will find the mail on the right persons contactcard and add it to the conversations on that customer in our CRM-system. “Forward as original” or “Redirect” feature would solve this accroding to our CRM-partner (GHL).

Most email apps I've used me to drag and drop files from the app straight into another app or website. So I'd expect a file can be pulled from Missive, for example, and dropped straight into an upload prompt on Dropbox or WordPress website. In the current version, however, drag and drop only works from Missive to Finder. Drag it anywhere else and the other app doesn't recognize that I'm trying to drop a file on it. So I have to drag from Missive to Finder, then grab and drag from Finder to the app I need the file in, then go back and delete the app out of Finder because I didn't really need it there in the first place. Would love to eliminate all of those extra steps :D