Resources · Make integration

Levity Make integrationAutomate Levity with Make.

Need incoming text sorted, summarized or answered without copy and paste? The Levity Make integration gives you 5 action modules that work on text. This guide is for teams who know Levity but are new to Make, and it walks you from the connection to a first live scenario.

Try the Levity integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Levity Make integration do for you?

The Levity Make integration lets a Make scenario, the automation you build as a chain of modules, hand a piece of text to Levity and get something useful back: a category, extracted values, a summary or a freshly generated text. Each module is one brick of that chain, and Levity brings 5 of them, all actions.

A support inbox that sorts itself. Feed each new ticket from your helpdesk into Classify a Text, then route billing questions to one team and bug reports to another with a filter on the result. The ticket text stays where it is; only the label travels on.

Order details pulled out of free-form emails. Extract a Text reads a message and returns the values you care about, so a sales assistant no longer retypes a reference or a delivery address into the CRM.

Short digests for busy managers. Summarize a Text condenses a long meeting transcript or a customer thread, and Generate a Text can draft the follow-up that goes with it.

Levity has no trigger in Make, so your scenario always starts elsewhere: on another app, or on the scenario's schedule. The Make documentation for Levity is also flagged as limited, so the guide below leans on testing with Run once rather than on field lists. For anything the 5 modules leave out, Make an API Call reaches the rest of the Levity API with the same connection.

Still choosing a platform? Read the n8n vs Make comparison and our Make review. When a run fails, the Make troubleshooting guide lists the usual causes.

Connect

How do you connect your Levity account to Make?

  1. 01

    Open the connection window

    Add any Levity module to your scenario and click Create a connection. A connection is your Levity account linked to Make once, then reused by every Levity module you add later.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, such as the workspace it belongs to. Then either approve Make on the Levity page that opens, or paste the key Levity gives you, depending on what the window asks for.

  3. 03

    Save and check the module

    Click Save. The connection now appears in the module, and any other Levity module in any scenario can pick it from the same list without asking again.

First scenario

Build your first scenario with Levity

GoalWhen a new message lands in another app, Levity labels it with Classify a Text, then Generate a Text drafts a reply for it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Since Levity has no trigger, pick the app where your messages arrive, such as your helpdesk or inbox.

  2. 02

    Add Classify a Text

    Click the + on the right of that first module, search for Levity and choose Classify a Text. Select your connection, then map the message body from the previous module into the text it should read.

  3. 03

    Chain Generate a Text

    Add one more Levity module with the + and pick Generate a Text. Map in both the original message and the label returned by the classifier, so the draft matches the kind of request.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles, the items each module received and passed on. Open them to check the label and the generated draft.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set Scheduling; a new scenario checks every 15 minutes by default. Then flip the scenario on and it keeps running without you.

Modules

What each Levity module does

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

Levity1

Classify a Text

Action

In Make“Performs text classification.”

Sort any incoming text into a category, so the rest of your scenario knows which path it should take. Each run returns a label you can filter on.

When to use it
a mixed inbox of tickets, reviews or leads that needs routing to the right person before anyone reads it.
Watch out
run it on a handful of real messages with Run once and check the labels before adding filters that depend on them.
Levity2

Extract a Text

Action

In Make“Extracts values from text.”

Get the specific values buried inside a message, instead of the whole paragraph, and pass them to the next module as clean data. That is the step that replaces manual retyping.

When to use it
an order or a booking request arrives as free text and the details must land in a spreadsheet or a CRM.
Watch out
Make does not document what comes out of this module, so read the bundle after a test before mapping anything.
Levity3

Generate a Text

Action

In Make“Generates a text for a specific use-case.”

Obtain a new piece of writing for one precise use, built from the data your scenario already holds. It is the module that turns a label or a summary into something a person can send.

When to use it
a reply draft, a product blurb or an internal note has to follow each classified request.
Watch out
keep a human review step before anything generated goes out to customers.
Levity4

Make an API Call

Action

In Make“Performs an authorized API call.”

Reach any part of the Levity API that the four text modules do not cover, using the connection you already set up. You write the request yourself and get the raw answer back.

When to use it
you need a Levity feature that has no dedicated module in Make.
Watch out
you describe the request yourself and Make documents little about Levity, so test each call with Run once before building on it.
Levity5

Summarize a Text

Action

In Make“Creates a summary of your data.”

Turn a long block of text into a short version that someone can read at a glance. The summary then flows on like any other bundle, ready to post or store.

When to use it
a call transcript, a long email thread or a report must reach a manager who will not open the original.
Watch out
map only the text itself, not headers or signatures, or they may end up in the summary.
Need help

Need help automating Levity with Make?

A person reads every message.

FAQ

Levity and Make: common questions

01Is the Levity Make integration free?
Yes, Levity is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops an execution after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one run of one module on one bundle.
02What do you need to connect Levity to Make?
You need a Levity account and a Make account. The Make documentation lists no other prerequisite for Levity. In the scenario editor, add a Levity module, click Create a connection, optionally name it, then either approve Make on the Levity page or paste the key Levity provides, and click Save. The same connection then serves all 5 Levity modules, including Make an API Call. Because the documentation is limited, run a test right away to confirm the connection works.
03Can a Levity scenario in Make start in real time?
Not from Levity itself, since the app has no trigger module in Make. The scenario has to start somewhere else. You can open it with a trigger from another app, for instance the tool where your messages arrive; if that app offers an instant trigger, it calls Make through a webhook as soon as something happens. Otherwise the scenario runs on its schedule, every 15 minutes by default, and each Levity module then processes the text it receives.
04What if the Levity module you need is missing in Make?
Use Make an API Call. It sends an authorized request to any endpoint of the Levity API, reusing your existing connection, so the four text modules are not the ceiling. Keep in mind that Make describes its Levity documentation as limited, since there is little public information about the app. Before you depend on a custom call, test the result with Run once to see exactly what comes back in the bundle.
05Should you use Make or n8n with Levity?
It depends on the platform your team already runs. In Make, Levity comes with 5 ready modules for classifying, extracting, generating and summarizing text, plus Make an API Call for the rest, and a first scenario needs no code. Many apps also have an n8n node, so check whether Levity does before comparing. If your other automations already live in one tool, keeping Levity there is usually simpler to maintain. The comparison page linked above lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations