- Home
- Resources
- Integrations
- 0CodeUtil
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 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.
How do you connect 0CodeUtil to Make?
- 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.
- 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.
- 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.
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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
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.
Modules index
Binary to Text Converter
ActionIn the docs onlyReadable 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.
Currency Converter
ActionIn the docs onlyAn 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.
Date Planner
ActionIn the docs onlyA 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.
Email Validator
ActionIn the docs onlyA 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.
Execute JavaScript Code
ActionIn the docs onlyYour 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.
Geocoding
ActionIn the docs onlyCoordinates 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.
Image Meta/Exif data Reader
ActionIn the docs onlyThe 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.
Make an API Call
ActionIn the docs onlyAccess 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.
Multi Regex Parser
ActionIn the docs onlySeveral 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.
Reverse Geocoding
ActionIn the docs onlyA 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.
Secure Zip
ActionIn the docs onlyA 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.
Secure Zip Extractor
ActionIn the docs onlyGoing 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.
Sentiment Analyzer
ActionIn the docs onlyA 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.
Text Format Converter
ActionIn the docs onlyText 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.
Unicode to Text Converter
ActionIn the docs onlyPlain 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.
Need help automating 0CodeUtil with Make?
A person reads every message.