Resources · n8n integration

AWS SNS n8n integrationAutomate AWS SNS with n8n.

One message, every subscriber, no loop to maintain. The AWS SNS n8n integration puts 3 topic operations inside your workflows and adds a trigger that catches each notification by webhook. Useful when SNS already carries your alerts and n8n has to react to them.

Try the AWS SNS integration on n8nSee the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the AWS SNS n8n integration actually do?

The AWS SNS n8n integration wires Amazon's notification service into your workflows in both directions. The node sends data to AWS SNS through 3 operations grouped under a single resource: create a topic, delete a topic, publish a message to a topic. The AWS SNS Trigger works the other way, receiving notifications through a webhook, meaning a URL that n8n registers and SNS calls when a message lands.

First scenario, alert fan-out. A workflow collects an incident from your monitoring tool, formats a readable summary, and publishes it to a topic. Everyone subscribed to that topic gets it at once, and the same workflow can mirror the message into Slack for the people who live in a channel rather than in an inbox.

Second scenario, SNS as the entry point. The trigger fires on a topic, the workflow parses the payload and stores a row in Postgres or appends it to a Google Sheets tab for the ops team. That pattern turns a notification stream into an audit trail without writing a consumer service.

Third scenario, short-lived topics. A workflow creates a topic for a migration or a batch job, publishes progress messages to it, then deletes the topic once the job is done. Create and Delete exist precisely for that kind of throwaway plumbing.

When to reach for HTTP Request instead: the node covers topics, not subscriptions. Managing subscribers, listing existing topics or editing topic attributes are not part of the 3 operations, so those calls go through the HTTP Request node, which hits any endpoint of the AWS API while reusing the same AWS credential through predefined authentication.

Known limits, stated plainly. There is one resource and 3 operations, so the node stays narrow on purpose. The trigger listens to a single topic, chosen in its Topic field, and it has no list of event types to tick: every message published to that topic wakes the workflow. Subject is required on Publish even when no subscriber is an email address. If you are still deciding whether the platform fits, the n8n review covers the trade-offs, and the n8n training walks through credentials and expressions from scratch.

Connect

How do you connect AWS SNS to n8n?

  1. 01

    Create an AWS access key

    Log in to the IAM console, select your user name in the navigation bar on the upper right, then Security credentials. In the Access keys section, choose Create access key, pick your use case on the best practices page, and select Other if none of them fits. Set a description tag such as n8n integration so the key stays identifiable, then create it and reveal the Access Key ID and the Secret Access Key.

  2. 02

    Fill the AWS (IAM) credential in n8n

    Open the Credentials menu in n8n and create an AWS (IAM) credential. Select your Region first, then paste the Access Key ID and the Secret Access Key you just revealed. A credential is created once and reused by every workflow on the instance, so the AWS SNS node and the AWS SNS Trigger both pick it from their dropdown list.

  3. 03

    Or assume a role instead of storing keys

    n8n offers a second credential type, AWS (Assume Role), which authenticates by assuming an IAM role through AWS STS. The keys used for the AssumeRole call are either typed in by hand or read automatically from the environment n8n runs in. That second option is the one to take when you self-host n8n on AWS infrastructure such as EKS, ECS or EC2 and would rather keep static keys out of the app.

Triggers

What starts a workflow from AWS SNS ?

AWS SNS Trigger is the node that starts a workflow when AWS SNS calls n8n. Activate the workflow: n8n gives you the webhook URL to register in AWS SNS, and every call becomes an execution.

What you see in n8n

Configuration notes

01Configure the AWS SNS TriggerThe AWS SNS Trigger is version 1 of a webhook node: activating the workflow registers an n8n URL, and AWS SNS calls that URL when a message is published, so the run starts within seconds and nothing polls the API on a timer. Handling AWS SNS events through webhooks is the whole job of this node.

The AWS SNS Trigger is version 1 of a webhook node: activating the workflow registers an n8n URL, and AWS SNS calls that URL when a message is published, so the run starts within seconds and nothing polls the API on a timer. Handling AWS SNS events through webhooks is the whole job of this node.

Key parameters

  • Topic: required, and the only field to fill. It is a resource locator, so you either pick the topic from the list loaded with your credential or paste its value, including an expression such as {{ $json.topic }} when an earlier node decides which topic to listen to.
When to use it
whenever AWS SNS is already the place where your services announce things, and n8n should be one more subscriber rather than a script somebody has to maintain.
Use cases
a deployment pipeline publishes to a topic, the trigger receives it and the workflow opens the follow-up checklist.
02New AWS SNS eventThis trigger exposes a single event, New AWS SNS event, and no list of event types to tick. Every message published to the selected topic produces one execution, with the notification payload available to the nodes that follow. Filtering, if you need it, happens inside the workflow rather than in the trigger settings.

