Short answer: You can send email via ses in AWS SES by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the AWS SES Send Email via SES 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 Address from | string | Required | Verified SES sender address. Optionally include display name: "Acme <no-reply@acme.com>". |
To Address(es) to | string | Required | Comma-separated list of recipient emails. |
Subject subject | string | Required | Message subject line. |
HTML Body body_html | string | Optional | HTML email body. At least one of body_html or body_text is required. |
Text Body body_text | string | Optional | Plain text fallback. Recommended for deliverability. |
Reply-To reply_to | string | Optional | Optional Reply-To address. Comma-separated for multiple. |
Configuration Set configuration_set | string | Optional | Optional SES configuration set for event tracking. |
{"from": "no-reply@yourdomain.com","to": "recipient@example.com","subject": "Your order confirmation","body_html": "{{trigger.body_html}}","body_text": "{{trigger.body_text}}"}
{"MessageId": "0100018be-abc123-def4-5678-..."}
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.