Where is SQS in Pipedream?

Inside the shared AWS app (aws), as the SQS - Send Message action. There is no separate SQS app.

What can the n8n AWS SQS node do?

Send a message to a standard or FIFO queue, with options for delay, message attributes, and for FIFO queues the message group ID and deduplication ID.

Can n8n read messages from a queue?

There is no SQS trigger node. Poll with a Schedule Trigger and an HTTP Request (or AWS SDK call in a Code node) to ReceiveMessage and DeleteMessage, or let a Lambda forward messages to an n8n Webhook.

Do SQS steps convert automatically?

No. They arrive as placeholders with their props (queue URL, message body), and the report lists the AWS credential to create.

Pipedream AWS SQS steps in n8n

Updated 2026-10-21 · 3 min read · n8n: AWS SQS (Native n8n node)

SQS steps in Pipedream hand work off to backend services: a webhook arrives, the workflow validates it and drops a message on a queue that a worker consumes. n8n has a native AWS SQS node that sends messages; consuming a queue needs a small polling pattern.

The n8n side

AWS SQS node (n8n-nodes-base.awsSqs), operation Send Message:

Queue: picked from a list (standard or FIFO).
Send Input Data as the body, or a custom Message.
Options: Delay Seconds, Message Attributes (string, number, binary).
FIFO queues: Message Group ID (required) and Message Deduplication ID.

There is no SQS trigger node.

What maps where

Pipedream (app `aws`)	In n8n	Status
SQS - Send Message	AWS SQS → Send Message	manual
SNS - Send Message	AWS SNS → Publish	manual
Lambda - Invoke Function	AWS Lambda → Invoke	manual
S3 - Upload Files	AWS S3 → File → Upload	manual
Code step with `@aws-sdk/client-sqs`	Code node (self-hosted, package allowed) or the SQS node	review

Pipedream's AWS app is not in the converter's mapped list. Each SQS step arrives as a placeholder with its props (region, queue URL, message body) in a comment, and the report lists one AWS credential for the workflow.

AWS SQS credentials in n8n

The AWS (IAM) credential (type aws): Region, Access Key ID, Secret Access Key, optional session token for temporary credentials, and custom endpoints. n8n also offers an AWS (Assume Role) credential that gets temporary credentials via STS. Give the IAM user or role sqs:SendMessage on the queue and sqs:ListQueues so the node can list queues.

Consuming a queue

Schedule Trigger every minute.
HTTP Request with the AWS credential to https://sqs.<region>.amazonaws.com/ (n8n derives the signing service from the hostname) calling ReceiveMessage with MaxNumberOfMessages=10 and WaitTimeSeconds up to 20.
Process each message.
Call DeleteMessage with the receipt handle, or the message reappears after the visibility timeout.

For instant delivery, an SQS-triggered Lambda that POSTs each message to an n8n Webhook avoids polling.

Typical migration: webhook to queue

Pipedream: HTTP trigger → filter → SQS - Send Message (orders.fifo, group ID = customer ID). n8n: Webhook → If → AWS SQS → Send Message (Queue orders.fifo, Message Group ID {{ $json.body.customerId }}, Deduplication ID = order ID). Respond to Webhook after the send if the caller waits for confirmation.

AWS SQS migration pitfalls

Message size. SQS messages are limited in size (check the current quota in the AWS docs); store large payloads in S3 and send the key.
FIFO requirements. FIFO queues need a group ID and either a deduplication ID or content-based deduplication on the queue.
Region. The credential's region must match the queue's region.
Attributes. Pipedream props sometimes hold attributes as JSON; in n8n add them one by one with their data type.

How to move your SQS workflows

Export from Pipedream.
Upload on /convert; the free report lists every AWS step and its props.
Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the code step checker for AWS SDK code. Related: AWS Lambda, AWS S3, PostgreSQL.

FAQ

Where is SQS in Pipedream?: Inside the shared AWS app (aws), as the SQS - Send Message action. There is no separate SQS app.
What can the n8n AWS SQS node do?: Send a message to a standard or FIFO queue, with options for delay, message attributes, and for FIFO queues the message group ID and deduplication ID.
Can n8n read messages from a queue?: There is no SQS trigger node. Poll with a Schedule Trigger and an HTTP Request (or AWS SDK call in a Code node) to ReceiveMessage and DeleteMessage, or let a Lambda forward messages to an n8n Webhook.
Do SQS steps convert automatically?: No. They arrive as placeholders with their props (queue URL, message body), and the report lists the AWS credential to create.