STEP 1
Select AWS SQS in workflow
Pick AWS SQS app in the workflow builder [4] - just one click to select the app.
AWS SQS Integration
Send, receive, and manage messages on Amazon SQS queues. Connect AWS SQS conversations to the systems your team already uses every day. When Watch Queue Messages lands, react with Get Queue Attributes or Get Queue Url.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for AWS SQS integration
Triggers can detect changes in AWS SQS and run actions that can create, search or modify data inside AWS SQS automatically [3] — exactly how you set them.
- Watch Queue MessagesTriggers when new messages arrive in an SQS queue. Messages become invisible for the visibility timeout; chain Delete Message to acknowledge.
- Get Queue AttributesReturns attributes of an SQS queue.
- Get Queue UrlReturns the URL of an existing SQS queue by name.
- List Dead Letter Source QueuesLists source queues that have a dead-letter queue configured.
- List Message Move TasksLists active and completed message move tasks for a source queue.
- List Queue TagsReturns the tags assigned to an SQS queue.
- List QueuesLists SQS queues in the region, optionally filtered by name prefix.
- Receive MessageRetrieves up to 10 messages from a queue. Messages become invisible for the visibility timeout; delete them to acknowledge processing.
- Add PermissionAdds a permission to a queue for a specific principal.
- Cancel Message Move TaskCancels a running message move task.
- Change Message VisibilityChanges the visibility timeout of a received message.
- Change Message Visibility BatchChanges the visibility timeout of multiple received messages in one request.
- Create QueueCreates a new SQS queue. FIFO queues must have a name ending in .fifo and set the FifoQueue attribute.
- Delete MessageDeletes a received message from a queue, acknowledging successful processing.
- Delete Message BatchDeletes up to 10 messages from a queue in a single request.
- Delete QueueDeletes an SQS queue and all its messages. This action is irreversible.
- Make an API CallPerforms an arbitrary authorized API call to the Amazon SQS endpoint.
- Purge QueueDeletes all messages from a queue without deleting the queue itself. This action is irreversible.
- Remove PermissionRemoves a permission from an SQS queue.
- Send MessageSends a message to an SQS queue.
How to integrate AWS SQS in automation workflow?
3 simple steps to make your AWS SQS connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
STEP 2
Connect AWS SQS
When prompted, authorize access to AWS SQS in WEXTL once. AWS SQS credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your AWS SQS account. Approve?
STEP 3
Build a workflow
Build your workflow with AWS SQS yourself or with WEXTL® AI Builder. Connect AWS SQS to any available integrations [5], or use HTTP node to go beyond them.
AWS SQS
How AWS SQS connects and integrates with WEXTL
Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever AWS SQS app is called in workflows. That allows your communication automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that AWS SQS supports.
The following table illustrates what fields AWS SQS integration require during authorization flow inside our workflow builder [4].
Connect AWS SQS
Access Key ID*Text
••••••••
Secret Access Key*Text
••••••••
Demonstration of AWS SQS connection step inside WEXTL Workflow Builder [4].
| Field | Type | Help |
|---|---|---|
Access Key IDRequired | text | IAM access key. |
Secret Access KeyRequired | password | Stored encrypted. Marker for SigV4 signing. |
RegionRequired | text | e.g. us-east-1. Drives host. |
ServiceRequired | select | Amazon SQS signing name. Leave as sqs. |
| Session Token | password | Temporary STS credentials. |
Connect AWS SQS to popular apps on WEXTL
Enter a name of the other app you want to sync with AWS SQS below. Click on selected app to explore integration options with AWS SQS. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.
Example automation with AWS SQS integration
Select Watch Queue Messages trigger from AWS SQS - this will be a starting point in your automation. Whenever event happens in AWS SQS, workflow will start [7] from Watch Queue Messages node.
Search for Create Queue, connect it as the next step of integration sequence. You can use filters between Watch Queue Messages and Create Queue, so only important data pass from Watch Queue Messages to the next step. WEXTL gives you full control over the process of AWS SQS automation. All parts of workflow are visible on the canvas [4].
AWS SQS on WEXTL has 25 modules for combining communication automations. Explore AWS SQS documentation for more.
AWS SQS
Watch Queue Messages
AWS SES
Performs action
OR
AWS SES
Triggers
AWS SQS
Create Queue
Demonstration of how visual AWS SQS automation [6] looks in WEXTL.
Frequently asked questions
Common questions about automating AWS SQS in your workflows.
AWS SQS has 1 trigger, including "Watch Queue Messages". Triggers are start points of the workflow, and automations may start from them.
Integration has 24 actions, including "Get Queue Attributes", "Get Queue Url", and "List Dead Letter Source Queues", and more. Refer to our AWS SQS Documentation for detailed inputs and outputs.
No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases [4].
Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.
The AWS SQS integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by AWS SQS official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.
Absolutely. Where AWS SQS provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever AWS SQS or any other service sends event to webhook URL.
WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for AWS SQS inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with AWS SQS modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.
References
List of sources used to gather information about the AWS SQS integration.
- AWS SQS integration source code, module specs and credentials implementation.
- Internal AWS SQS integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official AWS SQS vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® AWS SQS App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation