Actions12
Overview
This node operation creates a new email draft in Missive, optionally sending it immediately and managing conversation state. It supports specifying email details such as subject, HTML body, sender information, recipients (To, CC, BCC), and various conversation-related options like threading references, conversation ID, subject, color, team, organization, scheduling, and labels. Attachments can be included as base64-encoded files. This node is useful for automating email draft creation and sending within workflows, for example, sending notification emails or managing customer support conversations.
Properties
| Name | Meaning |
|---|---|
| Subject | Subject line of the email, required for the draft creation. |
| Body | HTML content of the email body, required for the draft creation. |
| Send | Boolean flag indicating whether to send the email immediately after creating the draft. |
| Close | Boolean flag indicating whether to close the conversation after sending the email. |
| From Name | Name of the sender to appear in the email's From field. |
| From Email | Email address of the sender to appear in the email's From field. |
| To | List of recipient emails with optional names for the To field. |
| CC | List of recipient emails with optional names for the CC field. |
| BCC | List of recipient emails with optional names for the BCC field. |
| Additional Fields | Collection of optional fields to control threading, conversation details, team and organization scoping, scheduling, inbox placement, follow-up, and attachments. |
Output
JSON
json- Response object from Missive API containing details of the created draft email.
Dependencies
- Missive API with an API token credential
Troubleshooting
- Ensure the API token credential is valid and has necessary permissions to create drafts.
- Verify that required fields like Subject and Body are provided; missing these will cause errors.
- Attachments must reference existing binary data in the workflow; invalid binary property names will cause failures.
- If scheduling is used, ensure the date/time format is correct and supported by the API.
- For JSON fields like references or user IDs, ensure correct formatting (e.g., comma-separated lists).
- If sending immediately, network or API errors may occur; check connectivity and API status.
Links
- Missive API Documentation - Official API documentation for Missive, detailing endpoints and data formats.