Resources · Make integration

Tiflux Make integrationAutomate Tiflux with Make.

Can Make open a Tiflux ticket when something happens in another tool? Yes. The Tiflux Make integration gives you 8 action modules for clients and tickets. This guide is for support leads who build their own flows: connect the account, then build a first scenario step by step.

Try the Tiflux integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Tiflux Make integration do for your support team?

The Tiflux Make integration links your Tiflux help desk to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick that does a single job. Tiflux brings 8 of those bricks, all actions, so Tiflux does the work while another app or a schedule decides when.

Tickets that open themselves. A customer fills in a contact form on your site. Make passes the answers to Criar um Ticket, and the request lands in Tiflux without anyone copying it by hand.

New customers already on file. When a deal is signed in your CRM, Criar um Cliente adds the company to Tiflux, so the first support request finds a record waiting for it.

A clean export for reporting. Listar Tickets and Listar Clientes pull records out of Tiflux so another module can write them into a spreadsheet or a dashboard tool.

Know the limits before you start. Tiflux has no trigger in Make, so nothing fires when a ticket changes inside Tiflux; the start always comes from another app or from the schedule. Make also says its own documentation for Tiflux is incomplete, because little public information exists about the app, and the module names appear in Portuguese. If you are weighing platforms, the n8n vs Make comparison sets out the criteria, and the Make pricing guide explains what counts against your plan. For hands-on learning, see Make training.

Connect

How do you connect Tiflux to Make?

  1. 01

    Add a Tiflux module

    In your scenario, click the +, type Tiflux in the search box and pick any module, for example Listar Mesas. Make then asks for a connection, which is your Tiflux account linked to Make once and reused by every Tiflux module.

  2. 02

    Create the connection

    Click Create a connection. You can give it a name, which helps when you run a test account next to your live one. Then authorize Make on the Tiflux page that opens, or paste the key Tiflux gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module's dropdown. A quick way to confirm it works is to run a list module such as Listar Mesas once and look at what comes back.

First scenario

Build your first scenario with Tiflux

GoalWhen a new request comes in from another app, Make records the client in Tiflux and opens a ticket for it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Tiflux has no trigger, so the first module belongs to the app where requests arrive, such as your form tool.

  2. 02

    Add Criar um Cliente

    Click the + to the right of the first module and choose Criar um Cliente. Pick your Tiflux connection, then map the requester's details from the previous module into the fields Make shows you.

  3. 03

    Add Criar um Ticket

    Add Criar um Ticket after it. Map the request text from the first module, and link the ticket to the client created one step earlier using the data that module returned.

  4. 04

    Test with Run once

    Click Run once and send one real request through your form. Each module shows the bundles it received, a bundle being one item passed along, so you can check the new client and ticket in Tiflux.

  5. 05

    Schedule and switch on

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

Modules

What each Tiflux module does in Make

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

Tiflux1

Criar um Cliente

ActionIn the docs only

Adds a client record to Tiflux; the name is Portuguese for "create a client". You get the customer on file before any ticket needs it.

When to use it
right after a deal closes or a signup completes in another app, so support starts from a known account.
Watch out
an action like this creates a new record each time it runs, so feed it only events that really mean a new customer.
Tiflux2

Criar um Ticket

ActionIn the docs only

Opens a new ticket in Tiflux from data another module hands it, which saves your team from retyping requests that arrive by form, chat or email.

When to use it
whenever a request lives outside Tiflux and you want it in the support queue without manual copying.
Watch out
test it with Run once on a single real request first, since each run creates a ticket your agents will see.
Tiflux3

Exibir um Cliente

ActionIn the docs only

Fetches one client from Tiflux, going by its name, which is Portuguese for "show a client". The next modules can then use that client's details.

When to use it
when you already know which client you need and want its record to fill in an email, a CRM update or a report row.
Watch out
it works on a single client; to go through many, start with Listar Clientes instead.
Tiflux4

