Resources · Make integration

DataRobot Make integrationAutomate DataRobot with Make.

Can Make drive your DataRobot generative AI workspace for you? The DataRobot Make integration gives you 10 modules: 6 actions and 4 searches around chats, playgrounds and LLM blueprints. This page shows how to link your account and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the DataRobot Make integration do?

The DataRobot Make integration lets a Make scenario (the automation you build, a chain of steps) create, read and tidy the pieces of your DataRobot generative AI work: playgrounds, LLM blueprints, chats and use cases. You link your DataRobot account once with an API key, then each module (one brick of the scenario) does one job.

Spin up a workspace from a request. When a project request lands in another app, Create a Playground opens a fresh playground and Create a LLM Blueprint adds a blueprint to it, so the data team starts from a ready space instead of a blank screen.

Keep an inventory in a spreadsheet. List Use Cases and List Playgrounds return what exists in your account, one bundle (one item passed to the next module) per result, which you can push to a sheet or a report that everyone reads.

Tidy old conversations. List Chats finds chats, Update a Chat renames them to match your naming rules, and Delete a Chat removes the ones nobody needs.

DataRobot has no trigger in Make: nothing starts on its own from DataRobot, so a scenario begins with another app or with a schedule. When a listed module does not cover your case, Make an API Call reaches the rest of the API. The same app often exists in n8n too; the n8n vs Make comparison lays out the differences between the two tools, and the Make review helps if you are still choosing a platform.

Connect

How do you connect DataRobot to Make?

  1. 01

    Copy your API key in DataRobot

    In DataRobot, click your user icon at the top right, open API keys and tools, then the Personal API keys tab. Copy the key shown in the Value column, or create a new key first if the list is empty.

  2. 02

    Add a DataRobot module in Make

    In your Make scenario, add any DataRobot module and click Create a connection. A connection is your DataRobot account linked to Make once, then reused by every DataRobot module you add later.

  3. 03

    Name and save the connection

    Give it a label in Connection name if you want (this field is optional), paste the credentials copied from DataRobot, or follow the instructions on screen, and save. The module can now read your account.

First scenario

Your first DataRobot scenario in Make

GoalWhen a new project request arrives in another app, Make creates a DataRobot playground and adds an LLM blueprint to it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where project requests arrive, such as a form tool, and its module that starts the flow.

  2. 02

    Add Create a Playground

    Click the + to the right of that first module, search DataRobot and choose Create a Playground. Pick your connection, then map the request details from the previous module into the fields Make shows.

  3. 03

    Chain Create a LLM Blueprint

    Add one more module: Create a LLM Blueprint. Map the playground returned by the step before, so the blueprint lands in the space the scenario just built.

  4. 04

    Test with Run once

    Click Run once and send a test request. Open the bubble above each module to read the bundles it received and check that the playground and blueprint appear in DataRobot.

  5. 05

    Schedule and switch it on

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

Modules

What the DataRobot modules do

DataRobot gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

DataRobot1

Create a Chat

Action

In Make“Creates a chat.”

Opens a new chat in DataRobot from your scenario, so a conversation exists before anyone types a word. That saves your team the manual setup each time a new topic comes in.

When to use it
a support ticket or a client question arrives in another app and you want a dedicated DataRobot chat ready for it.
Watch out
run it once per item, or duplicates pile up quickly.
DataRobot2

Create a LLM Blueprint

Action

In Make“Creates LLM Blueprint.”

Gives you a new LLM blueprint in DataRobot without clicking through the interface, straight from the data your scenario already carries. Useful when several teams need the same starting setup.

When to use it
right after Create a Playground, to fill the new space with a blueprint mapped from the playground bundle.
Watch out
test it with Run once first, because a scenario that fires twice creates two blueprints.
DataRobot3

Create a Playground

Action

In Make“Creates a playground.”

Hands you a fresh DataRobot playground the moment a request calls for one, so a new project never starts on an empty screen. It is the natural first DataRobot step of a setup scenario.

When to use it
a new project, client or experiment is approved in another app and needs its own space.
Watch out
search with List Playgrounds before creating if the same request can come back twice.
DataRobot4

Delete a Chat

Action

In Make“Deletes a chat.”

