Resources · Make integration

Amazon Bedrock Make integrationAutomate Amazon Bedrock with Make.

Can a Bedrock model work on your data without a line of code? The Amazon Bedrock Make integration gives you 4 action modules: a conversation, a prompt, an image and a raw API call. This guide links your AWS account and walks you through a first working scenario.

Try the Amazon Bedrock integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Amazon Bedrock Make integration let you do?

It lets a Make scenario (the automation you build in Make, a chain of bricks called modules) send text to a model hosted on Amazon Bedrock and pass the answer on. You get the model's output inside your workflow, next to your other apps, without writing code or calling AWS by hand.

Replies drafted for you. Text lands in a form, a CRM or a sheet; Create a conversation sends it to the model and the answer flows to the next module, ready to be saved or sent. A sales team can get a first reply to every inbound lead this way.

A prompt, ready for the model. Create a prompt prepares a prompt for the model you pick. Make describes it in one line, so run it once and read what it returns before you build on it.

Visuals on demand. Generate an image produces a picture a later module can store or attach. And when the model offers something the three modules do not cover, Make an API call reaches the rest of the API with the same connection.

What Make does not give you here: no trigger. Bedrock never starts a scenario on its own, so the flow opens on another app or on a schedule. If you are weighing tools, the n8n vs Make comparison sets both side by side, and the Make review covers the editor in depth. Stuck on an error later? See Make troubleshooting.

Connect

How do you connect Amazon Bedrock to Make?

  1. 01

    Generate your API key in AWS

    You need an active AWS account with the right permissions and access to Amazon Bedrock. In the Bedrock console, open API Keys in the left pane, click Generate API Key, name it if asked, then Create. Copy the key and the secret.

  2. 02

    Open the connection window in Make

    Add any Amazon Bedrock module to your scenario and click Create a connection. A connection is your Bedrock account linked to Make once, then reused by every Bedrock module. The Connection name field is optional.

  3. 03

    Paste the credentials and save

    Enter the API key and the secret you copied from the AWS console, or follow the on-screen instructions. The connection then serves every Bedrock module.

First scenario

Your first scenario with Amazon Bedrock

GoalWhen new text arrives in another app, Make sends it to Amazon Bedrock and hands the model's reply to the next step.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app that holds your text first (a form, a sheet, a CRM): Bedrock has no trigger, so the flow starts elsewhere.

  2. 02

    Add Create a conversation

    Click the + on the right of that first module, search Amazon Bedrock and pick Create a conversation. Link your account with Create a connection if it is not done yet.

  3. 03

    Map the incoming text

    Fill the module fields and drop the text from the first module into the message. Each item that flows between modules is a bundle: one form entry, one row, one contact.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, so you can read the model's answer before anything goes live.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and turn the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What the Amazon Bedrock modules do

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

Amazon Bedrock1

Create a conversation

Action

In Make“Sends messages to the specified Amazon Bedrock model.”

You get a reply from the Bedrock model you choose to the messages you send, delivered as data the next module can use. It is the one to reach for when the answer should read like a response to someone.

When to use it
a support ticket or lead message comes in and you want a drafted answer waiting in your helpdesk.
Watch out
every bundle that reaches this module is one operation, so filter out empty messages before it.
Amazon Bedrock2

Create a prompt

Action

In Make“Creates a prompt for the specified Amazon Bedrock model.”

It prepares a prompt for the Bedrock model you specify. Make only describes it in one line, so a Run once shows you what it actually returns before you map anything.

When to use it
you want the same instruction ready for a model before a later step uses it.
Watch out
keep the instruction in the module and map only the variable part, or each run starts from a different wording.
Amazon Bedrock3

Generate an image

Action

In Make“Generates an image.”

You get an image built from your description, which a later module can store, attach or publish. This is the only listed Bedrock module that returns a picture rather than text.

When to use it
a new blog post is ready in your content tool and it still needs a cover visual.
Watch out
on the Free plan, Make handles files up to 5 MB, so check the output size before sending it on.
Amazon Bedrock4

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

You reach any endpoint of the Bedrock API with the connection you already set up, for everything the three other modules leave out. You write the request yourself, which asks for a look at the AWS documentation.

When to use it
the model feature you need has no dedicated module in Make.
Watch out
the Make doc for this app is AI-generated and may contain mistakes, so verify key details with Amazon Bedrock directly.
Need help

Need help automating Amazon Bedrock with Make?

A person reads every message.

FAQ

Questions about Amazon Bedrock and Make

01Is the Amazon Bedrock Make integration free?
Yes, on the Make side. Amazon Bedrock is a standard app, available from the Free plan like the 3,000+ other standard apps. That plan allows 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. For Bedrock itself, check the Amazon Bedrock pricing page for your subscription.
02What do you need to connect Amazon Bedrock to Make?
An active AWS account with the right permissions and access to Amazon Bedrock. In the Bedrock console, you generate an API key from the API Keys pane, then copy the key and the secret shown to you and note the Region selected in the console. In Make, you add a Bedrock module, click Create a connection, and paste those credentials. The connection name is optional, and the same connection then serves all four modules.
03Can Amazon Bedrock start a Make scenario in real time?
No. Amazon Bedrock has no trigger module in Make, so it never starts a scenario by itself. You open the flow with another app instead: an instant trigger from a tool that calls Make through a webhook as soon as something happens, or a scheduled trigger that Make checks on the scenario's schedule. You can also run the scenario on a plain schedule, every 15 minutes by default, and place the Bedrock module after it.
04What if the Bedrock module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the Amazon Bedrock API with the connection you already have, so a feature without a dedicated module is still within reach. You write the request yourself, so keep the AWS documentation open. One more caution: the Make doc for this app is flagged as AI-generated and may contain mistakes, so confirm important details with Amazon Bedrock before you build on them.
05Should you use Make or n8n for Amazon Bedrock?
It depends on where the rest of your workflows live. On Make, Amazon Bedrock is a standard app with 4 modules, including Make an API call, and it works from the Free plan. The same app often has an n8n node too, so the deciding factors are the tool your team already runs, which apps sit around Bedrock in the flow, and who will maintain the scenarios once they run.
Same platform

Other docs you might need on this stack.

Browse all integrations