Integration · Cloud and hosting
AI agents for Amazon SQS
Send messages to Amazon SQS queues, receive and delete them to work through a queue, and list queues and their message counts, signed with an AWS access key.
- Actions
- 7
- Read
- 3
- Write
- 4
Actions
What your agents can do in Amazon SQS
Send messages to Amazon SQS queues, receive and delete them to work through a queue, and list queues and their message counts, signed with an AWS access key. Uses SQS's query API, whose XML answers this tool returns as text.
Read 3
Look things up. Nothing changes.
List queues
Lists the account's queue URLs in the connection's Region, optionally only those whose name starts with a prefix, up to 1,000 a page.
Get a queue's URL
Finds a queue's URL from its name (and the owning account, for a queue another account shared).
Get a queue's counts and settings
Gets a queue's attributes: ApproximateNumberOfMessages (waiting), ApproximateNumberOfMessagesNotVisible.
Write 4
Create, change or send.
Send a message
Sends one message to a queue.
Receive messages
Takes up to 10 waiting messages from a queue, waiting up to 20 seconds for one to arrive.
Delete a messageDeletes data
Deletes a received message from a queue by its ReceiptHandle, once it has been handled.
Hide a message for longer
Changes how long a received message stays hidden, to take more time over it, or 0 to put it back on the queue at once.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the sign-in details Amazon SQS gives you for its API.
What you enter
- Access key ID
- Secret access key
Settings
- Region
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Amazon SQS data
Ask a question in plain words. The agent can list queues, get a queue's URL or get a queue's counts and settings in Amazon SQS, then answers with what it found.
- 02
Let an agent update Amazon SQS
Have the agent send a message or delete a message in Amazon SQS as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Amazon SQS and Slack: it can list queues in Amazon SQS and post a summary to a Slack channel in the same run.
FAQ
Amazon SQS and MyDeepAgents
Can MyDeepAgents connect to Amazon SQS?
Yes. The Amazon SQS connector has 7 actions: 3 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Amazon SQS?
Enter the sign-in details Amazon SQS gives you for its API. You'll need: Access key ID and Secret access key. The connection also asks for: Region. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Amazon SQS without asking?
Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Amazon SQS in workflows as well as agents?
Yes. Every Amazon SQS action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Amazon SQS to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.