ActionButtondownUpdated September 2026
How do I create a Buttondown email?
Short answer: You can create email / draft in Buttondown by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Buttondown Create Email / Draft action to a workflow, map its 3 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 |
|---|---|---|---|
Subject subject | string | Required | Message subject line. |
Body body | html | Required | Message body content. Plain text unless the API specifies HTML/markdown. |
Status status | options | Optional | Status. Options: Draft, Send Now |
Sample request
{"subject": "e.g. Quick update","body": "e.g. Hi there, thanks for reaching out.","status": "{{trigger.status}}"}
Returns
{"id": "email123","status": "draft","subject": "Weekly Newsletter","creation_date": "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 Create Email / Draft.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Create Email / Draft.
What does the Create Email / Draft action do in Buttondown?
Creates an email — as draft for review, scheduled for later, or about_to_send for immediate delivery. Useful for "auto-publish from a Git-committed markdown file" workflows or for scheduled newsletter automation tied to publication cadence.
What inputs does Create Email / Draft require?
Required: 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 Buttondown returns an error?
The run history shows the failed step with its input and the error message Buttondown 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 Create Email / Draft support batch operations?
Run Create Email / Draft 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 Buttondown's rate limits.
More actions