Appearance
AWS SQS
Manage message queues with Amazon Simple Queue Service.
| Detail | Value |
|---|---|
| Category | Cloud & Infra |
| Base URL | https://sqs.us-east-1.amazonaws.com |
| Authentication | API Key |
| Endpoints | 8 |
| Connector key | aws-sqs |
Using AWS SQS in a workflow
- Go to Connections and click New Connection.
- Pick AWS SQS from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET / | List SQS queues |
POST /#CreateQueue | Create a queue |
POST /#SendMessage | Send a message |
POST /#ReceiveMessage | Receive messages |
POST /#DeleteMessage | Delete a message |
POST /#GetQueueAttributes | Get queue attributes |
POST /#PurgeQueue | Purge a queue |
POST /#SendMessageBatch | Send messages in batch |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /
List SQS queues
| Detail | Value |
|---|---|
| Operation ID | cloud.listQueues |
| Method | GET |
| Path | / |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SQS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listQueues. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS SQS API reference.
POST /#CreateQueue
Create a queue
| Detail | Value |
|---|---|
| Operation ID | cloud.createQueue |
| Method | POST |
| Path | /#CreateQueue |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SQS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.createQueue. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS SQS API reference.
POST /#SendMessage
Send a message
| Detail | Value |
|---|---|
| Operation ID | cloud.sendMessage |
| Method | POST |
| Path | /#SendMessage |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SQS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.sendMessage. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS SQS API reference.
POST /#ReceiveMessage
Receive messages
| Detail | Value |
|---|---|
| Operation ID | cloud.receiveMessage |
| Method | POST |
| Path | /#ReceiveMessage |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SQS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.receiveMessage. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS SQS API reference.
POST /#DeleteMessage
Delete a message
| Detail | Value |
|---|---|
| Operation ID | cloud.deleteMessage |
| Method | POST |
| Path | /#DeleteMessage |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SQS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.deleteMessage. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS SQS API reference.
POST /#GetQueueAttributes
Get queue attributes
| Detail | Value |
|---|---|
| Operation ID | cloud.getQueueAttributes |
| Method | POST |
| Path | /#GetQueueAttributes |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SQS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.getQueueAttributes. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS SQS API reference.
POST /#PurgeQueue
Purge a queue
| Detail | Value |
|---|---|
| Operation ID | cloud.purgeQueue |
| Method | POST |
| Path | /#PurgeQueue |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SQS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.purgeQueue. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS SQS API reference.
POST /#SendMessageBatch
Send messages in batch
| Detail | Value |
|---|---|
| Operation ID | cloud.sendMessageBatch |
| Method | POST |
| Path | /#SendMessageBatch |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SQS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.sendMessageBatch. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS SQS API reference.