Missive Send Email: Missive action

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	email	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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Missive Send Email support batch operations?

Yes. Run Missive Send Email inside a Loop node to process arrays. Tiny Command handles Missive's rate limits automatically so you don't have to throttle manually.

More actions