Resources · Make integration

uClassify Make integrationAutomate uClassify with Make.

Want every incoming text sorted without reading it yourself? The uClassify Make integration gives you 3 action modules to classify texts, translate them to English and reach the rest of the API. This page shows you how to link your account and build a first working scenario.

Try the uClassify integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the uClassify Make integration do for you?

The uClassify Make integration lets a Make scenario (the automation you build, a chain of modules) send text to your uClassify account and get the result back, without writing code. Each module is one brick of that chain, and uClassify brings three of them, all actions.

Sort support messages by topic. A form or mailbox module from another app hands over the message, Classify Texts sends it to uClassify, and the answer decides where the ticket goes next. Each item passed along is a bundle: here, one message.

Handle text written in other languages. Put Translate to English before the classification step when your customers write in several languages, so the rest of the scenario always works on English text.

Reach what the listed modules skip. Make an API Call calls any endpoint of the uClassify API with the same connection, for the cases the two other modules do not cover.

Keep one limit in mind: uClassify has no trigger in Make, so it never starts a scenario by itself. Another app, a schedule or a webhook of Make has to begin the flow. The Make documentation page for uClassify also states that its content is AI-generated and asks you to verify important details. If you are weighing tools, the n8n vs Make comparison sets out the criteria, and the Make pricing guide explains how operations are counted. For a guided start, see our Make training.

Connect

How do you connect uClassify to Make?

  1. 01

    Copy your API key from uClassify

    You need a registered uClassify account first. Log in, open your account dashboard, click the tab labeled Api Keys and copy the key shown on screen. Keep it at hand for the next step.

  2. 02

    Add a uClassify module in Make

    In your scenario, add any uClassify module, for example Classify Texts, then click Create a connection. A connection is your uClassify account linked to Make once and reused by all three modules.

  3. 03

    Paste the key and save

    Give the connection a name in the Connection name field if you like; it is optional. Paste the API key you copied, or follow the on-screen instructions, and save. The module can now talk to your account.

First scenario

Build your first scenario with uClassify

GoalWhen a new text arrives from another app, Make translates it to English and has uClassify classify it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since uClassify has no trigger, start with the app that receives your texts, such as a form tool or a mailbox.

  2. 02

    Add Translate to English

    Click the + on the right of that first module, search for uClassify and pick Translate to English. Create the connection, then map the text coming from the previous module into the module fields.

  3. 03

    Chain Classify Texts

    Add Classify Texts with the next +. It reuses the same connection. Map the translated text from the step before, so uClassify always reads English whatever language the sender used.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Then read the bundles each module received and check the classification before you rely on it.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What the uClassify modules do

uClassify gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

uClassify1

Classify Texts

ActionIn the docs only

This module hands your texts to uClassify and brings the classification back into the scenario, so the next modules can route, tag or store each text according to the answer.

When to use it
incoming reviews, tickets or survey answers need a label before anyone reads them, and a router or filter should act on that label.
Watch out
click Run once and read the output bundle before mapping its values further, so you see exactly what comes back for your own texts.
uClassify2

Make an API Call

ActionIn the docs only

Here you get direct access to any endpoint of the uClassify API, signed with the connection you already created, which fills the gaps left by the two ready-made modules.

When to use it
you need an API feature that neither Classify Texts nor Translate to English exposes, and you still want to stay inside the same scenario without a separate HTTP setup.
Watch out
you build the request yourself, so keep the uClassify API documentation open next to the editor.
uClassify3

Translate to English

ActionIn the docs only

With this step, a text written in another language comes out in English, ready for the modules that follow or for a colleague who only reads English.

When to use it
place it right before Classify Texts when messages reach you in several languages, so every text is judged on the same footing.
Watch out
it adds one operation per bundle, so skip it in scenarios where your texts are already in English.
Need help

Need help automating uClassify with Make?

A person reads every message.

FAQ

Questions about the uClassify Make integration

01Is the uClassify Make integration free?
Yes, on the Make side. uClassify is a standard app, available from the Free plan, which 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 count usage in operations per month. Your uClassify subscription is a separate matter: the documentation points to the uClassify pricing page for that.
02What do you need to connect uClassify to Make?
A registered uClassify account and its API key. After logging in to uClassify, open your account dashboard, click the Api Keys tab and copy the key. In Make, add a uClassify module, click Create a connection, optionally name it, then paste the key or follow the on-screen instructions. The same connection then serves all three modules, so you only do this once. If the connection fails, check that the key was copied in full from the Api Keys tab.
03Does uClassify trigger a Make scenario in real time?
No. uClassify has no trigger module in Make, so it cannot start a scenario on its own. The flow begins with another app's trigger, for instance a new form entry or a new email, or with a schedule set on the first module, every 15 minutes by default on a new scenario. How fast your texts get classified therefore depends on that first module, scheduled or instant, and not on uClassify.
04What if a uClassify feature is missing from the Make modules?
It depends on the feature, but Make an API Call usually answers it. That module can call any endpoint of the uClassify API with the connection you already set up, so you are not limited to Classify Texts and Translate to English. Also note that the Make documentation page for uClassify is AI-generated and may contain mistakes, so verify important details with uClassify directly, and test every call with Run once before switching the scenario on.
05Should you use Make or n8n for uClassify?
It depends on the tool your team already runs. Make offers uClassify as a standard app with 3 action modules, including Make an API Call to reach the rest of the API, and a visual editor where you test with Run once. n8n may also offer a uClassify node; check its catalog before choosing. Compare how each tool fits your existing scenarios and how it counts usage, rather than picking on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations