--- title: "Amazon SQS Integration" description: "Send, receive, and delete messages on Amazon SQS standard and FIFO queues. Agents decouple workflow steps, batch-send up to 10 messages at once, long-poll for work, and inspect queue depth." url: https://flowrunner.ai/integrations/sqs-service date_modified: 2026-08-01T02:40:32-07:00 --- # Amazon SQS [Developer Tools](https://flowrunner.ai/integrations/category/developer-infrastructure) Send, receive, and delete messages on Amazon SQS standard and FIFO queues. Agents decouple workflow steps, batch-send up to 10 messages at once, long-poll for work, and inspect queue depth. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 5 actions · API key · available [Amazon SQS website](https://aws.amazon.com/sqs/) · [Platform Documentation](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/welcome.html) · Capability data verified 2026-08-12 1. Upstream event needs to be processed asynchronously, not blocking the producing flow 2. Producer flow assembles the message body and any FIFO group/deduplication IDs 3. Producer calls Send Message (or Send Message Batch for up to 10 messages per request) against the queue URL 4. Consumer flow calls Receive Messages with long polling 5. Consumer processes each message and calls Delete Message with the receipt handle so it is not redelivered 6. Failures logged to a dead-letter queue or audit store for visibility 7. Queue backlog above the threshold or repeated processing failures get routed to the on-call engineer ## What This Integration Enables Agents send messages to a queue URL (with optional Message Group ID and Message Deduplication ID for FIFO ordering), and send up to 10 messages per Send Message Batch with each entry carrying its own id and body. Receive Messages supports long polling via the Wait Time Seconds parameter to reduce empty responses and cost. Visibility timeout keeps received messages hidden from other consumers until they are deleted with their receipt handle. Get Queue Attributes returns all attributes by default or a specified subset such as ApproximateNumberOfMessages and VisibilityTimeout. Queue selection is backed by a live List Queues dictionary so the agent can resolve a queue by name. The connector covers the queue surface a workflow needs; the surrounding flow decides what gets enqueued, what counts as processed, and when a backlog warrants a human. ### Without FlowRunner **Synchronous handoffs**: Producing flows wait for downstream consumers to finish, blocking the original work **Per-message API calls**: Producers send messages one at a time even when 10 are ready **Redelivery confusion**: Consumers that crash mid-process cause messages to redeliver in ways the producer cannot reason about ### With FlowRunner **Decoupled producer and consumer**: Send Message decouples the producing flow from the consumer; the consumer reads on its own cadence **Batched sends**: Send Message Batch handles up to 10 messages per request, with per-entry success and failure lists **Visibility-timeout discipline**: Received messages stay hidden until processed; Delete Message acknowledges them with their receipt handle ## Use Case Scenarios ### Decoupled Producer and Consumer A Slack channel message fires the producer flow. The agent calls Send Message to enqueue the message body for downstream processing. The producer flow completes immediately. A separate consumer flow calls Receive Messages with long polling, processes each message, and calls Delete Message with the receipt handle. The producer and consumer scale independently and the producer never waits on the consumer. ### Fan-Out to Per-Message Processing The agent calls Receive Messages on a notification queue, then for each message calls Publish Message on an SNS topic to broadcast the event to fan-out subscribers. After each successful publish, the agent calls Delete Message to acknowledge the message. The queue absorbs the producer-side bursts; the SNS topic handles the consumer-side fan-out. ### Batch Send From a Source System A spreadsheet row export needs to enqueue work for 10 downstream processors. The agent reads the rows from Google Sheets, then calls Send Message Batch with up to 10 entries per request, each carrying its own id and messageBody. The response splits successful and failed messages so the agent can retry only the failures. ## Human-in-Loop Highlight A queue backlog that keeps growing despite the consumer running is a structural signal. The agent calls Get Queue Attributes on the consumer's queue and watches ApproximateNumberOfMessages. When the backlog crosses the configured threshold or the dead-letter queue starts filling, the agent pauses new producers and posts to the on-call channel: "Queue \[name\] backlog at \[count\] messages. Consumer throughput at \[rate\]. Dead-letter queue at \[dlq-count\]. Add consumers, throttle producers, or pause the flow?" The engineer decides. The agent does the durable thing: it stops adding to a backlog it cannot drain. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 5 actions ### Producer 2 - **Send Message** Sends a single message to a queue. Accepts a Message Group ID (required for FIFO ordering) and a Message Deduplication ID (to prevent duplicates within a 5-minute window). - **Send Message Batch** Sends up to 10 messages to a queue in a single request. Each entry carries its own id and messageBody. The response returns separate lists of successful and failed messages so the agent can retry only the failures. ### Consumer 2 - **Receive Messages** Receives messages from a queue. Wait Time Seconds enables long polling, which reduces empty responses and request costs. Received messages stay hidden from other consumers until the visibility timeout expires. - **Delete Message** Deletes a processed message using its receipt handle so it is not redelivered. Used to acknowledge a message after the consumer has handled it successfully. ### Inspection 1 - **Get Queue Attributes** Returns all queue attributes by default, or a specified subset such as ApproximateNumberOfMessages and VisibilityTimeout. Used to monitor queue depth and configuration. ## Frequently Asked Questions ### What can FlowRunner do with Amazon SQS? FlowRunner agents can run Send Message, Send Message Batch, and Receive Messages in Amazon SQS, plus 2 more actions. ### Does connecting Amazon SQS to FlowRunner require OAuth? No. Amazon SQS connects to FlowRunner with an API key, no OAuth flow required. ### Can Amazon SQS trigger a FlowRunner workflow automatically? Amazon SQS doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Amazon SQS?** This integration exposes Amazon SQS to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/sqs-service. Site index: https://flowrunner.ai/llms.txt