Resources · Make integration

Amazon DynamoDB Make integrationAutomate Amazon DynamoDB with Make.

Your DynamoDB tables can fill and update themselves while other apps do the talking. The Amazon DynamoDB Make integration gives you 15 modules: 14 actions and 1 search. This guide shows builders how to connect AWS, pick the right module and run a first test.

Try the Amazon DynamoDB integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Amazon DynamoDB Make integration do for you?

The Amazon DynamoDB Make integration lets a Make scenario read, write and manage your DynamoDB tables without code. A scenario is the automation you build in Make, a chain of modules; each module is one brick, here an action or a search on your AWS data. Data from other apps goes in, and stored items come back out for the next step.

Keep a table in sync with another tool. A lead lands in your CRM or a form gets submitted, and Create or replace an item stores it as a DynamoDB item. When only one value changes later, Update an item touches that item and leaves the rest alone.

Feed other apps from stored data. Get an item pulls one record for an email or a Slack message, while Create a query and Scan a table bring back larger slices when a report or a sync needs them.

Housekeeping at scale. Batch delete items clears a set of records in one pass, and Create a table, Update a table or Delete a table manage the structure itself, useful for teams that spin up a table per project.

One limit to plan around: the app has no trigger, so a change inside DynamoDB cannot start a scenario by itself. The first module comes from another app, or the scenario runs on a schedule. Before committing, the Make review covers how the platform behaves day to day, and if you also weigh n8n, which often has a node for the same app, the n8n vs Make comparison lays out the differences.

Connect

How do you connect Amazon DynamoDB to Make?

  1. 01

    Create an access key in AWS

    In your AWS account, click your user name in the navigation bar, then Security credentials. In Access keys, click Create access key, choose Other, then Next if AWS asks for a use case, and confirm.

  2. 02

    Open a connection from a module

    In your scenario, add any Amazon DynamoDB module and click Create a connection. A connection is your AWS account linked to Make once; every DynamoDB module reuses it. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the two values

    Copy both values shown on the Retrieve access keys page and paste them into the connection window, or follow the on-screen instructions. Save, and Make can now list what it is allowed to read in your account.

First scenario

Build your first scenario with Amazon DynamoDB

GoalWhen a new entry arrives in another app, Make stores it as an item in your Amazon DynamoDB table.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + on the empty canvas. This is where the chain of modules takes shape, one bubble per step.

  2. 02

    Start from another app

    DynamoDB has no trigger, so the first bubble belongs to the tool where entries appear, a form or a shop for instance. Search that app, pick its trigger and create its connection.

  3. 03

    Add Create or replace an item

    Click the + on the right of the first module, search Amazon DynamoDB and choose Create or replace an item. Once the connection exists, pick your table and map values from the first module.

  4. 04

    Test with Run once

    Click Run once, then create a test entry in the first app. Open each module to read the bundles it received; a bundle is one item passing from one module to the next.

  5. 05

    Schedule and switch on

    Open Scheduling on the first module. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Then switch the scenario on.

Modules

What each Amazon DynamoDB module does

Amazon DynamoDB gives you 15 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Amazon DynamoDB1

Batch create or replace items

ActionIn the docs only

Writes a whole set of items to a table from a single module, so a list coming from another app lands in DynamoDB without one write step per record.

When to use it
an export of orders or sign-ups hands you several rows at once and they belong in the same table.
Watch out
the name says replace, so an item that already exists is overwritten; switch to Update an item when only part of a record should change.
Amazon DynamoDB2

Batch delete items

ActionIn the docs only

Removes several items from a table in one pass, which keeps cleanup inside one module instead of a loop of single deletions.

When to use it
a batch of test records, cancelled bookings or expired entries needs to disappear together after a check in another tool.
Watch out
a delete cannot be undone from Make. Test on a copy first.
Amazon DynamoDB3

Batch get items

ActionIn the docs only

Fetches a group of known items from a single module, handy when the next module needs several records side by side rather than one at a time.

When to use it
a ticket or an invoice references a few customers or products and you want all their details before building the message.
Watch out
open the output after Run once to see how Make hands the results to the next module before you map anything.
Amazon DynamoDB4

Create a query

ActionIn the docs only

Asks a table for the items that match what you describe, so the scenario works on a targeted slice of data instead of everything.

When to use it
you need every order of one customer, or every record tied to one project, to feed a summary or a follow-up.
Watch out
each module run on each bundle counts as an operation on your plan, so a query that feeds many later steps weighs more than it looks.
Amazon DynamoDB5

Create a table

ActionIn the docs only

Sets up a brand new table from a scenario, which spares a trip to the AWS console each time a new container for data is needed.

When to use it
your team opens a new client project or a new event and each one gets its own table from the start.
Watch out
the connection needs the IAM permissions to manage tables, not only to read and write items; check them before the first run.
Amazon DynamoDB6

Create or replace an item

ActionIn the docs only

Saves one record in a table: it creates the item, or replaces it entirely if it already exists. It is the natural landing spot for data coming from another app.

When to use it
a form submission, a new lead or a paid order should become one stored item.
Watch out
replace means the previous version goes away; to change a single value on an existing record, Update an item is the safer pick.
Amazon DynamoDB7

