Short answer: You can postmark send template email in Postmark by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Postmark Postmark Send Template 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 |
|---|---|---|---|
Template ID TemplateId | string | Optional | Numeric ID of the Postmark template, or use Template Alias instead |
Template Alias TemplateAlias | string | Optional | String alias of the template (alternative to Template ID) |
From From | string | Required | Sender email (must be a verified sender signature) |
To To | string | Required | Recipient email address |
Template Variables (JSON) TemplateModel | string | Optional | JSON object with template variable values, e.g. {"name": "John", "product": "Acme"} |
Tag Tag | string | Optional | Tag for categorizing this email in Postmark analytics |
Reply-To ReplyTo | string | Optional | Reply-to email address |
{"TemplateId": "e.g. 12345","TemplateAlias": "e.g. welcome-email","From": "noreply@yourcompany.com","To": "recipient@example.com","TemplateModel": "{\"name\": \"John\", \"action_url\": \"https://example.com\"}"}
{"To": "recipient@example.com","Message": "OK","ErrorCode": 0,"MessageID": "abc-123-def-456","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.