Resources · Make integration

Amazon SQS (Simple Queue Service) Make integrationAutomate Amazon SQS (Simple Queue Service) with Make.

Need other tools to drop work into an SQS queue without writing a producer script? The Amazon SQS (Simple Queue Service) Make integration gives you 9 modules: 8 actions and 1 search. This guide is for ops and dev teams on AWS, and it walks you through the connection and a first working scenario.

Try the Amazon SQS (Simple Queue Service) integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Amazon SQS (Simple Queue Service) Make integration do?

The Amazon SQS (Simple Queue Service) Make integration lets a Make scenario act on your SQS queues with no code. A scenario is the automation you build in Make, a chain of bricks called modules. Here, those modules create and remove queues, push messages, read queue details and tidy up messages once they are handled.

Feed a queue from a business tool. Put another app's trigger first, for example a new row in a table, then add Send a message. Every new item becomes a message that your workers pick up on the AWS side, and nobody has to maintain a small script just for that.

Keep an eye on your queues. Chain Search queues with Get queue attributes to pull the settings of each queue into a sheet or a chat message. A search can return several queues, so Make treats each one as its own item.

Spin queues up and down with a project. Create queue and Delete queue let a scenario open a queue when a project starts and remove it when the project is closed.

What Make does not do here: the app has no trigger, so no module watches a queue for you. A scenario starts from another app or from its own schedule. For anything the 9 listed modules miss, Make an API call reaches the rest of the API. The same app often has an n8n node too, and our n8n vs Make page lays out how the two tools differ. For the bigger picture on the tool itself, read the Make review, or check Make pricing before you pick a plan.

Connect

How do you connect Amazon SQS to Make?

  1. 01

    Create an access key in AWS

    You need an active AWS account. In the AWS Management Console, open IAM, choose Users, click the user Make will act as, open the Security credentials tab and click Create access key. Copy both the Access key ID and the Secret access key.

  2. 02

    Add a module and open the connection

    In your scenario, add any Amazon SQS (Simple Queue Service) module and click Create a connection. A connection is your AWS account linked to Make once, then reused by every SQS module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the keys and save

    Paste the two values you copied from AWS into the connection window, or follow the on-screen instructions, and save. Make can now act on your queues, and the next SQS module you add will offer this connection in its list.

First scenario

Your first scenario with Amazon SQS

GoalWhen a new item lands in another app, Make sends it as a message to your Amazon SQS queue.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Since SQS has no trigger, pick the trigger of the app where your items appear first, such as a form or a table.

  2. 02

    Add Send a message

    Click the + on the right of that first module, search for Amazon SQS and pick Send a message. Choose your connection, or click Create a connection if this is your first SQS module.

  3. 03

    Map the data

    Fill in the module fields. Make lists what it can read once the connection exists, and you map values from the first module into the message, so each bundle (one item passed along) becomes one message.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Open the bubble above each module to read the bundles it received, then check on the AWS side that the message reached your queue.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule. A new scenario runs every 15 minutes by default. Then switch the scenario on, and it keeps sending messages without you.

Modules

What the Amazon SQS modules do

Amazon SQS (Simple Queue Service) gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Amazon SQS (Simple Queue Service)1

Create queue

ActionIn the docs only

Opens a new queue in your AWS account straight from a scenario, so a fresh workspace for messages exists the moment a process needs one.

When to use it
a new client, project or environment is created in another tool and should get its own queue without a trip to the AWS console.
Watch out
if the scenario runs again on the same item, it may try to open the same queue twice, so filter on items that are truly new.
Amazon SQS (Simple Queue Service)2

Delete a message

ActionIn the docs only

Removes one message from a queue, which is how you tell SQS that a piece of work is finished and should not come back.

When to use it
your scenario has just processed a message, for example stored it in a database, and the queue should now forget it.
Watch out
treat the deletion as final, so place this module after the step that really does the work, not before.
Amazon SQS (Simple Queue Service)3

Delete queue

ActionIn the docs only

Removes a whole queue, which keeps your AWS account free of queues nobody uses anymore.

When to use it
a project, a client or a test environment is closed in another app and its queue should go with it.
Watch out
treat the deletion as final. Test it with Run once on a throwaway queue before you point it at anything real.
Amazon SQS (Simple Queue Service)4

Get queue URL

ActionIn the docs only

Looks up the address of a queue from its name and hands it to the next modules, so you work with a readable name instead of a long address.

When to use it
the queue name comes from data, such as a team or region field, and a later step needs the matching queue.
Watch out
a typo in the name finds nothing, so map the name from a reliable field rather than typing it by hand.
Amazon SQS (Simple Queue Service)5

Get queue attributes

ActionIn the docs only

Reads the settings and details of one queue and returns them as data you can map into a report, a message or a condition.

When to use it
you want a view of a queue's state in a sheet or a chat channel, or you want a filter to decide what happens next based on it.
Watch out
it reads a single queue per run, so pair it with Search queues when you need the same details for many.
Amazon SQS (Simple Queue Service)6

Make an API call

ActionIn the docs only

Calls any endpoint of the Amazon SQS API with the connection you already set up, which covers what the other eight modules leave out.

When to use it
you need an SQS operation that has no dedicated module here and would rather not build a separate authenticated request.
Watch out
you write the request yourself, so keep the AWS documentation open next to the module to get the endpoint and its parameters right.
Amazon SQS (Simple Queue Service)7

Search queues

SearchIn the docs only

Returns the queues of your account that match what you ask for, each one as its own bundle, so later modules can handle them one by one.

When to use it
you want an inventory of your queues, or a step that runs on every queue of a family, like a check with Get queue attributes.
Watch out
a search can return zero, one or many queues, and every module placed after it runs once per result, which counts operations.
Amazon SQS (Simple Queue Service)8

Send a message

ActionIn the docs only

Pushes a message into a queue so the programs reading that queue pick up the work, which turns any Make trigger into a producer for your AWS system.

When to use it
an order, a signup or a ticket appears in a business app and your backend should process it on its side.
Watch out
each bundle reaching this module sends one message, so a search placed before it can send many at once.
Amazon SQS (Simple Queue Service)9

Update message visibility timeout

ActionIn the docs only

Changes how long a message you are handling stays hidden from other readers of the queue, which gives your scenario more room or hands the message back sooner.

When to use it
a step in your scenario takes longer than planned, or it fails and the message should become available to another worker again.
Watch out
this acts on one specific message, so it has to follow the step that gave you that message.
Need help

Need help automating Amazon SQS (Simple Queue Service) with Make?

A person reads every message.

FAQ

Amazon SQS and Make: common questions

01Is the Amazon SQS (Simple Queue Service) Make integration free?
Yes, on the Make side. Amazon SQS is a standard app, available from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, 5 minutes of run time and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run on one bundle. The cost of SQS itself is set by AWS, on its own pricing page.
02What do you need to connect Amazon SQS (Simple Queue Service) to Make?
You need an active AWS account and an access key for the IAM user Make will act as. In the AWS console, open IAM, then Users, pick the user, open the Security credentials tab and click Create access key. Keep the Access key ID and the Secret access key. In Make, add any SQS module, click Create a connection, give it a name if you like and paste both values. Every SQS module of your scenarios then reuses that connection.
03Does the Amazon SQS (Simple Queue Service) Make integration react in real time?
No, because the app has no trigger module in Make, so nothing watches a queue on your behalf. A scenario that uses SQS starts in one of two ways. Either another app's trigger fires first and SQS modules follow it, or the scenario runs on its own schedule, every 15 minutes by default and down to 1 minute on paid plans. How fast things happen then depends on the trigger you put first.
04What if an Amazon SQS module is missing in Make?
Use Make an API call. It reaches any endpoint of the SQS API with the same connection you created for the other modules, so an operation without a dedicated module is still within reach. The price is that you write the request yourself, so keep the AWS documentation open next to it. The integration currently lists 9 modules, 8 actions and 1 search. If you still get stuck, test the scenario with Run once and read the bundles each module returned.
05Should you use Make or n8n with Amazon SQS?
It depends on the tool your team already works in. Amazon SQS has an integration in Make, and the same app often has an n8n node as well, so both can send messages and manage queues. In Make you get 9 ready modules, a visual editor where you test with Run once, and a Free plan to try the connection. The practical path is to build the same small scenario in the tool you know and keep the one your team finds easier to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations