Resources · Make integration

Tisane Make integrationAutomate Tisane with Make.

Got text coming in from forms, emails or tickets and want Tisane to read it for you? The Tisane Make integration offers 3 action modules and no trigger. This guide shows what each one is for, how to link your account and how to build your first flow.

Try the Tisane integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Tisane Make integration do for you?

The Tisane Make integration lets a Make scenario, the automation you build in Make as a chain of bricks called modules, send text to Tisane and get the answer back. It has three actions: detect a language, analyze a text, and call any endpoint of the Tisane API with the same account.

Route messages by language. A support inbox receives requests in several languages. Put Detect Language right after the step that brings the message in, then send each language to the right team or sheet. The language comes back as data you can map into the next module.

Review what customers write before it lands anywhere. A shop collecting reviews through a form can pass each review to Analyze Text and keep the result next to the original text, so the person who reads it later has Tisane's reading in front of them.

Reach the rest of the API. When neither module covers the call you need, Make an API Call hits any Tisane endpoint through the connection you already set up.

Know the limit before you start: Make itself says its documentation for Tisane is incomplete, because too little public information exists about the app. Expect to test each module with a real text before trusting the output. If you get stuck on errors, the Make troubleshooting guide helps, and Make pricing explains how runs are counted. Weighing another tool? Read n8n vs Make.

Connect

How do you connect Tisane to Make?

  1. 01

    Add a Tisane module

    In your scenario, add any Tisane module, for example Detect Language. In the module panel, click Create a connection. A connection is your Tisane account linked to Make once, then reused by every Tisane module you add later.

  2. 02

    Name it so you can find it

    Make offers a name field for the connection. It is optional, but a clear label such as the project or the team helps when several people share the same Make organization and pick from a list of connections.

  3. 03

    Authorize and save

    Depending on what Make asks, either approve access on Tisane's page or paste the key Tisane gives you into the field shown. Then click Save. The module now shows your connection and you can fill its fields.

First scenario

Your first scenario with Tisane

GoalWhen a new text shows up in another app, Make asks Tisane for its language and then analyzes it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module. Tisane has no trigger, so this first module comes from the app where your texts live.

  2. 02

    Start from your source app

    Search that app by name and pick the module that returns your texts, such as new form answers or new messages. Link its account the same way you will link Tisane.

  3. 03

    Add Detect Language

    Click the + on the right of the first module, search Tisane and pick Detect Language. Create your connection, then map the text coming from the first module into the Tisane field.

  4. 04

    Chain Analyze Text

    Add Analyze Text after it with the same connection. Map the same text again. Make lists the module's fields once the connection exists, so you see what it expects without guessing.

  5. 05

    Test with Run once

    Click Run once. Make executes the scenario one time, and a bubble on each module shows the bundles it received, a bundle being one item passed from one module to the next.

  6. 06

    Schedule and switch on

    On the first module, open the clock to set the schedule. A new scenario checks every 15 minutes by default. Then flip the switch so the scenario runs on its own.

Modules

What each Tisane module does

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

Tisane1

Analyze Text

ActionIn the docs only

This action hands a piece of text to Tisane for analysis and passes the answer to whatever module comes next, so a review or a message arrives downstream with Tisane's reading attached.

When to use it
a form, an inbox or a ticket tool sends you free text and a person or a sheet needs Tisane's view of it before acting.
Watch out
Make publishes no field list for this module, so run it once on a real sample and check the bundle before mapping anything.
Tisane2

Detect Language

ActionIn the docs only

Find out which language a text is written in, then use that answer to steer the rest of the scenario, for example toward the right team, template or translation step.

When to use it
messages reach you in several languages and each one should go down a different path.
Watch out
each call is an operation, one module run on one bundle, and that is what your Make plan counts.
Tisane3

Make an API Call

ActionIn the docs only

Reach any endpoint of the Tisane API from inside your scenario, reusing the connection you already created, when the two ready-made modules stop short of what you need.

When to use it
Tisane's own API reference describes a call that neither Analyze Text nor Detect Language exposes.
Watch out
you write the request yourself here, so keep Tisane's API documentation open and test the call with Run once first.
Need help

Need help automating Tisane with Make?

A person reads every message.

FAQ

Questions people ask about Tisane and Make

01Is the Tisane Make integration free?
Yes, on the Make side. Tisane is a standard app, so its modules work from the Free plan onward. The Free plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Every module run counts as an operation on your plan. Whatever Tisane itself charges is a separate matter to check with Tisane.
02What do you need to connect Tisane to Make?
A Tisane account and a Make account. Make's documentation lists no other prerequisite for this app. The link goes through the generic Make flow: add a Tisane module, click Create a connection, optionally name it, then either approve access on Tisane's page or paste the key Tisane gives you, and click Save. The connection is created once and every Tisane module in your scenarios reuses it. Because the official documentation for Tisane is limited, keep your Tisane account settings open while you do it.
03Can Tisane start a Make scenario in real time?
No. The Tisane Make integration has no trigger at all, neither scheduled nor instant, so Tisane cannot start a scenario by itself. The scenario has to begin somewhere else: with a trigger from the app that holds your texts, such as a form or an inbox, or with the schedule on the first module, set to every 15 minutes by default on a new scenario, which is also the shortest interval the Free plan allows. Tisane's modules then run as actions later in the flow.
04What if the Tisane module you need is missing in Make?
Use Make an API Call. It is part of the Tisane app in Make and can reach any endpoint of the Tisane API with the connection you already set up, so it covers what Analyze Text and Detect Language leave out. You build the request yourself, which means reading Tisane's API reference. Keep in mind that Make says it cannot provide complete documentation for Tisane because there is not enough public information about the app, so expect some trial with Run once before the call returns what you want.
05Make or n8n for Tisane?
It depends on the tool your team already uses. In Make, Tisane comes with 3 action modules: Detect Language, Analyze Text and Make an API Call, which opens the rest of the API. Many apps also have an n8n node, so check whether one exists for Tisane before choosing, and compare what each side exposes for your use case. Neither answer is better in general. If your other automations already live in Make, adding Tisane there keeps everything in one editor with one set of connections.
Same platform

Other docs you might need on this stack.

Browse all integrations