Resources · Make integration

TextCortex AI Make integrationAutomate TextCortex AI with Make.

What if every long text in your tools came back shorter, clearer or in another language on its own? The TextCortex AI Make integration gives you 6 modules to write, rewrite and translate without code. This guide connects your account and builds a first scenario with you.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the TextCortex AI Make integration do?

The TextCortex AI Make integration lets a Make scenario (the automation you build, a chain of steps) hand text to TextCortex AI and get the result back: a summary, a paraphrase, a simpler version, a translation or a completion from your own prompt. You can also upload files to your TextCortex knowledge base.

Support replies that land in the customer's language. When a ticket arrives in your help desk, Translate Text turns your answer into the right language before it goes back out. The agent writes once, Make handles the rest.

Meeting notes nobody has to condense. A long transcript saved in a shared folder goes through Summarize Text, and the short version lands in the team channel. Chain Simplify Text after it if the readers are outside the project.

Product copy that does not repeat itself. For an online shop listing near-identical items, Paraphrase Text rewrites each description so the pages read differently. Create Completion covers anything the ready-made modules miss, from a tagline to a reply draft.

What the integration does not do: it has no trigger, so TextCortex AI never starts a scenario by itself, and there is no generic API call module to reach features outside these 6. Another app, or Make's own schedule, has to kick things off.

New to Make? The Make training starts from zero, and the n8n vs Make comparison helps if you are still choosing a tool. For plan details, see Make pricing.

Connect

How do you connect TextCortex AI to Make?

  1. 01

    Copy your API key from TextCortex AI

    Sign in to TextCortex AI and open the dashboard. Click Settings, then API key, and copy the key shown on screen. Keep it handy: Make asks for it in the next step, and it is the only thing that links the two tools.

  2. 02

    Add a TextCortex AI module in Make

    In your Make scenario, add any TextCortex AI module and click Create a connection. A connection is your TextCortex account linked to Make once, then reused by every TextCortex module. The Connection name field is optional but helps when you have several.

  3. 03

    Paste the key and confirm

    Paste the API key you copied, or follow the on-screen instructions if Make shows them. Once the connection is created, the module fields open up and you can start filling them in. Every other TextCortex module in your account will offer this connection.

First scenario

Your first scenario with TextCortex AI

GoalWhen a new long text appears in another app, Make summarizes it with TextCortex AI and translates the summary.

  1. 01

    Create the scenario and pick a starting point

    Open the Scenarios page, create a new scenario and click the +. Since TextCortex AI has no trigger, the first module comes from the app where your text lives, such as a form, a note tool or a spreadsheet.

  2. 02

    Add Summarize Text

    Click the + to the right of the first module, search for TextCortex AI and choose Summarize Text. Create the connection with your API key if it is your first TextCortex module.

  3. 03

    Map the text and add Translate Text

    In Summarize Text, map the text field from the first module's output. Then click + again, pick Translate Text, map the summary into it and choose the target language.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can read the summary and its translation before anything goes live.

  5. 05

    Schedule and switch it on

    On the first module, open the clock to set the schedule; a new scenario checks every 15 minutes by default. Switch the scenario on and it keeps summarizing new texts as they show up.

Modules

What can TextCortex AI do in Make?

TextCortex AI gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

TextCortex AI1

Upload a File

Action

In MakeUploads file to your knowledge base.

Sends a file from your scenario into your TextCortex knowledge base, so the content is there when you or your team work in TextCortex AI later. It is the only action of the app; the other five return generated text.

When to use it
a signed brief or product sheet lands in cloud storage and should feed the knowledge base without a manual upload.
Watch out
on the Make Free plan, files go up to 5 MB, so check the size of what you send.
TextCortex AI2

Create Completion

Search

In MakeSends a prompt to the TextCortex API and creates a completion.

Gives you free rein: you write the prompt, TextCortex AI writes the answer, and the result flows to the next module. Think reply drafts, taglines or a short intro built from data mapped in earlier steps.

When to use it
none of the ready-made modules fits the task, and you would rather describe the output in your own words.
Watch out
Make classes it as a search, so it can hand over several bundles; each one then runs the next module and counts as an operation.
TextCortex AI3

Paraphrase Text

Search

In MakeParaphrases the given text.

Returns the same message in different words, which helps when many texts start from one template and should not read like copies of each other. The meaning stays, the wording changes.

When to use it
product descriptions for similar items, or outreach messages you want to vary before sending them from your email tool.
Watch out
if the goal is easier reading rather than new wording, Simplify Text is the better pick; paraphrasing keeps the original level of complexity.
TextCortex AI4

Simplify Text

Search

In MakeSimplifies the given text.

Turns dense text into plainer language, so a reader outside the field gets the point without rereading. Useful for technical notes, legal wording or internal jargon heading to customers.

When to use it
a release note written by engineers should go out to clients, or a policy update needs a version the whole company can read.
Watch out
simplifying does not shorten on purpose. If the text is long and you mainly want it shorter, place Summarize Text before or instead of this module.
TextCortex AI5

Summarize Text

Search

In MakeSummarizes the given text.

Condenses a long text into its key points, so people read the essentials instead of the whole thing. It fits transcripts, long emails, reports and customer feedback threads.

When to use it
a meeting transcript is saved, and the team channel should receive a short version without anyone writing it.
Watch out
summarizing then translating means two TextCortex modules, so each text costs two operations. Summarize only the texts that need it.
TextCortex AI6

Translate Text

Search

In MakeTranslates a text into specified language.

Puts a text into the language you specify, so content written once can reach readers in other markets. Chain it after another TextCortex module to translate a summary or a rewritten version.

When to use it
a support answer written in English must reach a customer in their own language, or a product page needs its Spanish copy.
Watch out
the official doc for this app is AI-generated and may contain mistakes, so check a few translations with Run once before switching the scenario on.
Need help

Need help automating TextCortex AI with Make?

A person reads every message.

FAQ

TextCortex AI and Make: common questions

01Is the TextCortex AI Make integration free?
Yes, on the Make side. TextCortex AI is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Make counts each module run as an operation. Your TextCortex AI subscription is separate: you still need an active account and an API key on their side.
02What do you need to connect TextCortex AI to Make?
You need an active TextCortex AI account and its API key. In TextCortex, open the dashboard, click Settings, then API key, and copy the key. In Make, add any TextCortex AI module, click Create a connection, give it a name if you like, and paste the key. The connection is then reused by all 6 TextCortex modules in your scenarios. If the key is missing from your account, look at your TextCortex subscription through their pricing page before trying again in Make.
03Can a TextCortex AI module start a scenario in real time?
No. TextCortex AI has no trigger in Make, so it never starts a scenario on its own. You have two ways to begin. The first is a trigger from another app, such as a new form entry or a new file, followed by the TextCortex module that processes the text. The second is a schedule set on the first module; a new scenario runs every 15 minutes by default, and a paid plan can go down to 1 minute. Either way, TextCortex AI works as a step in the middle of the flow.
04What if a TextCortex AI module is missing in Make?
It depends on the feature. The app offers 6 modules: Upload a File, Create Completion, Paraphrase Text, Simplify Text, Summarize Text and Translate Text. There is no Make an API Call module for TextCortex AI, so features outside that list cannot be reached from this app. Create Completion often fills the gap, since you write the prompt yourself. Otherwise, another app may cover the need, or the team can help you design the scenario. Note that the official doc is AI-generated and may contain mistakes; check with TextCortex AI if something looks off.
05Should you use Make or n8n with TextCortex AI?
It depends on what your team already runs. If your automations live in Make, the 6 TextCortex AI modules connect with an API key and a first scenario needs no code, which is what this page walks through. If your team works in n8n, check there whether a node for the app exists before switching tools. The deciding factors are the tool you already maintain, the other apps in the flow, and who will look after the scenarios. The n8n vs Make comparison linked above covers these criteria in detail.