Short answer: You can postmark send email in Postmark by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Postmark Postmark Send Email action to a workflow, map its 7 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
From From | string | Required | Sender email (must be a verified sender signature in Postmark) |
To To | string | Required | Recipient email address (comma-separated for multiple) |
Subject Subject | string | Required | e.g. "e.g. Your order has shipped" |
HTML Body HtmlBody | string | Required | HTML content of the email |
Plain Text Body TextBody | string | Optional | Plain text fallback for email clients that don't render HTML |
Tag Tag | string | Optional | Tag for categorizing this email in Postmark analytics |
Reply-To ReplyTo | string | Optional | Reply-to email address |
{"From": "sender@yourcompany.com","To": "recipient@example.com","Subject": "e.g. Your order has shipped","HtmlBody": "{{trigger.HtmlBody}}","TextBody": "{{trigger.TextBody}}"}
{"To": "recipient@example.com","Message": "OK","ErrorCode": 0,"MessageID": "b7bc2f4a-e38e-4336-af7d-e6c392c2f817","SubmittedAt": "2025-01-15T12:00:00.0000000Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.