ActionMissiveUpdated September 2026
How do I send email via Missive?
Short answer: You can missive send email in Missive by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Missive Missive Send Email action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
To to | Required | To | |
Subject subject | string | Required | Message subject line. |
Body body | html | Required | Message body content. Plain text unless the API specifies HTML/markdown. |
From Alias ID from_alias | string | Optional | Missive email alias to send from |
Sample request
{"to": "{{trigger.from}}","subject": "e.g. Quick update","body": "e.g. Hi there, thanks for reaching out.","from_alias": "{{trigger.from_alias}}"}
Returns
{"drafts": {"id": "draft123","subject": "Hello","delivered_at": "2026-04-11T10:00:00Z"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Missive Send Email.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Missive Send Email.
What does the Missive Send Email action do in Missive?
Composes and sends a new email from a shared inbox, optionally threading into an existing conversation. For Missive-based shared inboxes where the email goes out as the team rather than an individual.
What inputs does Missive Send Email require?
Required: To, Subject, Body. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Missive returns an error?
The run history shows the failed step with its input and the error message Missive returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Missive Send Email support batch operations?
Run Missive Send Email inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Missive's rate limits.
More actions
Other Missive actions.
Action
Create Missive Task
Creates a task (optionally tied to a conversation) with due date and assignee. For "follow up with this customer in 3 days" or "ensure handoff complete" workflows.
ActionList Missive Conversations
Paginated conversations with filters by inbox, label, status. For triage and capacity workflows.
ActionMissive Post Comment
Posts a team-only comment on a conversation thread. For AI-summarised context or escalation handoff notes that teammates see in-thread.