Resources · Make integration

0CodeUtil Make integrationAutomate 0CodeUtil with Make.

Need to clean, convert or check data between two apps without writing code? The 0CodeUtil Make integration adds 15 action modules to your scenarios, from email checks to geocoding. This page shows how to connect it and build a first flow, one click at a time.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the 0CodeUtil Make integration do for you?

The 0CodeUtil Make integration gives your scenarios a box of utility tools: 15 action modules that convert, check, parse or compute data while it travels between two other apps. A scenario is the automation you build in Make, and a module is one brick of it. Since 0CodeUtil has no trigger, it always sits in the middle of a flow, never at the start.

Clean leads before they reach the CRM. A form tool sends a new entry, Email Validator looks at the address, and only then does the contact move on to your sales app.

Customer messages sorted by tone. Reviews or support emails pass through Sentiment Analyzer, while Multi Regex Parser pulls the order number out of the text so the team knows which case it is dealing with.

Addresses ready for a map, amounts ready for the books. Geocoding turns a delivery address into coordinates, Reverse Geocoding does the opposite for a phone position, and Currency Converter brings an order total into the currency you report in.

What Make does not give you here is detail. Its documentation for 0CodeUtil lists the module names and warns that public information on the app is limited, so plan to learn each module by testing it with Run once and reading what comes back. The Make troubleshooting guide helps when a run fails, the Make training covers the editor from scratch, and n8n vs Make is worth a read if you are still choosing a tool.

Connect

How do you connect 0CodeUtil to Make?

  1. 01

    Add a 0CodeUtil module

    Open your scenario, click the + and search for 0CodeUtil. Pick any of its modules, then click Create a connection. A connection is your 0CodeUtil account linked to Make once, and every other 0CodeUtil module reuses it.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later; this part is optional. Then authorize Make on the 0CodeUtil page that opens, or paste the key 0CodeUtil gives you, whichever the window asks for.

  3. 03

    Save and reuse it

    Click Save. The module now shows your connection and its fields open up. When you build a second scenario with 0CodeUtil, pick this same connection from the list instead of creating a new one.

First scenario

Your first scenario with 0CodeUtil

GoalWhen a contact form in another app sends a new message, Make checks the sender's email with 0CodeUtil and reads the tone of the message.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Because 0CodeUtil has no trigger, this opening module comes from your form app.

  2. 02

    Start with your form app

    Search for your form tool, pick the module that picks up new entries and click Create a connection. From here on, each entry travels as one bundle: the single item handed from one module to the next.

  3. 03

    Add Email Validator

    Click the + on the right of the form module, search 0CodeUtil and choose Email Validator. Select your 0CodeUtil connection, then map the email address from the form into it.

  4. 04

    Add Sentiment Analyzer

    Click the + again, add Sentiment Analyzer and map the message text from the form. Every module run on a bundle counts as one operation, the unit Make tallies on your plan.

  5. 05

    Test with Run once

    Click Run once, send a test entry through your form, then open the bundles each module received. This is where you learn what 0CodeUtil really returns before you rely on it.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. The Free plan lets you keep 2 scenarios active at the same time.

Modules

What each 0CodeUtil module is for

0CodeUtil gives you 15 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

0CodeUtil1

Binary to Text Converter

ActionIn the docs only

Readable text out of binary data is what this module's name promises. It sits between a module that hands over raw content and one that expects words, and Make documents nothing beyond that name.

When to use it
a file or content from another app arrives as raw binary data and the next step, say Sentiment Analyzer, needs plain text.
Watch out
no input format is described, so click Run once and open the bundle before mapping anything further.
0CodeUtil2

Currency Converter

ActionIn the docs only

An amount restated in another currency, going by the module's name, so an order total can land in your books in the currency you report in. Rates, their source and the list of currencies are not documented.

When to use it
an invoice or order from another app shows a foreign currency and your accounting tool wants yours.
Watch out
after Run once, compare one converted amount with a figure you trust before switching the scenario on.
0CodeUtil3

