Skip to main content

Send AWS SQS node

The Send AWS SQS node allows sending messages in an Amazon SQS queue. It is used to decouple systems, to create processing queues and to integrate workflows with AWS.

Parameters​

ParameterTypeRequiredDefaultDescription
AppApp❌—Application associated with the node. See Apps.
AWS RegionString✅—Target AWS region (e.g. eu-west-1, us-east-1).
API VersionString❌—SQS API version used by the node.
Access key IDString✅—AWS Access Key ID used to sign the request.
Secret access keyString✅—Associated AWS Secret Access Key.
Queue type (Standard or FIFO)Standard / FIFO✅—Type of queue to target.
Queue URLString✅—Full URL of the target SQS queue.
Message bodyJSON❌—Content of the message sent to SQS.
Message group IDString❌—Required on the AWS side only for a FIFO queue.
Message delivery delay (in seconds)Number (seconds)❌—Delay before the message is available, between 0 and 900.

AWS Region​

AWS region to use for the SQS call (e.g. eu-west-1, us-east-1).

API Version​

SQS API version used by the connector (optional depending on the configuration).

Access key ID​

AWS Access Key ID used to authenticate the call.

Secret access key​

Secret Access Key associated with the AWS access identifier.

See also: Use authentication methods in workflows.

Queue type (Standard or FIFO)​

Choose the target queue type:

  • Standard: high throughput, best-effort ordering
  • FIFO: strict ordering and deduplication

Queue URL​

Queue URL:

  • Format: https://sqs.{region}.amazonaws.com/{account-id}/{queue-name}
  • Supports Handlebars variables
  • A dictionary variable can provide the full URL: {{dictionaries.aws.ordersQueueUrl}} — in this case, the .fifo suffix is not imposed by the form
Variable and queue type

When the URL is a dynamic variable (dictionary or context), the queue type displayed by the form cannot be deduced from the URL: the .fifo suffix is then not forced. Make sure the variable value respects the format expected for the configured queue type (.fifo for a FIFO queue).

Message body​

Message body:

  • JSON format (recommended)
  • Supports Handlebars variables
  • Max size: 256 KB

Message group ID​

Message group identifier:

  • Recommended for FIFO queues (messageGroupId)
  • May be present depending on the configured queue type

Message delivery delay (in seconds)​

Delay before the message is available on the consumer side:

  • Value between 0 and 900 seconds
  • Allows delaying the consumption after publication

Input​

The node receives the workflow context data (trigger or previous nodes) and injects it into the message body and the queue URL via Handlebars variables. Example of message body:

{ "orderId": "{{context.order.id}}", "status": "pending" }

Output​

The Send AWS SQS node generates no context variable: it publishes the message in the queue then the workflow continues. The message is then consumed by the AWS SQS trigger or any other consumer of the queue.

Errors​

No specific failure condition is documented for this node. On execution failure, add an On Error node to the workflow to handle the error cleanly.

Limits​

  • Maximum message body size: 256 KB.
  • Message delivery delay between 0 and 900 seconds.
  • For a FIFO queue, the queue URL must respect the expected format (.fifo suffix).

Example​

Send an order in an SQS queue: fill in the node fields:

  • AWS Region: us-east-1
  • Queue type: Standard
  • Queue URL: https://sqs.us-east-1.amazonaws.com/123456789012/orders
  • Message body:
{ "orderId": "{{context.order.id}}", "status": "pending" }

The AWS access keys are selected via an authentication method or referenced by variables ({{dictionaries.aws.accessKeyId}}).

See also​