Short answer: Drop the "AWS SQS → Delete 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 | A fully qualified URL (https://...) for the queue url. |
Receipt Handle receipt_handle | string | Required | From the ReceiptHandle field on the received message. |
{"queue_url": "e.g. https://example.com/path","receipt_handle": "{{trigger.receipt_handle}}"}
{}
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.