EmailReal-timeUpdated June 2026

AWS SES integration

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.

Connect AWS SES

No credit card required · Set up in under 2 minutes

0triggers

2actions

≈ 2 minto set up

Freetier · no card

Actions

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	Inputs	Open action
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.	1 input	View
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.	7 inputs	View

Recipes

Pre-built AWS SES workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

AWS SES → Slack alerts

AI-triage every AWS SES event, ping the right channel only when it matters.

AWS SES → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

AWS SES → Notion database

Turn AWS SES into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

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.

No JSON to read

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.

FAQ

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?

Open the Tiny Command workflow builder, drop in a AWS SES node, and click Connect. Authorize AWS SES once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What AWS SES triggers does Tiny Command support?

Tiny Command focuses on outbound actions for AWS SES today. Use Tiny Command's universal Webhook or Schedule trigger to start AWS SES workflows, then run any AWS SES action you need.

What AWS SES actions can I run from a workflow?

2 AWS SES actions are available out of the box, covering email operations like "List Verified Identities". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the AWS SES integration real-time?

AWS SES actions execute synchronously inside your workflow. Tiny Command waits for AWS SES's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use AWS SES with Tiny Command?

No. Every AWS SES trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any AWS SES API endpoint directly.

How much does the AWS SES integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The AWS SES integration itself has no per-app surcharge.