List Queues
sqs.list_queues
ActionAmazon Web Servicesconnection required
Calls the SQS ListQueues API with a SigV4-signed request.
List the SQS queues in the connection's region, optionally filtered by name prefix. Account-level, so it does not need a queue_url.
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
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 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 |
|---|---|---|---|---|---|
prefix Queue-name prefix filter. | string | No | — | — | — |
max_results Max queues (1-1000). | number | No | 100 | ≥ 1 | — |
next_token Continue from a previous run of this node by passing that run's next_token output; leave blank for the first page. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"max_results": 100
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
queue_urls | array | — |
count | number | — |
next_token Token for the next page; empty when there are no further pages. | string | — |
{
"count": 0,
"next_token": "",
"queue_urls": []
}Related Amazon SQS nodes
See List Queues 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.