Removes a chat from DataRobot for you, which keeps the list of conversations short and readable once a topic is closed. Pair it with a search so the scenario knows which chat to target.

When to use it
after List Chats, on the chats you have marked as finished.
Watch out
check which chat the search returned, then try it on one test chat with Run once before switching the scenario on.
DataRobot5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you reach any endpoint of the DataRobot API from the scenario, reusing the same connection, so you are not stuck when the ready-made modules stop short. It is the escape hatch of this app.

When to use it
you need a DataRobot operation that none of the other nine modules offers.
Watch out
you write the request yourself, so keep the DataRobot API documentation open next to Make.
DataRobot6

Update a Chat

Action

In Make“Updates a chat.”

Changes an existing DataRobot chat, which is handy for renaming it so your team finds it later by client or project name. Your team then finds it by name instead of scrolling.

When to use it
a deal changes name in your CRM and the matching chat should follow.
Watch out
you need the chat to target, so place List Chats or Create a Chat earlier in the flow.
DataRobot7

List Chats

Search

In Make“List Chats.”

Returns the chats in your DataRobot account, one bundle per chat, so the next modules can act on each of them. Think of it as the starting point of any cleanup or audit.

When to use it
before Update a Chat or Delete a Chat, to know which chats exist.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle, which adds operations.
DataRobot8

List LLM Blueprints

Search

In Make“List LLM Blueprints.”

Gives you the LLM blueprints already present in DataRobot, each as a separate bundle you can send to a sheet, a message or a filter. It answers the question of what has been built so far.

When to use it
a manager wants a shared table of every blueprint without logging into DataRobot.
Watch out
add a filter after it if only part of the list matters, to save operations downstream.
DataRobot9

List Playgrounds

Search

In Make“List Playgrounds.”

Brings back your DataRobot playgrounds as bundles, which lets a scenario check what exists before it creates anything new. That single check prevents most duplicates.

When to use it
ahead of Create a Playground, or to feed an inventory sheet shared with the data team.
Watch out
an empty result still lets the scenario continue, so decide with a filter what happens when nothing is found.
DataRobot10

List Use Cases

Search

In Make“List Usecases.”

Lists the use cases stored in DataRobot so you can see, outside the tool, which business problems are already being worked on. Each use case arrives as its own bundle.

When to use it
building a project board in another app that mirrors the use cases your team tracks in DataRobot.
Watch out
the result can be long; map only the details you need into the next module.
Need help

Need help automating DataRobot with Make?

A person reads every message.

FAQ

DataRobot and Make: common questions

01Is the DataRobot Make integration free?
Yes, on the Make side. DataRobot is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 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 lower the interval to 1 minute and remove the cap on active scenarios. Your DataRobot subscription is a separate matter, handled with DataRobot.
02What do you need to connect DataRobot to Make?
A registered DataRobot account and an API key. In DataRobot, open your user icon, go to API keys and tools, then the Personal API keys tab, and copy the value of an existing key or of a new one. In Make, add a DataRobot module, click Create a connection, optionally name it, paste the key and save. Once saved, it appears in the connection list of every new DataRobot module, so you never paste the key twice.
03Does the DataRobot integration react in real time?
No, because DataRobot has no trigger in Make. A scenario cannot start from an event inside DataRobot. It starts either from another app, such as a form or a CRM whose module watches for new items, or from the schedule on the first module, which runs every 15 minutes by default on a new scenario. From there, the DataRobot actions and searches run in sequence. If you need speed, a paid plan lets the schedule go down to 1 minute between runs.
04What if a DataRobot module is missing in Make?
Use Make an API Call. It calls any endpoint of the DataRobot API with the connection you already set up, so you are not limited to the 10 listed modules. Keep in mind that the Make documentation for this app is marked as AI-generated from DataRobot sources and may contain mistakes, so check important details with DataRobot directly before relying on them. If the call fails, read the error in the module bubble after a Run once.
05Should you use Make or n8n for DataRobot?
It depends on the tool your team already works in. In Make, DataRobot offers 10 modules covering chats, playgrounds, LLM blueprints and use cases, plus Make an API Call for the rest, and you connect it with an API key. The same app often has an n8n node as well. Compare what each tool offers for your exact case before choosing, rather than picking one by default. Whatever you choose, test with a single item before letting the flow handle real work.