Resources · n8n integration

AWS SQS n8n integrationAutomate AWS SQS with n8n.

Queues are where a workflow stops waiting. The AWS SQS n8n integration ships 1 operation, Send Message, on a node with no resource to choose first. There is no SQS trigger, so the workflow starts elsewhere and ends in the queue. Written for builders who already run SQS.

Try the AWS SQS integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the AWS SQS n8n integration actually cover?

The AWS SQS node sends messages to a queue, and that is the whole surface: 1 operation, 1 synthetic resource, no events to subscribe to. n8n handles the AWS signing with a credential you create once, loads your queues into a dropdown, and lets you fill the message body from the item that entered the node. Everything downstream, the consumer that reads the queue and deletes the message, stays on your side of AWS.

Three shapes of workflow come back constantly with this node.

The first is buffering. A workflow that polls an API on a timer can drop each result into a queue instead of writing it straight to storage, so a slow or flaky consumer never blocks the collection side. The public template that sends the position of the ISS to a queue every minute (workflow 1047, HTTP Request then AWS SQS) is the smallest honest version of that pattern.

The second is handing work off. A form submission, a Slack command or a webhook can start a job that takes far longer than an n8n execution should. Send the payload to SQS, let a worker pick it up, and the workflow finishes in milliseconds. The same trick fans work out to several consumers without n8n knowing how many there are.

The third is ordering. On a FIFO queue, Message Group ID decides which messages have to stay in sequence relative to each other, so per customer or per account updates arrive in the order they were produced while unrelated groups still run in parallel. Message Deduplication ID covers the retry case on the same queue type, and Delay Seconds holds a message back before any consumer can see it.

Prefer the HTTP Request node for anything the dedicated node does not expose: it stops at the send side, and HTTP Request reaches the rest of the SQS API with the same AWS credential through predefined authentication.

Two limits are worth knowing before you build. There is no AWS SQS trigger in n8n, so nothing here reacts to a message arriving; the workflow starts with a Schedule Trigger, an n8n Webhook, or another tool's trigger, and SQS sits at the end. And the node writes one message per execution item, so a batch read from Postgres or Google Sheets turns into as many sends as there are rows. Our n8n training covers that batching habit in more depth.

Connect

How do you connect AWS SQS to n8n?

  1. 01

    Create an access key in IAM

    Open the IAM console, select your user name in the upper right, then Security credentials. In the Access keys section, choose Create access key, pick a use case (or Other if none fits), and set a description tag such as n8n integration so you can recognize the key later. Reveal the Access Key ID and the Secret Access Key: the secret is shown once.

  2. 02

    Store it as an AWS credential in n8n

    In n8n, add an AWS (IAM) credential. A credential is a saved set of connection details that every workflow can reuse from a dropdown. Select your AWS Region first, since the queue list depends on it, then paste the two keys. If you work with short-lived keys, turn on Temporary security credential and add the Session token that came with them.

  3. 03

    Or assume a role instead of storing keys

    n8n also offers an AWS (Assume Role) credential, which authenticates by assuming an IAM role through AWS STS. The keys used for the AssumeRole call are either typed in or read automatically from the environment n8n runs in. That second option is the one to pick when you self-host n8n on EKS, ECS or EC2 and would rather not keep static keys inside the instance at all.

Actions

What the AWS SQS node can do

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

01

Send a message to a queue

sendMessage

What you see in n8n

Notes & use cases

The node's only operation. It posts one message to the queue and returns the SQS response, so the execution moves on without waiting for a consumer.

Key parameters

  • Queue Name or ID: choose from the list n8n loads from your account, or pass an ID with an expression like {{ $json.queue }}.
  • Message: the body that reaches the queue. Switch on Send Input Data to forward the incoming item as JSON instead.
  • Message Group ID: required by the node, but only read by FIFO queues, where it groups the messages that must stay in order.
Use cases
queue an order for a billing worker, or push each row of a nightly export so a separate service handles the slow part.
Need help

Need help automating AWS SQS with n8n?

A person reads every message.

FAQ

AWS SQS and n8n, common questions

01Is the AWS SQS n8n integration free to use?
Yes on the n8n side. The AWS SQS node ships with n8n, on n8n Cloud and on a self-hosted instance under the Community Edition and its Sustainable Use license, so there is nothing to install and no extra n8n charge for using it. What AWS bills you for the queue itself is a separate matter and depends on your own account, so check that in your AWS console rather than here. The credential you create is reusable too: the same AWS (IAM) or AWS (Assume Role) entry serves this node and the other AWS nodes in n8n without being set up again.
02What AWS credentials does the n8n SQS node need?
One of two types. AWS (IAM) authenticates with an access key, which means your AWS Region, an Access Key ID and a Secret Access Key generated in the IAM console. AWS (Assume Role) instead assumes an IAM role through AWS STS, and the keys used for that AssumeRole call can be entered by hand or read automatically from the environment n8n runs in. If you self-host n8n on AWS infrastructure such as EKS, ECS or EC2, the second type is what lets you avoid storing static keys in n8n at all. Short-lived keys work too, through the temporary security credential option and its session token.
03What are the limits of the AWS SQS node in n8n?
It only sends. The node exposes a single operation, Send Message, so anything else on SQS falls outside it. For that, the HTTP Request node calls any SQS endpoint and reuses the same AWS credential through predefined authentication, which keeps the key in one place. Two parameters also behave in a way worth remembering: Message Group ID is marked required by the node even though only FIFO queues read it, and Message Deduplication ID applies to FIFO queues as well. On a standard queue you fill the group field and SQS ignores it.
04Can n8n react to a new message in an SQS queue?
No, not with this node. There is no AWS SQS trigger in n8n, so a workflow cannot wake up because a message arrived. The workflow starts somewhere else and SQS sits at the end of it: a Schedule Trigger firing at a fixed interval, an n8n Webhook called by another service, or the trigger of a different tool in your setup. If something really has to consume the queue, that consumer lives on the AWS side and can call an n8n Webhook when it has finished a batch. Plan the direction before you build, because it decides where the workflow begins.
05n8n or Make for AWS SQS?
It depends on where you want the automation to run. Make is hosted by Make, with no self-hosting option, and it bills per operation, which suits teams that do not want to run anything themselves. n8n can be self-hosted with Docker or npm, or used on n8n Cloud, and a workflow behaves the same either way, so the queue payloads never have to leave infrastructure you control. Since SQS usually sits between systems that are already yours, that hosting question tends to decide it. Cost model and visual logic differ too, and both platforms build the same queue flows.
Same platform

Other docs you might need on this stack.

Browse all integrations