Exibir um Ticket

ActionIn the docs only

Retrieves a single ticket from Tiflux, going by its name, Portuguese for "show a ticket", so later modules can read what it contains.

When to use it
when another app gives you a ticket reference and you want the full ticket before notifying a manager or updating a spreadsheet.
Watch out
the documentation lists no fields for this module, so open it in the editor to see what it asks for before you plan the rest.
Tiflux5

Fazer uma Chamada API

ActionIn the docs only

Its name is Portuguese for "make an API call": a way to send a request to Tiflux that none of the other seven modules cover.

When to use it
only once you have checked that no ready-made Tiflux module does the job.
Watch out
Make's documentation gives no details on this module, so you need Tiflux's own API information to use it; if you are stuck, the team can help.
Tiflux6

Listar Clientes

ActionIn the docs only

Going by its name, it brings back your Tiflux clients as a series of bundles, one per client, which lets the following modules process each of them in turn.

When to use it
to copy your client base into a spreadsheet, or to compare it with the accounts held in your CRM.
Watch out
every client that flows through a later module costs one operation there, so a long list can use up a good part of your plan.
Tiflux7

Listar Mesas

ActionIn the docs only

Returns the desks set up in your Tiflux account, going by its name, Portuguese for "list desks". That shows how your support work is split.

When to use it
as a safe first test of a new connection, since its name says it only lists, or to check a desk before routing tickets.
Watch out
Make's documentation does not describe what a desk contains, so run it once and read the output before relying on it.
Tiflux8

Listar Tickets

ActionIn the docs only

Going by its name, it pulls your Tiflux tickets into Make as separate bundles, which is the starting point for any report or export built outside Tiflux.

When to use it
when a manager wants ticket data in a spreadsheet or dashboard tool instead of logging into Tiflux.
Watch out
Tiflux has no trigger, so this module will not react to new tickets on its own; it runs when the scenario's schedule or another app starts it.
Need help

Need help automating Tiflux with Make?

A person reads every message.

FAQ

Tiflux and Make: common questions

01Is the Tiflux Make integration free?
Yes. Tiflux is a standard app in Make, so its modules work on the Free plan as well as on paid plans. The Free plan has limits you will notice quickly: 2 active scenarios, at least 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 (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month.
02What do you need to connect Tiflux to Make?
A Tiflux account and a Make account. Make's documentation lists no prerequisite and no specific steps for Tiflux, so the generic process applies: add a Tiflux module, click Create a connection, optionally name it, then authorize Make on the Tiflux page or paste the key Tiflux provides, and click Save. The connection is created once and every Tiflux module in your scenarios reuses it. If you are unsure which credentials to use, ask the person who manages your Tiflux account.
03Does the Tiflux Make integration react in real time?
No, because Tiflux has no trigger module in Make, scheduled or instant. A change inside Tiflux cannot start a scenario by itself. You still have two ways to begin: put a trigger from another app first, such as a form or CRM that reports a new request, or let the scenario run on its schedule, which is every 15 minutes by default and at least 1 minute apart on paid plans. The Tiflux modules then act on the data that start gives them.
04What if a Tiflux module is missing in Make?
It depends on what you need. Tiflux does not have Make's universal Make an API Call module, but its own list includes Fazer uma Chamada API, whose name means make an API call; Make's documentation gives no details about it, so you would need Tiflux's API information. The documentation for this app is marked as limited overall. If neither the 8 modules nor that call fit, handle the step in another app, or ask the team for help designing the scenario.
05Should you use Make or n8n with Tiflux?
It depends on your criteria, not on a winner. On Make, Tiflux is available today with 8 action modules and no trigger, on every plan including Free. Many apps also have an n8n node, so check n8n's own catalog for Tiflux before deciding. Then compare what matters to your team: which modules each tool offers for Tiflux, how you want to start a flow, and how usage is counted. The comparison page linked above sets out those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations