missive_create_post
Create a post in a Missive conversation to inject content and manage conversation state such as closing, reopening, assigning users, and adding labels.
Instructions
Creates a post in a Missive conversation (POST /posts). A post is the recommended way for an automation to inject content and manage conversation state (close/reopen, move to inbox, assign users, add labels, set color) while leaving a visible trace. WARNING: the post is PERMANENT and VISIBLE to everyone with access to the conversation, creating it can send NOTIFICATIONS to those people, and it CANNOT be undone through this server (no delete tool is exposed). At least one of text, markdown, or attachments is required. If no conversation or matching references is given, a new conversation is created.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| team | No | Team ID to link the conversation to. Required when add_to_team_inbox is true. | |
| text | No | Main message of the post as plain text (max 8000 chars). At least one of text, markdown, or attachments is required. | |
| close | No | If true, close the conversation for everyone with access. | |
| reopen | No | If true, keep a closed conversation closed even after adding this post (prevents auto-reopen). | |
| markdown | No | Main message of the post formatted with Markdown (max 8000 chars). At least one of text, markdown, or attachments is required. | |
| username | No | Name of the post author, used instead of the API token owner's name. | |
| add_users | No | User IDs to grant access to the conversation. Requires `organization`. | |
| force_team | No | If true, move the conversation to `team` even if it is already in another team. | |
| references | No | Reference strings (e.g. email Message-ID values) used to append the post to an existing conversation; chevrons are optional. If none match, a new conversation is created. | |
| attachments | No | Array of attachment objects: either formatted blocks (color/title/text/fields/etc.) or binary file attachments ({ base64_data, filename }). At least one of text, markdown, or attachments is required. | |
| add_to_inbox | No | If true, move the conversation to Inbox (unarchive) for everyone with access. | |
| conversation | No | ID of an existing conversation to append this post to. If omitted (and no matching references), a new conversation is created. | |
| notification | No | Optional notification object with `title` and `body`, used to render the notification shown to recipients. | |
| organization | No | Organization ID. Required when using add_users, add_assignees, or remove_assignees. Also scopes conversation search and links a newly created conversation to the organization. | |
| add_assignees | No | User IDs to assign to the conversation (existing assignees remain). Requires `organization`. | |
| username_icon | No | Image URL of the post author, used instead of the API token owner's avatar. | |
| remove_assignees | No | User IDs to unassign from the conversation. Requires `organization`. | |
| add_shared_labels | No | Shared label IDs to apply to the post's conversation. | |
| add_to_team_inbox | No | If true, move the conversation to a team inbox for everyone with access. Requires `team`. | |
| conversation_icon | No | Image URL used as the icon in the conversation list. | |
| conversation_color | No | Conversation color: a HEX code (e.g. "#000") or one of "good", "warning", "danger". | |
| conversation_subject | No | Subject for the conversation, e.g. "New user!". | |
| remove_shared_labels | No | Shared label IDs to remove from the post's conversation. |