Date Planner

ActionIn the docs only

A date worked out for you, judging by the name: a due date or a follow-up day computed inside the scenario instead of by hand. What the module accepts as input is not described anywhere in Make.

When to use it
a signed quote or a fresh support ticket should come with a planned date for the next step.
Watch out
a date can shift by a day without anyone noticing, so read the returned value in the Run once bundle.
0CodeUtil4

Email Validator

ActionIn the docs only

A verdict on an email address before you use it, which is what this module's name announces. It helps keep a mistyped or fake address out of your CRM or mailing tool. The checks it runs are not documented.

When to use it
a form entry or new lead carries an address you plan to write to.
Watch out
run one valid and one broken address through Run once to see both answers, then decide how the next module uses them.
0CodeUtil5

Execute JavaScript Code

ActionIn the docs only

Your own short piece of JavaScript, run as a step of the scenario, covers a calculation or a reshaping of data that no ready-made module offers. Make does not say what the code can reach or which options exist.

When to use it
none of the named 0CodeUtil modules fits the transformation you need.
Watch out
a Free plan run stops after 5 minutes at most, so test the code on one bundle before feeding it a long list.
0CodeUtil6

Geocoding

ActionIn the docs only

Coordinates for a postal address, as the name Geocoding suggests, so a delivery point or a store can be placed on a map by the module that follows. The output layout is not documented.

When to use it
a new customer or order from your shop carries an address, and your map or routing tool expects coordinates instead.
Watch out
check with a real sample what an incomplete address gives back before the scenario runs unattended.
0CodeUtil7

Image Meta/Exif data Reader

ActionIn the docs only

The hidden details stored inside a photo file, its metadata and EXIF block, read out so the next module can use them. Which details come back is not listed in Make's documentation.

When to use it
photos arrive through a form or a shared folder and you want to sort, tag or check them by what the file itself records.
Watch out
the Free plan handles files up to 5 MB, and full-size originals from a camera can exceed that.
0CodeUtil8

Make an API Call

ActionIn the docs only

Access to any endpoint of the 0CodeUtil API, through the same connection as the other modules. This is Make's universal module for the app, your way around a function that has no module of its own.

When to use it
the utility you need exists in 0CodeUtil but not in the module list above or below.
Watch out
you write the request yourself, which assumes you know the endpoint; with the app's thin documentation, test it on a single bundle first.
0CodeUtil9

Multi Regex Parser

ActionIn the docs only

Several values pulled out of one block of text, if the name is a fair guide: an order number, a date and an amount from the body of an email, for instance. The name suggests you describe each one with a regular expression, a search pattern for text.

When to use it
messages from another app follow a steady layout and you want their parts as separate values.
Watch out
a pattern that matched your sample can miss the next message, so run several real texts first.
0CodeUtil10

Reverse Geocoding

ActionIn the docs only

A street address for a pair of coordinates, the reverse of Geocoding as the name says, so a GPS position from a phone or tracker becomes a place a person can read.

When to use it
a delivery confirmation or a field check-in arrives as latitude and longitude, and your team needs an address in its report.
Watch out
the language and level of detail of the returned address are not documented, so read one bundle before mapping it.
0CodeUtil11

Secure Zip

ActionIn the docs only

A protected ZIP archive built from your files, if the name describes it well, ready to send to a client or to store. Make says nothing about the protection method or its settings.

When to use it
contracts or data exports produced by another app must leave the scenario bundled and locked.
Watch out
on the Free plan, each file stays under 5 MB and total transfer under 512 MB, a ceiling that batches of archives reach faster than single files.
0CodeUtil12

Secure Zip Extractor

ActionIn the docs only

Going by its name, the files inside a protected ZIP archive, opened up so each can move on to the next module. It is the natural partner of Secure Zip on the receiving side.

