Short answer: Drop the "AWS SQS → Send SQS Message" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Queue URL queue_url | string | Required | Full SQS queue URL. Find in SQS console → click queue → URL field. |
Message Body message_body | string | Required | Message content. Usually JSON-stringified, but can be any text up to 256 KB. |
Delay (seconds) delay_seconds | number | Optional | Hide the message for N seconds before consumers can receive it. 0-900. |
Message Group ID message_group_id | string | Optional | Required for FIFO queues. Messages in the same group are ordered. |
Message Deduplication ID message_deduplication_id | string | Optional | Optional FIFO dedup — same id within 5 minutes is treated as duplicate. |
{"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}}"}
{"MessageId": "abc-def-123","MD5OfMessageBody": "..."}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.