This trigger exposes a single event, New AWS SNS event, and no list of event types to tick. Every message published to the selected topic produces one execution, with the notification payload available to the nodes that follow. Filtering, if you need it, happens inside the workflow rather than in the trigger settings.

When to use it
when the sorting logic belongs to you. Since the trigger does not discriminate between messages, an IF node reading a field of the payload is what separates a routine notification from one that deserves a page.
Use cases
a single operations topic carries backup reports, quota warnings and job failures. The workflow catches all of them, writes each one to a table, and escalates only the failures. Another common shape is one trigger per topic, each in its own workflow, which keeps the routing readable when several teams publish to the same account.
Actions

What can the AWS SNS node do?

The AWS SNS node exposes 3 operations. For each one: the node as you configure it in n8n, the required fields, and our field notes.

01

Create a topic

create

What you see in n8n

Notes & use cases

Creates a new topic in AWS SNS, which is the channel other services subscribe to. The workflow can then publish to it in a later node.

Key parameters

  • Name: required, the name of the topic to create, typed in or built from an expression such as {{ $json.name }} when it depends on incoming data.
  • Display Name: optional, the display name to use for a topic with SMS subscriptions.
  • Fifo Topic: optional boolean that decides whether the topic you create is a FIFO, first-in-first-out topic.
Use cases
a provisioning workflow gives each new environment its own topic, named after the environment, before any service starts publishing to it.
02

Delete a topic

delete

What you see in n8n

Notes & use cases

Removes an existing topic from AWS SNS. The messages stop, and so does everything subscribed to it, which makes this the cleanup end of the node.

Key parameters

  • Topic: required resource locator. Select the topic from the list n8n loads with your AWS credential, or pass its value from an earlier step, typically {{ $json.topic }} when the same workflow created it.
Use cases
a batch job that created a temporary topic at the start deletes it at the end, so the AWS account does not slowly fill with topics nobody reads.
03

Publish a message to a topic

publish

What you see in n8n

Notes & use cases

Sends a message to a topic, and AWS SNS delivers it to every endpoint subscribed to that topic. This is the operation most workflows end on.

Key parameters

  • Topic: required resource locator, the destination of the message.
  • Subject: required, the subject used when the message is delivered to email endpoints.
  • Message: required, the message you want to send, often assembled from earlier nodes with expressions like {{ $json.summary }}.
Use cases
a nightly reconciliation workflow publishes its result once, and subscribers on email and mobile receive the same text without any extra branch in the workflow.
Need help

Need help automating AWS SNS with n8n?

A person reads every message.

FAQ

AWS SNS and n8n, the questions that come next

01Is the AWS SNS n8n integration free to use?
Yes on the n8n side. The AWS SNS node and the AWS SNS Trigger ship with n8n, so there is nothing to install and nothing extra to pay for the connector itself. That holds on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both places, which is what makes moving from a cloud trial to your own server painless later on. What Amazon charges on your AWS account is a separate matter, billed by AWS and not covered here.
02Which credentials or permissions do you need for AWS SNS in n8n?
Two credential types work with this node. AWS (IAM) authenticates with an access key, so you provide your Region, the Access Key ID and the Secret Access Key generated in the IAM console. If the key is temporary, switch on the Temporary security credential option and add the Session token. AWS (Assume Role) is the second type: it authenticates by assuming an IAM role through AWS STS, and the credentials used for that AssumeRole call can be entered by hand or read automatically from the environment n8n runs in. Both credential types cover the node and the trigger, and both are created once then reused everywhere.
03What are the limits of the AWS SNS node in n8n?
The node is deliberately small: one resource and 3 operations, all of them about topics. Creating a topic, deleting a topic and publishing a message to a topic is the full list. Subscription management, listing the topics that already exist and editing topic attributes are not there, so those calls go through the HTTP Request node, which reaches any endpoint of the AWS API while reusing the same AWS credential through predefined authentication. On the trigger side, the limit is scope: one topic per trigger, no event type selection, so message filtering belongs to the workflow logic.
04Does the AWS SNS Trigger work in real time?
Yes. The AWS SNS Trigger is a webhook node, which means n8n exposes a URL and registers it when you activate the workflow, then AWS SNS calls that URL itself as soon as a message is published to the topic. The execution starts within seconds of the message, and nothing checks the API on a schedule, so there is no interval to tune and no delay to accept between two checks. One consequence worth knowing: the workflow has to be active for the URL to be live, so a test run in the editor is not the same thing as a subscription that stays up.
05n8n or Make for AWS SNS?
It depends on where you want the platform to live and how you want to pay for it. Make is hosted by Make, with no self-hosting option, and it is billed per operation, so a chatty topic costs more as volume grows. n8n runs on Cloud or on your own server through Docker or npm, which matters when the notification payloads carry data you would rather keep inside your own infrastructure. Both give you a visual canvas. The honest split is that Make tends to feel quicker on first build, while n8n gives more room for expressions, custom code and hosting control.
Same platform

Other docs you might need on this stack.

Browse all integrations