Feature Requests

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.

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

We would like to request the ability to create a rule that snoozes based on business days instead of the full 7-day calendar. For example: If we snooze an item for 2 days on a Friday, we’d like the snooze to end on Tuesday (skipping the weekend), not on Sunday. This would be much more practical for business workflows.

I love how Gmail and other web applications allow you to click an attachment to preview WITHOUT downloading the document. This is particularly useful for Microsoft documents, since the Microsoft applications take forever to open.

Whenever I do a search, Missive would bring back results that are not remotely related. Just wondering if we could remedy that. Thank you.

Currently, "Tasks" are nearly absent in rules except an action to create. To make tasks useful to us, we would like to see improvements such as: Trigger on Create/Complete/Due Date +-= time Actions to Modify Description, Set due date, Assign, Label, Complete etc

It would be great to be able to measure the standard productivity metrics as well as what's in analytics. Things like, time logged on per day for each user, idle time vs active time etc. Also a detailed audit log of each user's activity would be helpful.

Organization labels are available from the API. Individual email account labels should also be accessible.

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).