Resources · Make integration

Cerebras AI Make integrationAutomate Cerebras AI with Make.

What if every new form answer or support message got a written reply before anyone opened it? The Cerebras AI Make integration gives you 3 modules to send text to a Cerebras model from a scenario. This page connects your account and walks you through a first working scenario.

Try the Cerebras AI integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cerebras AI Make integration do for you?

The Cerebras AI Make integration links your Cerebras AI account to Make, so a scenario (the automation you build in Make, a chain of bricks called modules) can hand text to a Cerebras model and pass the answer on to your other apps. There is no trigger in this app: something else starts the scenario, and Cerebras AI does the writing in the middle.

Replies drafted as requests come in. A form tool starts the scenario, Create a Chat Completion turns the request into a draft answer, and the next module stores it where your team reviews it. The 123FormBuilder Make integration is one way to feed that first step.

A picture of what your account offers. List Models returns the models your key can use, one bundle (one item passed to the next module) per model, so you can check what is available before you build anything bigger.

Anything the menu leaves out. Make an API Call reaches any endpoint of the Cerebras AI API with the same connection, for the cases the two other modules do not cover.

Keep in mind that Make lists no trigger for Cerebras AI, and the official Make page for this app warns that it was written with AI help and may contain mistakes, so check important details with Cerebras AI. The same app often exists as an n8n node too; n8n vs Make lays out how the two tools differ. For a guided start, see our Make training.

Connect

How do you connect Cerebras AI to Make?

  1. 01

    Generate an API key in Cerebras AI

    Log in to Cerebras AI and open the Inference Cloud Console. Go to the section for API keys or credentials, click the button that generates a new key, then copy the key shown on screen. You need an active Cerebras AI account for this.

  2. 02

    Add a Cerebras AI module in Make

    In your Make account, add any Cerebras AI module to a scenario and click Create a connection. The Connection name field is optional; a clear name helps when you later run several accounts side by side.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, and save. From then on, every Cerebras AI module in your scenarios reuses this connection (your account linked to Make once).

First scenario

Your first scenario with Cerebras AI

GoalWhen a new request lands in another app, Make sends its text to Cerebras AI and gets a drafted reply back.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since Cerebras AI has no trigger, pick the app where your requests arrive, such as a form tool.

  2. 02

    Set up the first module

    Connect that app and fill its fields. Make lists what it can read once the connection exists, so there is no need to know the exact names by heart.

  3. 03

    Add Create a Chat Completion

    Click the + on the right of the first module, search for Cerebras AI and choose Create a Chat Completion. Pick your connection, then map the request text coming from the previous module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can read the reply Cerebras AI wrote before anything goes live.

  5. 05

    Schedule and switch it on

    If your first module is a scheduled trigger, set its schedule (every 15 minutes by default); then switch the scenario on. Each module run on one bundle counts as one operation, the unit Make tracks on your plan.

Modules

What the Cerebras AI modules do

Cerebras AI gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Cerebras AI1

Create a Chat Completion

Action

In Make“Creates a new chat completion.”

This is the module that makes Cerebras AI write: you send it text from earlier in the scenario and it returns a generated answer that the next module can store or send.

When to use it
a customer question arrives through a form and you want a draft reply waiting in your help desk.
Watch out
the answer is machine written, so route it to a person for review before it reaches a client.
Cerebras AI2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Your way into the parts of Cerebras AI that the two other modules do not reach: it calls any endpoint of the Cerebras AI API while reusing the connection you already created, so no second key to manage.

When to use it
the Cerebras AI documentation describes a request that neither Create a Chat Completion nor List Models handles.
Watch out
you write the request yourself, so keep the vendor documentation open while you set it up.
Cerebras AI3

List Models

Search

In Make“Returns a list of models.”

Handy for knowing what your key gives access to, List Models returns the models available on your Cerebras AI account, each one as a separate bundle.

When to use it
before you settle on a model in Create a Chat Completion, or when you want to log what the account currently offers.
Watch out
it is a search, so it can return several bundles, and every module placed after it runs once per model.
Need help

Need help automating Cerebras AI with Make?

A person reads every message.

FAQ

Cerebras AI and Make: frequent questions

01Is the Cerebras AI Make integration free?
Yes, on the Make side. Cerebras AI is a standard app, so it is available from the Free plan onward. The Free plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans bring the minimum interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution, with usage counted in credits each month. Your Cerebras AI subscription is separate: check the Cerebras AI pricing page for that part.
02What do you need to connect Cerebras AI to Make?
An active Cerebras AI account and an API key. You generate the key in the Inference Cloud Console, under the section for API keys or credentials, then copy it. In Make, add a Cerebras AI module, click Create a connection, optionally give the connection a name, and paste the key. That single connection is then reused by all three Cerebras AI modules, so you only go through these steps once per account.
03Can a Cerebras AI scenario in Make run in real time?
It depends on what starts it, because Cerebras AI has no trigger in Make. The scenario opens on another app's module or on a schedule. With a scheduled first module, Make checks at the interval you set, every 15 minutes by default and never less than 15 minutes on the Free plan. If the first module is an instant trigger from another app, that app calls Make through a webhook as soon as something happens, and Cerebras AI answers within that same run.
04What if a Cerebras AI module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Cerebras AI API with the connection you already set up, which covers what Create a Chat Completion and List Models do not. Keep the Cerebras AI documentation open while you configure it. Also note that the Make documentation for this app says it was produced with AI help and may contain mistakes, so confirm key details with Cerebras AI directly when something behaves differently than expected.
05Should you use Make or n8n for Cerebras AI?
It depends on the tool your team already works in. On Make, Cerebras AI comes with 3 modules, one connection built from an API key, and Make an API Call for anything else. The same app often exists as an n8n node too, so check whether it is available there before choosing. The comparison page linked higher up sets out the differences between the two tools without picking a winner for you.
Same platform

Other docs you might need on this stack.

Browse all integrations