Resources · Make integration

e2b.dev Make integrationAutomate e2b.dev with Make.

Need a scenario to run real code without leaving Make? The e2b.dev Make integration gives you 1 action module that sends Python or JavaScript to E2B. This page is for builders who already know E2B: connect it, place the module, test it once.

Try the e2b.dev integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the e2b.dev Make integration do?

The e2b.dev Make integration lets a Make scenario hand a piece of Python or JavaScript to E2B, which runs it outside of Make. A scenario is the automation you build in Make, a chain of modules; a module is one brick of it. Here the app brings a single action module, so another app or a schedule starts the flow.

Code where the built-in tools stop. A support team pulls a ticket from its helpdesk app and needs a calculation that the usual Make tools make awkward. The next module, Run Python or Javascript Code on E2B, runs a short script and passes its output on as a bundle, meaning one item that flows to the following module.

A script on a fixed schedule. With no trigger in the app, a data analyst can simply let the scenario's clock start it. The default schedule of a new scenario is every 15 minutes, and the code module does the work each time.

A cleanup step inside a longer chain. A form tool such as the one on the 123FormBuilder Make integration page collects answers, then E2B reshapes them in JavaScript before they reach the next app.

Know the limits before you start. Make's own documentation for e2b.dev is limited, because little public information about the app exists, so the fields of the module are not described there. Test with care. For a wider look at the platform, read the Make review, and if you also weigh n8n for code steps, the n8n vs Make comparison lays out both tools.

Connect

How do you connect e2b.dev to Make?

  1. 01

    Add the module and open the connection

    In your scenario, add Run Python or Javascript Code on E2B and click Create a connection. A connection is your e2b.dev account linked to Make once, then reused by every module of the app.

  2. 02

    Give the connection a name

    This step is optional, but a clear name helps as soon as you keep more than one E2B account, for instance a test account and a production account. Pick a label that tells them apart at a glance.

  3. 03

    Authorize and save

    Follow what Make asks for: either approve access on the e2b.dev page that opens, or paste the key that e2b.dev gives you. Then click Save and the module is ready to fill.

First scenario

Your first scenario with e2b.dev

GoalWhen another app sends a new item to the scenario, Make passes it to E2B, which runs your code and returns the result.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since e2b.dev has no trigger, choose the app that holds your data, such as a form tool or a spreadsheet.

  2. 02

    Set the starting module

    Connect that first app and fill its fields. Once the connection exists, Make lists the folders, sheets or objects it can read, so you pick from a list instead of typing paths by hand.

  3. 03

    Add the E2B module

    Click the + on the right of the first module, search for e2b.dev and pick Run Python or Javascript Code on E2B. Create the connection, then map the data from the previous module into the module fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubbles above each module to read the bundles they received and check that the E2B step returned the output you expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each run of each module counts as an operation, the unit Make tallies on your plan.

Modules

What the e2b.dev module does

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

e2b.dev1

Run Python or Javascript Code on E2B

Action

In Make“Code execution outside of Make via E2B”

You get a code step inside your scenario: this action sends a Python or JavaScript snippet to E2B, the code runs there rather than inside Make, and the scenario carries on with what comes back.

When to use it
a value from a previous app needs logic that plain mapping in Make cannot express, like a custom calculation or text reshaping.
Watch out
Make's documentation for this app is limited, so test each change with Run once before you switch the scenario on.
Need help

Need help automating e2b.dev with Make?

A person reads every message.

FAQ

Questions about e2b.dev and Make

01Is the e2b.dev Make integration free?
Yes, on the Make side. e2b.dev is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow up to 40 minutes of execution. Usage is counted in operations each month. Your E2B account is a separate matter that this page does not cover.
02What do you need to connect e2b.dev to Make?
An e2b.dev account and a Make account are enough to start. Make's documentation lists no prerequisite and no official connection steps for this app, so the generic flow applies: add the module, click Create a connection, optionally name it, then approve access on the e2b.dev page or paste the key the app gives you, and click Save. From then on, every scenario that uses the module picks up the same connection, and if a field looks unclear, your E2B account settings are the place to check.
03Does e2b.dev trigger a Make scenario in real time?
No, because e2b.dev has no trigger module at all. Its single module is an action, so something else has to start the scenario. You can open the flow with a trigger from another app, such as a form or a helpdesk, or let the scenario run on its own schedule, which is every 15 minutes by default on a new scenario. The Free plan keeps that interval at 15 minutes minimum, while paid plans go down to 1 minute.
04What if the e2b.dev module you need is missing in Make?
It depends on what you need. The app offers one action, Run Python or Javascript Code on E2B, and no Make an API Call module, so this app gives you no generic way to reach other E2B features. Often the code step itself covers the gap, since your script decides what happens. If not, look for another app in Make that fits the job, or ask the Make agency team for help with a custom setup.
05Should you use Make or n8n with e2b.dev?
It depends on the tool your team already works in. Many apps that Make supports also have a node in n8n, so check whether E2B is available there before you decide. On the Make side, you get one action module that runs Python or JavaScript on E2B and fits into scenarios alongside the 3,000+ standard apps. Compare how each editor feels for your use case, then pick the one your team is most comfortable maintaining over time.
Same platform

Other docs you might need on this stack.

Browse all integrations