Delete a table

ActionIn the docs only

Removes an entire table, structure and contents, straight from a scenario. It closes the loop for teams that create tables on the fly.

When to use it
a project is archived in your project tool and its dedicated table no longer serves any purpose.
Watch out
nothing in Make brings a deleted table back, so add a filter or a manual check before this module and never test it on production data.
Amazon DynamoDB8

Delete an item

ActionIn the docs only

Erases a single item, the precise tool when one record has to go and the rest of the table stays untouched.

When to use it
a contact unsubscribes or asks for removal in another app, and the matching record in DynamoDB should follow.
Watch out
the deletion is final, so make sure the value you map points to the right item; a quick Run once on a test entry avoids bad surprises.
Amazon DynamoDB9

Get a table

ActionIn the docs only

Returns information about one table, so a scenario can look at a table before acting on it rather than working blind.

When to use it
right after Create a table or Update a table, to confirm the result, or before a batch write to make sure the target is the one you expect.
Watch out
it describes the table, not its items; to read records, use Get an item, Create a query or Scan a table.
Amazon DynamoDB10

Get an item

ActionIn the docs only

Reads one specific item and passes its values to the next module, the quickest route when you already know which record you need.

When to use it
an incoming support ticket carries a customer reference and you want that customer's stored details in the reply.
Watch out
if the item is missing, the following modules have nothing to map; test with Run once on both a known and an unknown reference.
Amazon DynamoDB11

List tables

SearchIn the docs only

Brings back the tables your connection can see, one bundle per table, which gives the scenario an inventory to work from.

When to use it
you want a recap of existing tables sent to a sheet or a channel, or you need to loop over every table in a later step.
Watch out
as a search, it can return zero, one or many bundles, and every module placed after it runs once per bundle.
Amazon DynamoDB12

Make an API call

ActionIn the docs only

Opens the whole DynamoDB API from your scenario, with the same connection, for anything the other 14 modules do not cover.

When to use it
a request you need has no dedicated module and you are comfortable reading the AWS API documentation to build it.
Watch out
you write the request yourself, so check the response with Run once before mapping it into the next module.
Amazon DynamoDB13

Scan a table

ActionIn the docs only

Goes through a table and returns what it holds, the broad view when you do not have a precise target in mind.

When to use it
you want to copy the contents of a small table into a spreadsheet for a review, or check every record against another system.
Watch out
when you can describe exactly which items you need, Create a query keeps the scenario lighter and the output easier to read.
Amazon DynamoDB14

Update a table

ActionIn the docs only

Changes the settings of an existing table from a scenario, so structural adjustments follow the same flow as the rest of your automation.

When to use it
a project moves to a new stage in your management tool and its table needs different settings to match.
Watch out
this module acts on the table, not on the items inside; to change a record, reach for Update an item instead.
Amazon DynamoDB15

Update an item

ActionIn the docs only

Edits values on an item that already exists and keeps everything else in place, the careful counterpart to a full replace.

When to use it
a deal changes stage in your CRM or a payment is confirmed, and only the status of the stored record should move.
Watch out
the item has to exist first; pair it with Get an item when you are not sure, or use Create or replace an item for new records.
Need help

Need help automating Amazon DynamoDB with Make?

A person reads every message.

FAQ

Questions about Amazon DynamoDB and Make

01Is the Amazon DynamoDB Make integration free?
Yes. Amazon DynamoDB is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Make counts usage in operations, one module run on one bundle. Your AWS usage is billed separately by Amazon, and the doc points to the Amazon DynamoDB pricing page for that part.
02What does it take to connect Amazon DynamoDB to Make?
An active AWS account with appropriate IAM permissions, then an access key. In AWS, open Security credentials from your user name, click Create access key in the Access keys section, pick Other if asked for a use case, and create the key. Copy the two values shown on the Retrieve access keys page. In Make, add any Amazon DynamoDB module, click Create a connection, optionally name it, and paste those values. The connection is then reused by every DynamoDB module in your scenarios.
03Can Amazon DynamoDB start a Make scenario on its own?
No. The app has no trigger module in Make, so a change inside a table cannot launch a scenario directly. There are two ways around it. Start the scenario with a trigger from another app, such as a form, a CRM or a shop, and let the DynamoDB modules follow. Or run the scenario on a schedule set on the first module: every 15 minutes by default, 15 minutes at least on the Free plan and down to 1 minute on paid plans.
04What if a DynamoDB action is missing in the Make integration?
Use the Make an API call module. It reaches any endpoint of the DynamoDB API from your scenario with the connection you already set up, which covers requests the 14 other modules do not offer. You build the request yourself from the AWS API documentation, so test it with Run once and read the returned bundle before mapping it further. The doc lists no specific limit for this app, and its content is marked as AI-generated, so verify important details with Amazon directly.
05Make or n8n for Amazon DynamoDB: which one fits?
It depends on the modules you need. In Make, Amazon DynamoDB comes with 15 modules, including Make an API call, and it is available from the Free plan with 2 active scenarios. n8n often has a node for the same app, so list the operations your workflow requires and check that each tool covers them. Neither is ranked here: the right pick is the one whose building blocks match your use case and the platform your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations