Resources · Make integration

Tranzila Make integrationAutomate Tranzila with Make.

Can Make react to your Tranzila payments on its own? The Tranzila Make integration gives you 7 modules: 1 trigger that watches transactions and 6 actions for documents, payments and API calls. This guide shows you how to connect your account and build a first working scenario.

Try the Tranzila integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Tranzila Make integration do for you?

The Tranzila Make integration links your Tranzila account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Each module is one brick: a trigger that starts the flow, or an action that does something in Tranzila. You click the steps together, and Make runs them for you.

Paperwork that follows the payment. Put Watch Transactions at the start and Create a Document right after it, so a new transaction in Tranzila leads straight to a matching document without anyone copying numbers by hand.

Payments started from another tool. When a form, a CRM or a spreadsheet decides that someone should pay, Create a Payment Process or Create a Token Transaction lets that decision reach Tranzila directly.

Documents pulled into your other apps. Get a Document and Get Multiple Documents bring existing Tranzila documents into the scenario, ready to be passed to storage, email or accounting modules from other apps.

Know the limits before you start: Make itself says its Tranzila documentation is incomplete, because little public information exists about the app. Expect to discover the exact fields inside the editor. If something is not covered, Make an API Call reaches the rest of the Tranzila API. For a wider view of the tool, read our Make review, check Make pricing, or compare both platforms in n8n vs Make.

Connect

How do you connect Tranzila to Make?

  1. 01

    Add a Tranzila module

    In a scenario, click the + and search for Tranzila. Pick any of its modules, then click Create a connection. A connection is your Tranzila account linked to Make once, then reused by every Tranzila module.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps later. If you run a test account and a live account, a clear label saves you from sending a real payment request from a test scenario.

  3. 03

    Authorize and save

    Follow what the window asks: either approve Make on the Tranzila page that opens, or paste the key Tranzila gives you. Then click Save. The module can now read your account.

First scenario

Build your first scenario with Tranzila

GoalWhen a new transaction shows up in Tranzila, Make creates a matching document in Tranzila.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the canvas. This is where your first module will go.

  2. 02

    Add Watch Transactions

    Search for Tranzila, choose Watch Transactions and click Create a connection to link your account. Fill the fields Make shows you once the connection works.

  3. 03

    Add Create a Document

    Click the + on the right of the trigger and pick Create a Document. Map the transaction data coming from the first module into the document fields.

  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 check the document was built from the right transaction.

  5. 05

    Schedule and switch it on

    Open Scheduling on the first module. A new scenario checks every 15 minutes by default; the Free plan cannot go below that. Then turn the scenario on.

Triggers

What starts a Tranzila scenario?

1 module starts a scenario when something happens in Tranzila. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Tranzila as soon as it happens.

Tranzila1Watch Transactions

Watch Transactions

triggerIn the docs only

Watch Transactions hands your scenario each new Tranzila transaction as a bundle, meaning one item passed along to the next module. Everything you build after it can then react to real payment activity instead of a manual export.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default and never more often than that on the Free plan; paid plans go down to 1 minute.
When to use it
any flow that should begin because money moved, such as issuing a document or alerting your finance team.
Watch out
Make's documentation gives no description of this module, and its scheduled type is deduced from its name, so confirm what it returns with Run once.
Modules

What can each Tranzila module do?

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

Tranzila1

Create a Document

ActionIn the docs only

Create a Document produces a new document in your Tranzila account from data the scenario already holds, so the paperwork appears without anyone typing it.

When to use it
right after Watch Transactions, or after a form or CRM step that confirms a sale.
Watch out
Make publishes no description of its fields, so open the module and review each one before your first test.
Tranzila2

Create a Payment Process

ActionIn the docs only

This action opens a payment process in Tranzila straight from your scenario, which means a decision taken in another app can turn into a payment step without a manual handoff.

When to use it
a booking, an order or a signed quote in another tool should lead to a payment on the Tranzila side.
Watch out
test it on a non-production account first, since the documentation does not explain what the process involves.
Tranzila3

Create a Token Transaction

ActionIn the docs only

Going by its name, this module records a Tranzila transaction based on a token rather than on fresh payment details, which suits customers whose payment data is already stored.

When to use it
pick it over Create a Payment Process when the customer is already known and the flow should not ask them again.
Watch out
a run may move real money, so keep Run once tests on a test connection.
Tranzila4

Get Multiple Documents

ActionIn the docs only

Get Multiple Documents pulls several Tranzila documents into the scenario in a single step, giving the next modules a batch to file, forward or copy into a spreadsheet.

When to use it
you need a set of documents rather than one known record, for example to sync them with a storage app.
Watch out
Make lists it as an action with no details, so run it once and count the bundles it returns before chaining more modules.
Tranzila5

Get a Document

ActionIn the docs only

Get a Document fetches one specific Tranzila document so its contents can travel to the rest of your scenario, such as an email or a shared folder.

When to use it
an earlier module already points to a single document, for instance the one Create a Document just produced.
Watch out
if you need several at once, Get Multiple Documents fetches them in one step instead of repeating this one. Each module run counts as an operation, the unit Make counts on your plan.
Tranzila6

Make an API Call

ActionIn the docs only

Make an API Call lets your scenario reach any endpoint of the Tranzila API with the same connection, covering whatever the six other modules leave out.

When to use it
the action you need has no dedicated module, which is likely given how thin the official documentation is.
Watch out
you write the request yourself, so you will need Tranzila's own API documentation; see Make troubleshooting if a call fails.
Need help

Need help automating Tranzila with Make?

A person reads every message.

FAQ

Tranzila and Make: common questions

01Is the Tranzila Make integration free?
Yes, Tranzila is a standard app in Make, so it works on the Free plan. That plan has real limits though: 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 such as Core, Pro, Teams and Enterprise lift those limits, allow a 1 minute interval and count usage in credits each month. Your Tranzila subscription is a separate matter that this page does not cover.
02What do you need to connect Tranzila to Make?
A Tranzila account and a Make account. Make's documentation lists no specific prerequisite and no official connection steps for Tranzila, so the generic path applies: add a Tranzila module, click Create a connection, name it if you like, then approve Make on the Tranzila page or paste the key Tranzila provides, and click Save. The same connection then serves every Tranzila module in your scenarios. If the authorization fails, review your Tranzila account settings first, then create the connection again.
03Does the Tranzila trigger in Make fire in real time?
No. Watch Transactions is a scheduled trigger, based on its name, since the documentation does not describe it. Make checks Tranzila on the schedule you set on the first module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans let you go down to 1 minute. There is no instant trigger for Tranzila, so a transaction is picked up at the next scheduled check.
04What if a Tranzila module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Tranzila API through the connection you already created, so you are not limited to the six listed actions and the trigger. Make itself warns that its Tranzila documentation is limited because little public information exists, so you will rely on Tranzila's own API reference to build the request and read the answer. Test each custom request with Run once before switching the scenario on.
05Make or n8n for Tranzila?
It depends on where the rest of your automations already live. In Make, Tranzila comes with 7 ready modules and runs on the Free plan, which makes it easy to test a first scenario. Many apps also have an n8n node, so check whether one exists for Tranzila before choosing. Neither tool is ranked above the other here: pick the one your team already knows and that covers the other apps in your flow.
Same platform

Other docs you might need on this stack.

Browse all integrations