- Integrations
- /
- AWS SQS
- /
- Actions
- /
- Delete SQS Message
ActionAWS SQSUpdated May 2026
How do I acknowledge a processed SQS message?
Short answer: Drop the "AWS SQS → Delete 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.
| Field | Type | Required | Description |
|---|---|---|---|
Queue URL queue_url | string | Required | A fully qualified URL (https://...) for the queue url. |
Receipt Handle receipt_handle | string | Required | From the ReceiptHandle field on the received message. |
Sample request
{"queue_url": "e.g. https://example.com/path","receipt_handle": "{{trigger.receipt_handle}}"}
Returns
{}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Delete SQS Message.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Delete SQS Message.
What does the Delete SQS Message action do in AWS SQS?
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.
What inputs does Delete SQS Message require?
Required: Queue URL, Receipt Handle. 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 Delete SQS Message support batch operations?
Yes. Run Delete 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
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.
ActionSend SQS Message
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.
Send delete sqs message from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.