Skip to main content
Technical reference · Updated October 2026

How to Run JavaScript in Make.com (2026): Code, Costs & Limits

Current Make documentation checked Current third-party code options checked Current Latenode pricing model checked
Quick answer

The native way to run JavaScript in Make.com is the Make Code app. Add Make Code → Run code to a scenario, select JavaScript, map the inputs you need, write the code and run the module.

Make Code also supports Python. On current plans, Make charges 2 credits per second of code execution time. Core, Pro and Teams use a 30-second maximum execution sandbox, while Enterprise has a 300-second maximum.

The important tradeoff is not simply “native versus third party.” You need to compare execution cost, runtime, dependency access, API handling, data volume and whether code is an occasional helper or a central part of the workflow.

Cite this Make JavaScript reference

This page is maintained as a technical reference for the current Make Code limits, pricing model and alternative ways to execute JavaScript from a Make scenario.

Make.com is designed around visual scenarios, but some automation problems are easier to express in code: reshaping arrays, validating complex data, calculating values, parsing structured input, generating custom output or implementing business rules that would require a long chain of visual modules.

Make’s current answer is the Make Code app, a built-in module for JavaScript and Python. It is now the first option to investigate before adding an external execution service.

There are still good reasons to use an external code service. The deciding factors are usually runtime, cost, dependency access, execution model and how much of the workflow you want to keep inside Make.


Step by step

How to run JavaScript in Make.com

The simplest current setup uses Make’s native Code module. Make documents the module as a paid-plan feature with a built-in editor, input mapping, output handling and isolated execution.

01
Create or open your Make scenario.

Start with the trigger and any modules that generate the data your JavaScript needs.

02
Add Make Code → Run code.

The Code app is a native Make module rather than an HTTP call to another service.

03
Select JavaScript.

The same Code module also provides Python. The language is selected within the module.

04
Define the inputs.

Map values from previous modules into the Code module. They are exposed through the input object.

05
Write the JavaScript.

Use normal JavaScript syntax supported by Make’s documented runtime and return the value or object that subsequent modules need.

06
Run once and inspect the output.

Make exposes execution output and error information so you can test the transformation before putting the scenario into production.

A simple Make Code example

Suppose the previous module supplies two dates. The Code module can calculate the number of days between them and return a structured result.

// Values mapped from previous Make modules
const { start_date, end_date } = input;

const start = new Date(start_date);
const end = new Date(end_date);

if (
  Number.isNaN(start.getTime()) ||
  Number.isNaN(end.getTime())
) {
  throw new Error("Invalid date");
}

const days =
  Math.floor(
    (end.getTime() - start.getTime()) /
    (1000 * 60 * 60 * 24)
  );

return {
  days
};

Make’s current documentation uses the same general input-object pattern and provides a date-difference example in its official Code documentation. See Make Code documentation →


What you actually get

What Make Code provides

Make Code is more capable than the old “paste a tiny JavaScript snippet” description suggests. The current documentation describes an isolated sandbox, an editor with autocompletion and error highlighting, access to standard output and error logs, dynamic code input, scenario blueprint sharing and support for both JavaScript and Python.

Languages

2

JavaScript and Python are supported in the same Code app.

Standard RAM

512 MB

The standard Core, Pro and Teams sandbox documentation specifies 512 MB.

Standard runtime

30 sec

The documented Core, Pro and Teams maximum execution time.

Enterprise

300 sec

Enterprise has 2 CPUs, 1 GB RAM and a 300-second maximum.

Important product-status detail

Make’s current app documentation still labels Make Code as Open Beta and notes that functionality and pricing may change. Treat product limits as a living reference and re-check the official documentation when making a purchase decision.


Current limits

Make Code runtime limits in 2026

The current official feature table gives two runtime environments. Core, Pro and Teams receive the standard sandbox, while Enterprise receives the larger execution environment.

Make Code JavaScript and Python runtime limits by plan
PlanCPURAMMaximum executionCustom dependencies
Core1 CPU512 MB30 secondsNo
Pro1 CPU512 MB30 secondsNo
Teams1 CPU512 MB30 secondsNo
Enterprise2 CPUs1,024 MB300 secondsYes

Source: Make Code — official application documentation .

Do not confuse runtime with billing

The maximum runtime determines how long the Code execution can run. The billing model is separate: Make Code consumes 2 credits for every second of code execution time. The billed execution time excludes backend processing time.


The part most tutorials skip

How much does JavaScript cost in Make.com?

Make’s general billing model is credit-based. Most non-AI module actions use a fixed rate, normally one credit per operation. Make Code is a specific exception: it consumes 2 credits per second of code execution.

That means execution time matters. A two-second Code execution consumes about four credits; a five-second execution consumes about ten; a ten-second execution consumes about twenty.

Make Code credits consumed at different JavaScript execution times
Execution timeMake Code creditsMonthly runsCode credits consumed
1 second21,0002,000
2 seconds41,0004,000
5 seconds101,00010,000
10 seconds201,00020,000
30 seconds601,00060,000

The important distinction is that these are Code-module credits, not the total credits for your complete scenario. Other modules may consume additional credits.

Make’s official pricing also states that credit usage varies by feature and that Make Code is an exception to the normal one-credit-per-operation model. See Make’s current credit documentation →


Dependencies

Can you install NPM packages in Make Code?

This is one of the biggest practical differences between Make plans.

Make currently documents standard JavaScript libraries including moment, moment-timezone and lodash. For Python, it documents pendulum, toolz and requests.

Enterprise adds the ability to import custom dependencies. Make’s current documentation shows an axios example using the additional-dependencies setting.

Make Code dependency access by plan
CapabilityCoreProTeamsEnterprise
JavaScriptYesYesYesYes
PythonYesYesYesYes
moment / moment-timezone / lodashYesYesYesYes
Custom dependency installationNoNoNoYes

Don’t describe Make Code as unrestricted Node.js

That would be inaccurate for most Make plans. The native module gives you a controlled execution environment and documented built-in libraries. Arbitrary additional dependencies are an Enterprise capability according to Make’s current app documentation.


Security

Can Make Code call APIs?

Yes. Make’s official examples demonstrate API requests from Code, including JavaScript using fetch().

But Make explicitly recommends considering the standard HTTP module for API requests when credentials need protection. The reason is that Code execution, logging and mapped input can expose information depending on how the scenario is built.

const response =
  await fetch("https://example.com/api/data");

if (!response.ok) {
  throw new Error(
    `Request failed: ${response.status}`
  );
}

const data = await response.json();

return data;

For API keys, OAuth credentials and other secrets, put authentication in the appropriate Make connection or HTTP module whenever that is the safer architecture rather than embedding credentials in code.


External code options

0CodeKit vs 1001fx vs Make Code

External JavaScript services still have a legitimate place. They can be useful where Make Code’s dependency model, execution limits or native feature set do not fit the job.

Native

Make Code

JavaScript and Python directly inside Make. 2 credits per second of code execution. Built-in libraries are available on paid plans, while custom dependencies are an Enterprise capability.

External executor

0CodeKit

JavaScript runs on a Bun-based Linux sandbox. Its current documentation states a 180-second execution limit, 512 MB memory limit and 50 0CodeKit credits per execution.

External function service

1001fx

Execute JavaScript is listed at 5 1001fx credits per item. It provides a defined set of JavaScript packages and does not allow arbitrary imports.

Comparison of Make Code, 0CodeKit and 1001fx for executing JavaScript
CapabilityMake Code0CodeKit1001fx
Runs JavaScriptYesYesYes
Runs PythonYesYesNot the focus of Execute JavaScript
Execution pricing2 Make credits / second50 0CodeKit credits / execution5 1001fx credits / item
Execution limit30 sec standard; 300 sec Enterprise180 secProvider documentation should be checked for current limits
Custom dependenciesEnterpriseNPM-style packagesDefined package list; imports disabled
Extra accountNoYesYes

Sources: 0CodeKit JavaScript Executor and 1001fx Execute JavaScript .

Cost warning

Do not compare “credits” across these companies as though one credit has the same monetary value. Make credits, 0CodeKit credits and 1001fx credits are different billing units. Compare their actual plan prices and expected usage instead.


Alternative architecture

What about Latenode?

Latenode is worth considering when JavaScript is becoming a major part of the workflow rather than an occasional helper. Its current platform documentation describes full JavaScript nodes, data passing between nodes, npm imports and an AI assistant for generating, modifying and debugging code.

However, the pricing comparison needs to be updated from older Latenode material. Current Latenode documentation uses CPU seconds rather than the old “one credit per 30 seconds” model for new Pay-As-You-Go accounts. The current Free tier includes 10,000 CPU seconds per month; additional CPU seconds are billed at tiered rates.

Current execution model comparison between Make Code and Latenode
QuestionMake CodeLatenode
JavaScriptYesYes
PythonYesJavaScript-focused code node
Execution billing2 Make credits / secondCPU-second based
Free compute allowanceMake’s normal credit allowance; Code is paid-plan only10,000 CPU seconds / month
Custom NPM packagesEnterprise capabilityDocumented npm imports in JavaScript
AI-assisted codeMapped Code can be supplied dynamicallyAI Assistant inside JavaScript tooling
Workflow integrationNative Make moduleNative scenario node

Latenode’s current billing documentation also distinguishes wall-clock duration from billed CPU seconds, so a cost comparison should not simply multiply the visible scenario duration by a fixed rate.

Do not use the old Latenode comparison from outdated pages

Older Latenode documentation describes execution credits where one credit represented 30 seconds. That documentation is now archived for legacy accounts. Newer accounts use CPU seconds and Pay-As-You-Go billing.


Architecture guide

Which JavaScript approach fits which workload?

A
Use Make Code for short, occasional custom logic.

This is the natural choice when the scenario already lives in Make and the code completes quickly within the documented runtime.

B
Use Make Code Enterprise when dependency access is the blocker.

Enterprise adds custom dependency support and the larger 300-second execution environment documented by Make.

C
Use 0CodeKit or 1001fx for targeted external functions.

This can make sense when you need a particular utility or package outside Make’s native feature set and are comfortable maintaining the additional provider connection.

D
Consider Latenode when code becomes central to the architecture.

A JavaScript-heavy workflow can be easier to structure when code, data transformation, HTTP calls and workflow logic are all designed together rather than treating code as an exception inside a visual scenario.

The practical decision

The important question is not “Which platform is best?” It is “Where does the code belong in this particular workflow?” Keep small logic close to the automation when that is efficient. Change the execution architecture when runtime, dependency, cost or maintainability becomes the bottleneck.


Practical examples

Useful JavaScript tasks inside Make

1. Filter and transform an array

Array transformation
const items = input.items || [];

const result = items
  .filter(item => Number(item.price || 0) >= 100)
  .map(item => ({
    id: item.id,
    price: Number(item.price)
  }));

return { result };

2. Normalize incoming data

Data normalization
const email =
  String(input.email || "")
    .trim()
    .toLowerCase();

return {
  email,
  valid: /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(email)
};

3. Apply business rules

Business logic
const amount = Number(input.amount || 0);
const status =
  amount >= 1000
    ? "high"
    : amount >= 250
      ? "medium"
      : "low";

return {
  amount,
  status
};

These are good Code-module workloads because the code produces a compact result that can immediately be mapped into downstream Make modules. Large API orchestration, long-running computation or dependency-heavy applications are different architectural problems.


Reference material

Primary sources used for this guide

Product limits and pricing can change. The following first-party documentation is the source trail behind the factual claims on this page.


Answers

Frequently asked questions about JavaScript in Make.com

How do you run JavaScript in Make.com?

Add the Make Code module to a scenario, choose JavaScript in the Language field, define the input values you need from previous modules, write the code in the editor, and test the module with Run once. The native Make Code app also supports Python.

Is Make Code available on the free plan?

No. Make’s current documentation says the Make Code app is available to customers on paid plans.

How much does Make Code cost?

Make Code uses dynamic credit billing of 2 credits for every second of code execution time. Make says the billed execution time excludes backend processing time.

What is the Make Code timeout?

Make’s current documentation lists a 30-second maximum execution time for the standard Core, Pro and Teams sandbox, and a 300-second maximum execution time for Enterprise.

Can Make Code run Python?

Yes. The native Make Code module supports both JavaScript and Python.

Can you install NPM packages in Make Code?

Make includes standard JavaScript libraries such as moment, moment-timezone and lodash. Custom dependencies can be added on Enterprise plans. Core, Pro and Teams do not have the same custom dependency capability.

What JavaScript libraries are included with Make Code?

Make currently documents moment, moment-timezone and lodash for JavaScript. Its documented Python libraries include pendulum, toolz and requests.

What are 0CodeKit and 1001fx?

They are third-party services with Make integrations that can execute JavaScript and provide other utilities. 0CodeKit documents a JavaScript executor using Bun with a 180-second execution limit and 50 0CodeKit credits per execution. 1001fx documents Execute JavaScript at 5 of its own credits per item and provides a defined list of supported packages.

Is Latenode cheaper than Make Code?

There is no universal answer because the billing models differ. Make Code uses 2 Make credits per second of code execution. Latenode currently uses CPU-second billing, includes 10,000 CPU seconds on its Free plan, and then uses tiered per-second pricing. A meaningful comparison needs the Make plan, run count, execution time and the amount of the Latenode scenario being measured.

Can Make Code call an API?

Yes. Make documents API requests from Code, but recommends considering the HTTP module when credential protection is important.

Can JavaScript in Make replace an iterator?

Sometimes. A Code module can process arrays and perform filtering, mapping and other transformations in one execution. Whether that is appropriate depends on the workflow, data size and resulting credit usage.


Disclosure: CreatorOpsMatrix is an independent technical publication. Software links on this page may include affiliate relationships. Any affiliate relationship does not change the product facts or pricing methodology presented here. Pricing, limits and product capabilities can change, so the linked first-party documentation remains the final source for current account-specific terms.

Scroll to Top