AWS SES
AWS SES bulk transactional email
AWS SES (Simple Email Service) is the AWS-native email-sending service — used for transactional and bulk email at AWS-native cost (much cheaper per email than SendGrid/Mailgun for high volume), with the trade-off being more operational responsibility (you manage your sender reputation, set up bounce/complaint handling). Tiny Command exposes two actions, no triggers (SES bounce/complaint events fire via SNS topics; for "react to bounce" workflows, SNS-to-Tiny-Command webhook trigger via subscription): Send Email (single recipient with HTML/text body, attachments, headers), List Verified Identities (the verified sender email addresses and domains — SES requires sender verification before allowing sends). The connection uses AWS IAM credentials with ses:SendEmail permissions plus the region. SES is typically the right choice for orgs already in AWS that want cheap email at scale; new green-field projects often start with Resend/Postmark/SendGrid for the easier developer experience and only move to SES at high volume.
Do anything AWS SES can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| List Verified Identities | Returns every verified sender email/domain in the connected SES region. SES blocks sends from unverified identities, so this is the pre-flight check before Send Email — confirm the from-address is verified or your sends will silently fail. |
| Send Email via SES | Sends a transactional or bulk email through SES. Requires the from-address to be verified. SES pricing is dramatically cheaper than SendGrid/Mailgun at scale (~$0.10 per 1000 emails) — the trade-off is more operational responsibility around bounce/complaint handling and reputation management. |
Pre-built AWS SES workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect AWS SES once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every AWS SES field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the AWS SES integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect AWS SES to Tiny Command?
What AWS SES triggers does Tiny Command support?
What AWS SES actions can I run from a workflow?
Is the AWS SES integration real-time?
Do I need to write code to use AWS SES with Tiny Command?
How much does the AWS SES integration cost?
More email apps people connect.
Same category as AWS SES, ordered by how often teams pair them. Hover the carousel to pause.
Do more with AWS SES.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
