ActionAWS SQSUpdated June 2026

How do I push a message into an SQS queue?

Short answer: Drop the "AWS SQSSend SQS Message" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Queue URL
queue_url
stringRequiredFull SQS queue URL. Find in SQS console → click queue → URL field.
Message Body
message_body
stringRequiredMessage content. Usually JSON-stringified, but can be any text up to 256 KB.
Delay (seconds)
delay_seconds
numberOptionalHide the message for N seconds before consumers can receive it. 0-900.
Message Group ID
message_group_id
stringOptionalRequired for FIFO queues. Messages in the same group are ordered.
Message Deduplication ID
message_deduplication_id
stringOptionalOptional FIFO dedup — same id within 5 minutes is treated as duplicate.
Sample request
{
"queue_url": "https://sqs.us-east-1.amazonaws.com/123456789012/my-queue",
"message_body": "{{trigger.message_body}}",
"delay_seconds": "{{trigger.delay_seconds}}",
"message_group_id": "{{trigger.message_group_id}}",
"message_deduplication_id": "{{trigger.message_deduplication_id}}"
}
Returns
{
"MessageId": "abc-def-123",
"MD5OfMessageBody": "..."
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Send SQS Message.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Send SQS Message.

What does the Send SQS Message action do in AWS SQS?
Sends a message to a Standard or FIFO queue with optional delay (delay_seconds) for delayed delivery and message_attributes for typed metadata that subscribers can filter on. The standard hook for decoupling: webhook trigger → push to queue → external worker consumes.
What inputs does Send SQS Message require?
Required: Queue URL, Message Body. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if AWS SQS returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Send SQS Message support batch operations?
Yes. Run Send SQS Message inside a Loop node to process arrays. Tiny Command handles AWS SQS's rate limits automatically so you don't have to throttle manually.
More actions

Other AWS SQS actions.

Action
Delete SQS Message
Acknowledges a received SQS message so it doesn't redeliver after the visibility timeout. Must call this within the visibility timeout window or SQS re-delivers the message to another consumer.
Action
Receive SQS Messages
Long-polls the queue for up to 10 messages. Pass wait_time_seconds=20 for full long polling (waits up to 20s for new messages to arrive on quiet queues) — reduces empty-receive costs significantly. Schedule this on a cadence to drain a queue from a workflow.

Send send sqs message from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.