Academy
⌘K
Getting Started
  • Platform Overview
  • AWS Marketplace Setup
  • Quickstart Guide
Connections
  • Overview
Workflow Builder
  • Overview
  • Nodes Catalog
Helix AI Assistant
  • Overview
Mapping Engine
  • Overview
Workflow Library
  • Overview
  • HL7
  • FHIR
  • Insurance
  • Agentic
  • Mapping
Security & Infrastructure
  • Architecture
  • HIPAA Compliance
  • Performance & Scalability
← Back to ConnectHealth
Get Started
Back to Nodes
AWS1 input → 2 outputs

SQS Delete

payload.queueUrl (string)payload.receip… (string)payload.receip… (array)payload.messages (array)AWSSQS DeleteOutput 1payload.success (boolean)payload.deleted (number)payload.failed (number)Output 2payload.success (boolean)payload.error (string)payload.errorT… (string)Data flowProperty

Deletes one message, or many messages in a single batch call, from an SQS queue using their receipt handle(s). This permanently removes the message(s) from the queue — call it only after the message has been fully processed.

Inputs

payload.queueUrl string
Overrides the Queue URL set in the node config.
payload.receiptHandle string
Single delete. The receipt handle of the message to delete. Overrides the node's static Receipt Handle.
payload.receiptHandles array
Batch delete. Array of receipt-handle strings, or objects { receiptHandle, id? }.
payload.messages array
Batch delete. Array of message-like objects, e.g. straight from SQS Receive's msg.payload.Messages: { ReceiptHandle, MessageId }.
payload (whole message) array
Batch delete. If msg.payload itself is an array, it is treated the same as payload.messages.

Batch mode is chosen automatically whenever any of the three array shapes above is present; otherwise the node performs a single delete using payload.receiptHandle (or the node's static Receipt Handle).

Outputs

Output 1 — Success
payload.success boolean
Single delete: always true. Batch delete: true only if every entry succeeded.
payload.deleted number
Count of messages successfully deleted (1 for single delete).
payload.failed number
Batch delete only — count of entries that failed.
payload.Successful / payload.Failed array
Batch delete only — raw per-entry results from DeleteMessageBatch.
sqs.operation string
"delete" or "deleteBatch"
sqs.queueUrl string
The queue that was targeted.
Output 2 — Error
payload.error string
Error message from AWS, or (batch) a summary when every entry failed.
payload.errorType string
Human-readable error category (e.g. Queue Not Found, Auth Error).
payload.solution string
Suggested fix for the error.
payload.awsCode string
Raw AWS error code.

How to Use

  1. Select an AWS config node (or create one with your AWS credentials/region).
  2. Enter the Queue URL, or supply it at runtime via msg.payload.queueUrl.
  3. Single: wire this node after processing one message from SQS Receive and pass its ReceiptHandle as msg.payload.receiptHandle.
  4. Batch: pass the array of processed messages/handles as msg.payload.messages or msg.payload.receiptHandles (or as the whole msg.payload).
  5. Wire the output: Output 1 = success/partial success, Output 2 = AWS error or total batch failure.

ConnectHealth Example

Delete a single message after successfully processing an EHR sync event:

msg.payload = {
  queueUrl: "https://sqs.us-east-1.amazonaws.com/123456789012/fhir-sync",
  receiptHandle: "AQEB3s...=="
};

// Output 1 on success:
msg.payload = { success: true, deleted: 1 }

Delete a batch of messages received together from SQS Receive:

msg.payload = {
  messages: [
    { MessageId: "m1", ReceiptHandle: "AQEB1..." },
    { MessageId: "m2", ReceiptHandle: "AQEB2..." }
  ]
};

// Output 1 (all succeeded):
msg.payload = {
  success: true,
  deleted: 2,
  failed: 0,
  Successful: [ ... ],
  Failed: []
}

Best Practices

  • Only delete a message after it has been fully and durably processed — deletion is permanent and cannot be undone.
  • For batch input, a partial failure (some entries succeed, some fail) still routes to Output 1 — check payload.failed and payload.Failed and retry those handles if needed.
  • If every entry in a batch fails, the message routes to Output 2 instead.
  • Never log or persist receipt handles or message bodies outside of this flow — they are transient references, and message bodies/attributes may carry PHI.