Skip to content
Per-pair page

Connect Slack to AWS SES in two minutes.

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

Trigger app
Slack as the trigger

Workflows fire when something happens in Slack.

See all 13 triggers →
Action app
AWS SES as the action

Workflows do something in AWS SES, instantly.

Both directions

Pick the way that fits your stack.

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

SlackAWS SES

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

13 Slack triggers wired to 2 AWS SES actions. Most-used pairing: App Home OpenedList Verified Identities.

AWS SESSlack

Or fire it the other way around.

0 AWS SES triggers wired to 45 Slack actions downstream.

  • Use any trigger in the catalog as the upstream.
See AWS SESSlack
Popular pairings

Common Slack → AWS SES workflows.

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

Showing 6 of 26 combinations
How it works

Connect Slack and AWS SES in five steps.

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

  1. 1
    Connect
    Authorize Slack and AWS SES

    Open Tiny Command, authorize Slack and AWS SES once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Slack trigger

    Drop the Slack → App Home Opened trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/slack.trigger-app-home-opened
  3. 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. 4
    Action
    Add the AWS SES action

    Drop the AWS SES → List Verified Identities action below it. Map fields from the Slack payload into the AWS SES inputs.

    aws-ses.list-identities
  5. 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 Slack + AWS SES.

How long does it take to connect Slack and AWS SES on Tiny Command?
Under two minutes. Authorize Slack and AWS SES once each, drop the Slack trigger and AWS SES action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Slack ↔ AWS SES integration real-time?
Yes. Both Slack and AWS SES 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 Slack and AWS SES?
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 AWS SES.
What Slack events can trigger a AWS SES workflow?
Any of the 13 Slack triggers, including "App Home Opened". Each fires in real time when the matching event happens in Slack.
Do I need a paid plan to use Slack with AWS SES?
No. There's a free tier that covers most Slack+AWS SES use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want AWS SES → Slack instead?
Build it the same way, in reverse. There's a dedicated /integrations/aws-ses/with/slack page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Slack.


Wire Slack to AWS SES in 2 minutes.

Free tier available. No credit card. No onboarding call.