Resources · Make integration

Make Code Make integrationAutomate Make Code with Make.

What if one step of your automation could run your own script? The Make Code Make integration gives you 1 action module that executes JavaScript or Python inside a scenario. This page shows who it suits, how to add it and how to test a first flow.

Try the Make Code integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Make Code Make integration do?

Make Code is a built-in Make app with a single module, Actions, that runs a piece of JavaScript or Python in the middle of a scenario (the automation you build in Make, a chain of modules). You type the code in an editor with syntax coloring, autocompletion and error highlighting, or you pass it in from an earlier module.

Take an online store whose order export arrives with messy product names. Place the Actions module right after the app that sends each order, write a few lines that clean the text, and hand the tidy result to the module that follows. Each item that flows between modules is called a bundle: one order, one contact, one row.

A second pattern suits a marketing team: a form tool sends raw answers, Make Code turns them into a score with your own rule, and the next module files the lead. A third one helps an ops manager who receives code stored in another tool: Make Code can run that code as it comes from the previous module, instead of a script you typed by hand.

Your code runs in an isolated sandbox, and the module shows standard output and error logs, so you can test without an outside tool. Built-in libraries exist for both languages; importing your own libraries needs an Enterprise account. The code travels with the scenario when you download its blueprint, which helps when a colleague rebuilds it.

Know the limits before you start. Make Code is in Open Beta, open to customers on paid plans, and its features and pricing may change; the Make pricing page covers the plans. Make support does not debug your JavaScript or Python. If you also weigh n8n for scripted steps, read n8n vs Make, and the Make training page helps you get comfortable with the editor first.

Connect

How do you add Make Code to a scenario?

  1. 01

    Add the module

    In your scenario, click the + where you want the script to run, search for Make Code and pick Actions. The module drops into the chain at that spot, after the app whose data you plan to process.

  2. 02

    Link an account if Make asks

    Make links an app once through a connection, then reuses it in every module of that app. If the module shows Create a connection, click it and give the connection a name your team will recognize later.

  3. 03

    Confirm and save

    Follow the authorization Make displays, either the app page or a key to paste, then click Save. Back in the module, you can start writing your JavaScript or Python in the editor.

First scenario

Build your first scenario with Make Code

GoalWhen another app sends a bundle, Make Code runs your script on it and passes the result on.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app that holds your data first, for example a form tool or a spreadsheet, and set up its module.

  2. 02

    Add the Actions module

    Click the + on the right of that first module, search for Make Code and choose Actions. It sits second in the chain, ready to receive what the first module sends.

  3. 03

    Write the code and map the data

    Choose JavaScript or Python, type your script in the editor and map the values from the previous module into it. Error highlighting flags a typo before you even test.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Then read the bundles Make Code received, and check its logs if the script failed.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What the Make Code module can do

Make Code gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Make Code1

Actions

ActionIn the docs only

With Actions, you drop your own JavaScript or Python into a scenario and the modules that follow get its result.

When to use it
pick it when no ready-made module of Make does the transformation you need, such as a custom scoring rule or a text cleanup on each bundle.
Watch out
the runtime is Python 3.12.11 and Node 20.19.4, and Make support will not troubleshoot your code, so read the error logs yourself.
Need help

Need help automating Make Code with Make?

A person reads every message.

FAQ

Make Code and Make: common questions

01Is the Make Code Make integration free?
No. Make Code is in Open Beta and the documentation reserves it for customers on paid plans, so the Free plan is not enough. Free still gives you 2 active scenarios and a minimum of 15 minutes between scheduled runs, which is fine for learning the editor with other apps. Paid plans bring a minimum interval of 1 minute and unlimited active scenarios. Since Make Code is a beta feature, its functionality and pricing may change, so check the current terms before you build something your team relies on.
02What do you need to use Make Code in a scenario?
You need a Make account on a paid plan, because Make Code is an Open Beta feature open to paid customers. The documentation lists no other prerequisite. You also need to be able to write or adapt JavaScript or Python: the module runs Python 3.12.11 and Node 20.19.4, with built-in libraries for both. If your code depends on a custom library, importing it requires an Enterprise account. If the module asks for a connection, click Create a connection, follow the prompt and click Save.
03Can Make Code start a scenario on its own?
No. Make Code has no trigger, only the Actions module, so something else has to start the scenario. You can put a trigger from another app first, so the script runs whenever that app sends a new bundle. You can also start the scenario from its schedule, set on the first module and every 15 minutes by default on a new scenario. On the Free plan the shortest interval is 15 minutes, on paid plans it drops to 1 minute. Either way, Make Code works as a step inside the chain.
04What if the Make Code module is not enough?
It depends on the blocker. Make Code has no Make an API Call module, so the answer is not another Make Code module. If your data lives in a specific tool, look for that tool's own app in Make and let Make Code handle only the transformation. If your script fails, the error logs in the module are your main clue, because Make support does not troubleshoot JavaScript or Python code. When a scenario gets stuck at that step, the Hack'celeration team can review it with you.
05Should you use Make or n8n for scripted steps?
It depends on where the rest of your automations live. If your scenarios already run in Make and you are on a paid plan, Make Code keeps your script inside the same scenario, next to the other modules, and saves it in the blueprint you download. If your team works in n8n, compare the options there before moving a single step. The criteria that matter are the plan you already pay for, the language your team writes, and who will maintain the code. Neither tool is ranked here.
Same platform

Other docs you might need on this stack.

Browse all integrations