Receive Messages
sqs.receive_messages
ActionAmazon Web Servicesconnection required
Calls the SQS ReceiveMessage action (SigV4).
Receive messages from an AWS SQS queue.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Amazon SQS
- Secret shape
- {"access_key_id", "secret_access_key"}
- Config it needs
- region, queue_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
region AWS region (overrides connection). | string | No | — | — | — |
queue_url Queue URL (overrides connection). | string | No | — | — | — |
max_messages Max messages (1-10). | number | No | 1 | ≥ 1 | — |
wait_seconds Long-poll wait seconds (0-20). | number | No | 0 | 0–20 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"max_messages": 1,
"wait_seconds": 0
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
messages | array | — |
count | number | — |
{
"count": 0,
"messages": []
}Related Amazon SQS nodes
See Receive Messages run in a workflow.
In a technical demo we add the Amazon SQS connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.