Missive icon

Missive

Work with the Missive API

Actions12

Draft → Create SMS & WhatsApp

AI-generated

Overview

This node operation allows you to create a new draft message specifically for SMS or WhatsApp channels within the Missive platform. It supports composing message content, specifying sender and recipient phone numbers, and optionally sending the message immediately or closing the conversation after sending. This is useful in scenarios where you want to automate messaging workflows via SMS or WhatsApp, such as sending notifications, alerts, or customer support messages directly from your automation.

For example, you can use this node to:

  • Draft an SMS notification to multiple recipients and send it immediately.
  • Create a WhatsApp message draft with template variables and schedule it for later delivery.
  • Attach files or images to your SMS or WhatsApp messages.
  • Manage conversation threading and assign messages to specific teams or users.

Properties

Name Meaning
Body Content of the SMS or WhatsApp message to be sent.
Send Boolean flag indicating whether to send the message immediately after creating the draft.
Close Boolean flag indicating whether to close the conversation after sending the message.
From Phone Number The phone number from which the message will be sent (e.g., +18005550199).
Message Type Type of message to send; options are SMS (default) or WhatsApp.
To Phone Numbers Comma-separated list of recipient phone numbers (e.g., +18005550199,+18005550200).
Additional Fields A collection of optional fields to further customize the draft:
- References Comma-separated references for threading messages (e.g., ref1,ref2).
- Conversation ID ID of the conversation to create the draft in.
- Conversation Subject Subject of the conversation, overwriting any existing subject.
- Conversation Color Color code (e.g., #FF0000) to set the conversation color.
- 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 is already assigned 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 (e.g., id1,id2).
- 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 to send the draft message.
- 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.
- External Response ID (WhatsApp only) ID for WhatsApp template responses.
- External Response Variables (WhatsApp only) JSON string defining variables for WhatsApp templates, e.g., {"1":"Variable1","2":"Variable2"}.
- Attachments One or more attachments to include with the message. Each attachment includes:
-- Binary Property Name of the binary property containing the attachment data.
-- File Name Name of the attachment file.

Output

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

If attachments are included, they are uploaded as base64-encoded content within the request but do not affect the output structure beyond what the API returns.

No binary data is output by this node.

Dependencies

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

Troubleshooting

  • Invalid JSON in External Response Variables: If using WhatsApp message type and providing external response variables, ensure the JSON string is valid. Invalid JSON will cause an error. Correct the JSON format to resolve.
  • Missing Required Fields: The properties Body, From Phone Number, and To Phone Numbers are required. Omitting these will result in errors.
  • API Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Attachment Issues: When adding attachments, verify that the binary property exists and contains valid data. Missing or invalid binary data will cause failures.
  • Scheduling Errors: If scheduling a message (Schedule For), ensure the datetime is valid and in the correct format.

Links and References

Discussion