When to use it
a client sends a locked archive by email or upload and its content must be filed or read.
Watch out
after Run once, count the bundles that come out, because each module run on each bundle is one operation on your plan.
0CodeUtil13

Sentiment Analyzer

ActionIn the docs only

A read on the mood of a text, as the name implies, so a review or a support message can be routed by tone instead of being read one by one. The scale or labels it returns are not documented.

When to use it
customer reviews or ticket messages arrive from another app and the team wants to see unhappy customers first.
Watch out
compare a handful of results with your own reading before letting the scenario act on them.
0CodeUtil14

Text Format Converter

ActionIn the docs only

Text rewritten from one format into another, which is what Text Format Converter announces. The supported formats are not documented, so the options shown inside the module are the ones that count.

When to use it
content written in one app must land in another that expects a different format, for example notes headed to a newsletter tool.
Watch out
open the result in the destination app after Run once, since layout details can shift in the conversion.
0CodeUtil15

Unicode to Text Converter

ActionIn the docs only

Plain characters where escape codes used to be, going by the module's name, so an accented name or a symbol reads normally again in the next app.

When to use it
names or messages exported from another tool show sequences of codes where letters should appear.
Watch out
this module and Binary to Text Converter both hand back text; pick this one when the input is already text, only encoded, and check the result in the Run once bundle.
Need help

Need help automating 0CodeUtil with Make?

A person reads every message.

FAQ

0CodeUtil and Make: common questions

01Is the 0CodeUtil Make integration free?
Yes. 0CodeUtil is a standard app in Make, so it works on the Free plan. That plan comes with limits: 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes per run at most, files up to 5 MB and 512 MB of data transfer. Paid plans, namely Core, Pro, Teams and Enterprise, bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Make counts usage in operations, one per module run on one bundle, so a flow with three modules spends three operations per entry. Whether 0CodeUtil charges for its own account is not covered by Make.
02What do you need to connect 0CodeUtil to Make?
An 0CodeUtil account and a Make account; the documentation lists no other prerequisite. Add any 0CodeUtil module, click Create a connection, name it if you like, then authorize Make on the 0CodeUtil page or paste the key the app provides, and click Save. The connection is created once and shared by all 15 modules, so there is nothing to repeat for the next scenario. Make also warns that public information on 0CodeUtil is limited: if the window asks for something unexpected, the answer is more likely to sit in your 0CodeUtil account than in Make's pages.
03Can 0CodeUtil start a Make scenario in real time?
No, because 0CodeUtil has no trigger: its 15 modules are all actions. A trigger is the first module, the one that starts a scenario. To use 0CodeUtil, open the flow with another app's trigger, such as a form, an inbox or a spreadsheet, or with a schedule on that first module, every 15 minutes by default. Whether the start feels instant then depends on the other app. An instant trigger is called by the app through a webhook as soon as something happens, while a scheduled one is checked by Make at an interval, never more often than every 15 minutes on the Free plan.
04What if a 0CodeUtil module is missing in Make?
Use Make an API Call. This module comes with 0CodeUtil in Make and lets a scenario call any endpoint of the 0CodeUtil API with the same connection as the other modules. It fits a function that has no dedicated module. You write the request yourself, so it takes more care than the ready-made modules: test it with Run once and read the returned bundle before mapping anything. If the obstacle is a Free plan limit instead, note that paid plans allow 40 minutes per run against 5 on Free, and a 1 minute interval between scheduled runs.
05Should you use Make or n8n for 0CodeUtil?
It depends on your criteria rather than on a winner. On Make, 0CodeUtil comes as 15 ready modules plus Make an API Call, usable from the Free plan, which suits a team that wants to add a utility step without writing code. The same app often has a node on n8n as well, so look at what that node offers before deciding. Compare, for your exact task, which modules each side provides, how your team prefers to build, and the limits of the plan you would run. The n8n vs Make comparison linked earlier on this page lays out the wider differences between the two tools.