Missive icon

Missive

Work with the Missive API

Actions12

Draft → Create Email

AI-generated

Overview

This node integrates with the Missive API to create and manage email drafts within conversations. Specifically, the Draft - Create Email operation allows users to compose a new email draft with detailed control over recipients, sender information, scheduling, attachments, and conversation context. The node can optionally send the email immediately and close the conversation after sending.

Common scenarios where this node is beneficial include:

  • Automating email drafting and sending workflows in customer support or sales pipelines.
  • Creating scheduled emails linked to specific conversations or teams.
  • Managing email threads programmatically with references and labels.
  • Adding rich attachments and metadata to email drafts.

Practical example:

  • Automatically generate a follow-up email draft for a customer inquiry, specifying the subject, HTML body, recipients (To, CC, BCC), and schedule it to be sent later. Optionally, send it immediately and close the conversation once sent.

Properties

Name Meaning
Subject Subject line of the email.
Body HTML content of the email body.
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 shown in the email.
From Email Email address of the sender.
To List of recipient emails with optional names. Multiple recipients can be added.
CC List of CC recipient emails with optional names. Multiple recipients can be added.
BCC List of BCC recipient emails with optional names. Multiple recipients can be added.
Additional Fields Collection of optional fields to further customize the draft:
- References Comma-separated list of references for threading emails.
- Conversation ID ID of the conversation to create the draft in.
- Conversation Subject Overrides the subject of the conversation.
- Conversation Color Hex color code to set the conversation color (e.g., #FF0000).
- Team ID ID of the team to link the draft's conversation to.
- Force Team Boolean to force a new team even if the conversation belongs to another team.
- Organization ID ID of the organization to scope the conversation to.
- Add Users Comma-separated user IDs to grant access to the conversation.
- Add Assignees Comma-separated user IDs to assign to the conversation.
- Add Shared Labels Comma-separated label IDs to add to the conversation.
- Remove Shared Labels Comma-separated label IDs to remove from the conversation.
- Schedule For DateTime to schedule when the draft should be sent.
- Add to Inbox Boolean to add the conversation to the inbox.
- Add to Team Inbox Boolean to add the conversation to the team inbox.
- Auto Follow-up Boolean to enable auto follow-up for this message.
- Attachments List of attachments to add to the draft. Each attachment includes:
    * Binary Property Name of the binary property containing the attachment data.
    * File Name Filename for the attachment.

Output

The node outputs the JSON response returned by the Missive API after creating the draft. This typically includes details about the created draft such as its ID, status, and metadata.

If attachments are included, they are uploaded as base64-encoded content within the request payload.

No binary output is produced by this node; all data is handled and returned as JSON.

Dependencies

  • Requires an API authentication token credential for the Missive API.
  • The node makes HTTP POST requests to https://public.missiveapp.com/v1/drafts endpoint.
  • Proper configuration of the API key credential in n8n is necessary for authorization.

Troubleshooting

  • Invalid JSON in External Response Variables: If using WhatsApp messaging (not applicable here), malformed JSON in template variables will cause errors. Ensure JSON strings are valid.
  • Missing Required Fields: The node requires at least the "Subject" and "Body" fields for creating an email draft. Omitting these will result in errors.
  • Attachment Issues: Attachments must reference existing binary properties in the workflow. If the binary property name is incorrect or missing, the node will throw an error.
  • API Authentication Errors: Ensure the API token credential is correctly configured and has sufficient permissions.
  • Scheduling Errors: Invalid date/time formats in the "Schedule For" field may cause failures. Use ISO 8601 format.

Links and References

Discussion