ActionMissiveUpdated May 2026

How do I create a Missive task?

Short answer: Drop the "Missive → Create Missive Task" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 4 Missive actions

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
Team ID team	string	Optional	—
Description description	string	Required	—
State state	options	Optional	—

Sample request

{
  "team": "{{trigger.team}}",
  "description": "{{trigger.description}}",
  "state": "{{trigger.state}}"
}

Returns

{
  "tasks": {
    "id": "task_abc",
    "state": "todo",
    "description": "Follow up"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Create Missive Task.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Missive

2 Google Sheets triggers

HubSpot → Missive

18 HubSpot triggers

FAQ

Questions about Create Missive Task.

What does the Create Missive Task action do in Missive?

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.

What inputs does Create Missive Task require?

Required: Description. 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 Create Missive Task support batch operations?

Yes. Run Create Missive Task 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