Resources · Make integration

Bleez Make integrationAutomate Bleez with Make.

Tired of retyping customers and invoices into Bleez by hand? The Bleez Make integration gives you 7 action modules for customers, invoices and accounting. This guide connects your account and walks you through a first scenario, click by click.

Try the Bleez integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Bleez Make integration do for you?

The Bleez Make integration links your Bleez account to Make, a visual tool where you chain apps together without writing code. Each Bleez module is one brick of a scenario (the automation you build in Make): it creates a customer, issues an invoice, records an accounting entry or reads data back from Bleez.

Invoices that write themselves. When a deal is won or an order is paid in another app, Creating a Customer adds the buyer to Bleez and Create an Invoice bills them right after, so nobody copies names and amounts between tabs.

Bookkeeping fed from your other tools. An expense approved elsewhere can become a Bleez record through Create an Accounting Entry, and the matching receipt can follow with Submit an Accounting Document. Your accountant finds the entry and its proof in the same place.

Bleez data sent where your team works. Get Invoices and Get the Customer List pull records out of Bleez so a later module can push them into a spreadsheet, a dashboard or a chat message.

Know the limits before you start. Bleez has no trigger in Make, so it never starts a scenario by itself: the start comes from another app or from the schedule you set. Make also warns that its Bleez documentation was generated by AI from the vendor docs, so check important details with Bleez. For a wider view of the tool, read our Make review. If you are weighing another platform, the n8n vs Make comparison lays out the differences, and Make pricing explains how operations are counted.

Connect

How do you connect Bleez to Make?

  1. 01

    Add a Bleez module and open the connection

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

  2. 02

    Name the connection

    The Connection name field is optional, but a clear label helps when you run several Bleez files or a test account next to the live one. Pick something you will recognize in a dropdown.

  3. 03

    Paste your Bleez key

    In Bleez, open Administration > Dossier > Paramétrages and copy the key labeled Clé du dossier encryptée. Paste it into Make, or follow the on-screen instructions, and save the connection.

First scenario

Your first scenario with Bleez

GoalWhen a new order or signed deal lands in another app, Make adds the buyer to Bleez and creates their invoice.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since Bleez has no trigger, this first module comes from the app where your orders or deals live.

  2. 02

    Add Creating a Customer

    Click the + on the right of that first module, search for Bleez and pick Creating a Customer. Choose your connection, then map the buyer details that the previous module passes along.

  3. 03

    Chain Create an Invoice

    Add Create an Invoice after the customer module. Map the customer Bleez just created and the order data, so each bundle (one order moving through the chain) turns into one invoice.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time and read the bundles each module received. The test writes real records, so check the new customer and invoice in Bleez afterwards.

  5. 05

    Schedule it and switch it on

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

Modules

What each Bleez module does

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

Bleez1

Create an Accounting Entry

ActionIn the docs only

This module records an accounting entry in Bleez from data that started somewhere else, so your books stay current without a manual export and re-import.

When to use it
an expense gets approved or a payment is confirmed in another tool, and your accountant needs the matching line in Bleez.
Watch out
every run writes a real entry, so test with Run once on a sample before you switch the scenario on.
Bleez2

Create an Invoice

ActionIn the docs only

Here you get a new invoice issued in Bleez straight from the scenario, with the amounts and customer mapped from earlier modules instead of typed in by hand.

When to use it
a deal closes or an order is paid, and the invoice should exist before anyone opens Bleez.
Watch out
an invoice is a document your customer may receive, so run the scenario once on a test customer and read the result carefully.
Bleez3

Creating a Customer

ActionIn the docs only

Adding the buyer to your Bleez customer records is what this module handles, which gives later modules, such as the invoice, a customer to attach to.

When to use it
a new client signs up, fills a form or pays for the first time in another app.
Watch out
a scenario that runs for every order can add the same person twice, so check with Get the Customer List first when repeat buyers are common.
Bleez4

Get Invoices

ActionIn the docs only

Pulling your invoices out of Bleez into the scenario lets the next module copy them to a sheet, a report or a message for the team.

When to use it
finance wants invoice data outside Bleez, for a follow-up list or a shared dashboard.
Watch out
each module that processes a retrieved invoice spends one operation (one module run on one bundle, the unit Make counts on your plan), so keep an eye on volume.
Bleez5

Get the Customer List

ActionIn the docs only

With this module, your Bleez customers become data the rest of the scenario can read, compare or send on to another tool.

When to use it
you want to sync Bleez customers to a CRM or a mailing tool, or spot whether a buyer already exists before creating one.
Watch out
Make says its Bleez documentation is AI-generated, so confirm with Bleez what the list returns before relying on it.
Bleez6

Make an API Call

ActionIn the docs only

Your escape hatch: this module calls any endpoint of the Bleez API from the scenario, reusing the same connection, when the six ready-made modules do not cover the task.

When to use it
you need a Bleez operation that has no module of its own in Make.
Watch out
you pick the endpoint and build the request yourself, so keep the Bleez API documentation open while you set it up.
Bleez7

Submit an Accounting Document

ActionIn the docs only

What you gain is the supporting file sent into Bleez automatically, so a receipt or bill reaches your accounting without being downloaded and uploaded again.

When to use it
a supplier bill arrives in your inbox or a storage folder and belongs in Bleez next to its entry.
Watch out
on the Free plan, Make handles files up to 5 MB, so large scans may need a paid plan.
Need help

Need help automating Bleez with Make?

A person reads every message.

FAQ

Bleez and Make: common questions

01Is the Bleez Make integration free?
Yes, on the Make side. Bleez is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. You still need your own active Bleez account, which Bleez bills separately.
02What do you need to connect Bleez to Make?
An active Bleez account and its API key. In Bleez, go to Administration, then Dossier, then Paramétrages, and copy the key labeled Clé du dossier encryptée. In Make, add a Bleez module, click Create a connection, give it a name if you like, and paste the key. That connection is then reused by every Bleez module in your scenarios, so you only do this once per account. No active account or no key in that menu? Sort it out with Bleez before you start.
03Does the Bleez Make integration have a real-time trigger?
No. Bleez has no trigger module in Make, so it cannot start a scenario on its own. You start the scenario from another app, for example a form, a store or a CRM that sends new orders or deals, and add Bleez modules after it. You can also run the scenario on a schedule: the clock on the first module sets how often it runs, every 15 minutes by default for a new scenario, and never faster than that on the Free plan.
04What if a Bleez module you need is missing in Make?
Use Make an API Call. It is part of the Bleez app in Make and can reach any endpoint of the Bleez API with the connection you already set up, so it covers what the six other modules do not. You write the request yourself, so the Bleez API documentation becomes your reference. Make also flags that its Bleez documentation was generated by AI, so confirm important details with Bleez directly.
05Should you use Make or n8n for Bleez?
It depends on the tool your team already knows. On Make, Bleez offers 7 action modules, including a generic API call, and runs from the Free plan with no code. The same app often has an n8n node too, so check whether one exists before choosing. Neither tool is ranked here: compare how each one handles your customers, invoices and accounting steps, and pick the editor your team will actually maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations