Resources · Make integration

YepCode Run Make integrationAutomate YepCode Run with Make.

Need a scenario to hand work over to YepCode Run? The YepCode Run Make integration gives you 2 action modules, Run Code and Run Process, and no trigger. This guide covers the API token, a first scenario you can test, and what each module is for.

Try the YepCode Run integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the YepCode Run Make integration do for you?

The integration lets a Make scenario (the automation you build in Make, a chain of modules) send work to your YepCode Run account. A module is one brick of that chain. YepCode Run brings two of them, both actions: Run Code and Run Process. Something else has to start the scenario, because the app has no trigger.

Picture three setups. An operations lead gets a form entry from another app and passes it to Run Process, so the logic already kept in YepCode Run handles it. A developer drops Run Code after a spreadsheet module when a calculation is too awkward for Make's own tools. A support team chains both, with Run Code preparing the input before Run Process takes over.

Be honest about the gaps. The official documentation gives no description for either module and lists no fields, and it carries a notice saying it was written with AI and may contain mistakes. Check each field against the YepCode Run side before you rely on it. There is also no Make an API Call module here, so anything outside these two modules needs another route.

If you are new to scenarios, the Make training walks through the editor from scratch. YepCode Run may also exist as an n8n node; the n8n vs Make comparison lays out the differences between the two tools, and the Make agency team can build the scenario with you.

Connect

How do you connect your YepCode Run account to Make?

  1. 01

    Copy your API token

    In YepCode Run, open the Settings page, then the API Credentials tab. Copy the API token shown there. You need an active YepCode Run account first; its own pricing page covers subscriptions.

  2. 02

    Open the connection window

    Back in Make, add a YepCode Run module to your scenario and click Create a connection. A connection is your YepCode Run account linked to Make once, then reused by both modules.

  3. 03

    Paste the token and save

    Give the connection a clear label in Connection name if you like; the field is optional. Paste the token you copied, or follow the on-screen instructions, and save.

First scenario

Build your first scenario with YepCode Run

GoalWhen a new record lands in another app, Make hands it to a YepCode Run process with Run Process.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your records start. YepCode Run has no trigger, so it cannot open the flow on its own.

  2. 02

    Add Run Process

    Click the + on the right of that first module, search for YepCode Run and choose Run Process. Select the connection you created, or click Create a connection if you skipped that part.

  3. 03

    Map the incoming data

    Fill the module fields and map values from the first module into them. Each bundle, one item passed from one module to the next, becomes one run of Run Process.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each module received and confirm YepCode Run got what you expected.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module with Scheduling. A new scenario checks every 15 minutes by default. Then switch the scenario on so it keeps running without you.

Modules

What the YepCode Run modules do

YepCode Run gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

YepCode Run1

Run Code

ActionIn the docs only

You get a place to run a piece of code in YepCode Run from the middle of a scenario. The documentation gives no description, so this reading comes from the module name alone.

When to use it
a step needs logic that Make's built-in tools handle badly, such as a custom calculation on a bundle.
Watch out
the doc lists no fields, so check each one in the module against YepCode Run before trusting the output.
YepCode Run2

Run Process

ActionIn the docs only

This one lets a scenario start a process in your YepCode Run account, going by its name, since the doc offers no description. Each incoming bundle counts as one operation, the unit Make counts on your plan.

When to use it
the logic already lives in YepCode Run and you only need Make to feed it fresh data.
Watch out
run it once with a single bundle before switching the scenario on.
Need help

Need help automating YepCode Run with Make?

A person reads every message.

FAQ

YepCode Run and Make: common questions

01Is the YepCode Run Make integration free?
Yes, on the Make side. YepCode Run is a standard app, so it works 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 drop the interval to 1 minute and raise execution time to 40 minutes. Your YepCode Run subscription is a separate matter, covered by its own pricing page.
02What do you need to connect YepCode Run to Make?
An active YepCode Run account and its API token. In YepCode Run, open Settings, then the API Credentials tab, and copy the token shown on screen. In Make, add a YepCode Run module, click Create a connection, name it if you wish and paste the token. The same connection then serves both Run Code and Run Process, so you only do this once per account. If you manage several YepCode Run accounts, create one connection per account and give each a clear name.
03Can YepCode Run start a Make scenario in real time?
No. YepCode Run has no trigger module in Make, so it never starts a scenario by itself. You open the flow with a module from another app, such as a form or a spreadsheet, or you rely on the schedule on the first module. A new scenario runs every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Paid plans go down to 1 minute.
04What if the YepCode Run module you need is missing?
It depends on what is missing. The app offers only Run Code and Run Process, and it has no Make an API Call module to reach other parts of YepCode Run. If the task fits inside code or a process, one of those two modules usually covers it. Otherwise, look for another app in the Make catalog that does the job, or ask the team to review the scenario with you.
05Should you use Make or n8n for YepCode Run?
It depends on where the rest of your automations live. In Make, YepCode Run gives you two action modules, available from the Free plan, and the scenario needs another app or a schedule to start. YepCode Run may also have an n8n node, so check what each tool offers for your case. Neither is better by default; compare the modules and the plan limits against the job at hand. If most of your scenarios already run in Make, keeping YepCode Run there is usually simpler.
Same platform

Other docs you might need on this stack.

Browse all integrations