Amazon SNS

Publish messages to Amazon SNS topics or send SMS directly. Agents fan workflow events out to many subscribers, manage topics, and subscribe email, SMS, HTTP, SQS, or Lambda endpoints to a topic.

5 actions available

Upstream system signals an event that needs to fan out to multiple subscribers

Agent assembles the message payload and optional subject line for email subscribers

Agent confirms the Topic ARN exists by selecting it from the live List Topics dictionary

Agent calls Publish Message against the topic ARN

Agent stores the returned messageId for traceability

Audit log records the publish event with the topic name and messageId

Sustained subscription-confirmation failures across endpoints get routed to ops for review

What This Integration Enables

Agents publish messages to a topic ARN or directly to a phone number for SMS, with an optional subject line used only for email subscriptions. Topic selection is backed by a searchable dropdown (the List Topics dictionary) so the agent can resolve a topic by name rather than memorizing ARNs. Subscriptions support email, sms, https, http, sqs, lambda, application, and firehose protocols; the response returns a subscription ARN that may read "pending confirmation" for email endpoints until the recipient confirms. Topic creation and deletion fit provisioning flows where a new feature stands up its own notification channel. The connector covers the SNS surface a workflow needs; the surrounding flow decides what gets published, who is subscribed, and when sustained delivery failures warrant a human.

Without FlowRunner

Per-channel notification glue Each event handler ships its own email, SMS, and queue-publish code

Ad-hoc topic management Topics are created and deleted by hand in the console, with no provisioning record

Inconsistent subscription lifecycle Subscriptions are added one-off and rarely cleaned up

With FlowRunner

One publish, many subscribers Publish Message fans an event out to every subscriber on a topic in a single call

Topics provisioned in flow Create Topic and Delete Topic make the topic lifecycle part of the workflow

Subscription lifecycle in flow Subscribe and Unsubscribe make adding and removing endpoints a flow step with an audit trail

Use Case Scenarios

Event Fan-Out to Many Subscribers

A Slack channel message fires the flow. The agent calls Publish Message against an alerts topic ARN. Every subscriber on that topic, whether an email address, a downstream SQS queue, or a Lambda function, receives the message. One publish call replaces N per-subscriber notification calls and keeps the subscriber list as the single source of truth for who hears about a given event.

Direct SMS for Critical Alerts

A monitoring flow detects a threshold breach. The agent calls Publish Message with a phone number instead of a topic ARN, sending an SMS directly to the on-call operator. It then calls Put Item on a DynamoDB table to record the message ID and recipient for audit retention. The on-call person gets a text without a topic and subscription needing to exist between the flow and them.

Provisioned Notification Channel for a New Feature

When a new feature launches, the agent calls Create Topic to stand up the feature's notification channel, then calls Subscribe for each endpoint the feature needs (an SQS queue for downstream processing, a Lambda for analytics, an email distribution list for ops). When the feature is retired, the agent calls Unsubscribe for each subscription and Delete Topic. The channel's lifecycle lives in the workflow, not in tribal knowledge.

Human-in-Loop Highlight

A wave of pending-confirmation subscriptions across email endpoints, or a sustained delivery-failure rate against an HTTP endpoint, is a signal that something structural is off. The agent watches the subscription ARNs returned by Subscribe and the downstream delivery indicators. When pending confirmations cross the threshold within the configured window, or HTTPS delivery failures spike, the agent posts to the ops channel: "[count] subscriptions on topic [name] are still pending confirmation after [window]. Resend confirmation, escalate to channel owners, or pause new subscriptions?" The operator decides. The agent does the durable thing: it stops adding subscriptions that are likely to be dropped silently.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

5 actions

Publish

Publish Message Publishes a message to a topic ARN to fan out to every subscriber, or sends an SMS directly to a phone number. The optional Subject line is used only for email subscriptions. Returns a messageId for traceability.

Topics

Create Topic Creates a new SNS topic. Used in provisioning flows that stand up a notification channel for a new feature.
Delete Topic Deletes an SNS topic. Used in tear-down flows when a feature is retired. Topic selection is backed by a searchable dropdown of your topics in the configured region.

Subscriptions

Subscribe Subscribes an endpoint (email, sms, https, http, sqs, lambda, application, or firehose) to a topic. Returns a subscription ARN that may read "pending confirmation" for email endpoints until the recipient confirms.
Unsubscribe Removes a subscription from a topic. Used in tear-down and access-control flows.

Start building with Amazon SNS

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us