Per-pair page

Connect AWS SES to Slack in two minutes.

Real-time triggers from AWS SES, ready-made actions in Slack. Filter, transform, and route without writing a line of code.

Connect AWS SES and Slack See reverse direction

Trigger app

AWS SES as the trigger

Workflows fire when something happens in AWS SES.

AWS SES has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

AWS SES → Slack

When something happens in AWS SES, do it in Slack.

0 AWS SES triggers wired to 45 Slack actions.

Slack → AWS SES

Or fire it the other way around.

13 Slack triggers wired to 2 AWS SES actions downstream.

See Slack → AWS SES →

Popular pairings

Common AWS SES → Slack workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 0 of 0 combinations

How it works

Connect AWS SES and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize AWS SES and Slack
Open Tiny Command, authorize AWS SES and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a AWS SES trigger
Drop the AWS SES → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/aws-ses.event
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Slack action
Drop the Slack → Raw API Request action below it. Map fields from the AWS SES payload into the Slack inputs.
slack.api-request
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about AWS SES + Slack.

How long does it take to connect AWS SES and Slack on Tiny Command?

Under two minutes. Authorize AWS SES and Slack once each, drop the AWS SES trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the AWS SES ↔ Slack integration real-time?

Yes. Both AWS SES and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between AWS SES and Slack?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.

What AWS SES events can trigger a Slack workflow?

Use Tiny Command's universal Webhook trigger to receive AWS SES events, then run any of the 45 Slack actions downstream.

Do I need a paid plan to use AWS SES with Slack?

No. There's a free tier that covers most AWS SES+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Slack → AWS SES instead?

Build it the same way, in reverse. There's a dedicated /integrations/slack/with/aws-ses page with the reverse-direction triggers and actions.

Other apps that pair well with AWS SES.

AWS SES + Gmail

AWS SES + Google Sheets

Spreadsheets & Databases