Resources · Make integration

Fatture in Cloud Make integrationAutomate Fatture in Cloud with Make.

Your invoices, clients and receipts can move on their own. The Fatture in Cloud Make integration gives you 62 modules, 2 of them triggers. This guide is for the person who runs the books and wants to link one account, build a first flow and test it safely.

Try the Fatture in Cloud integration on MakeSee the 62 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Fatture in Cloud Make integration do for you?

The Fatture in Cloud Make integration links your invoicing account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Fatture in Cloud brings 62 of those bricks, covering clients, suppliers, products, documents, receipts, the cashbook and F24s.

E-invoices that leave without a manual export. Watch New Issued Documents spots each new document, Verify E-Invoice XML checks the file, and Send E-Invoice passes it to SDI. If the check fails later, Get an E-Invoice Rejection Reason tells you why.

A client list that stays in sync with your CRM. Watch New Clients picks up every new client, and the next module can copy it into a table. The Airtable Make integration guide covers the other half of that flow. Going the other way, Create a Client or Update a Client keeps Fatture in Cloud current when the data starts elsewhere.

Receipts and purchases recorded from other tools. Create a Receipt, Create a Received Document and Create a Cashbook Entry let a sale or a supplier bill land in your books from a form, an inbox or a shop.

Know the limits before you start. Both triggers are scheduled: Make checks the account on the scenario's clock, so nothing fires the second a client is added. Some features also require a paid Fatture in Cloud plan. When a listed module falls short, Make an API call reaches the rest of the API. Weighing tools first? The n8n vs Make comparison sets the criteria side by side, and the Make pricing page explains what an operation costs you.

Connect

How do you connect Fatture in Cloud to Make?

  1. 01

    Add a Fatture in Cloud module

    In your scenario, search for Fatture in Cloud, pick any of its modules and click Create a connection. A connection is your Fatture in Cloud account linked to Make once, then reused by every module of the app.

  2. 02

    Give the connection a clear name

    The Connection name field is optional, yet worth filling. Name it after the company or the person who owns the account, so you pick the right one later when several people share the same Make team.

  3. 03

    Enter credentials or follow the prompts

    Paste the credentials you copied from Fatture in Cloud, or follow the on-screen instructions to authorize access. You need an active Fatture in Cloud account and an API token first; some features require a paid Fatture in Cloud plan.

First scenario

Your first scenario: send each new invoice to SDI

GoalWhen a new document is issued in Fatture in Cloud, Make checks its XML and sends the e-invoice to SDI.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas. Search for Fatture in Cloud and choose Watch New Issued Documents.

  2. 02

    Link your account

    Click Create a connection and finish the three steps above. Once linked, Make can read your company data and shows the choices it finds in the module fields.

  3. 03

    Add the XML check

    Click the + on the right of the trigger and add Verify E-Invoice XML. Map the document from the trigger, so each bundle (one document passing from module to module) gets checked.

  4. 04

    Add the sending step

    Add Send E-Invoice after the check and map the same document again. During the test, read what the check returned before you let the sending run on its own.

  5. 05

    Test with Run once

    Issue a test document in Fatture in Cloud, then click Run once. Open the bubble above each module to read the bundle it received and confirm the right document went through.

  6. 06

    Schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default; keep that or pick another interval, then switch the scenario on.

Triggers

What starts a Fatture in Cloud scenario?

2 modules start a scenario when something happens in Fatture in Cloud. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Fatture in Cloud as soon as it happens.

Fatture in Cloud1Watch New Clients

Watch New Clients

Scheduled trigger

In Make“Triggers when a new client is created.”

Every client added to Fatture in Cloud becomes the start of a run, so the rest of your tools learn about the new customer without anyone retyping the details. Each client arrives as one bundle you can map into the next module.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and the Free plan does not go below that.
When to use it
your sales team creates clients in Fatture in Cloud and your CRM or mailing list has to follow.
Watch out
the module is described around new clients, so build a separate check if edits to existing clients matter to you.
Fatture in Cloud2Watch New Issued Documents

Watch New Issued Documents

Scheduled trigger

In Make“Triggers when a new issued document is created.”

This trigger hands you each document your company issues, ready to be verified, sent, archived or announced to a colleague. It is the natural starting point for anything that should happen after an invoice exists.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a document shows up at the next check rather than the instant it is saved.
When to use it
you want every new invoice pushed to SDI or copied to a shared drive without opening Fatture in Cloud.
Watch out
the module is described around new documents; if changes to existing ones matter, plan a List All Issued Documents step instead.
Modules

What can Fatture in Cloud do in a scenario?

Fatture in Cloud gives you 60 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Fatture in Cloud1

Create a Cashbook Entry

Action

In Make“Creates a new cashbook entry.”

Records money in or out of your cashbook straight from the scenario, so a payment captured by another tool shows up in Fatture in Cloud without a second entry by hand.

When to use it
a payment platform confirms a transfer and you want the movement booked the moment the scenario sees it.
Watch out
map the amount from the previous module rather than typing it, or every run books the same figure.
Fatture in Cloud2

Create a Client

Action

In Make“Creates a client for the company.”

Adds a new client to your company in Fatture in Cloud using data that arrives from elsewhere, like a signed quote or a web form. You skip the copy and paste before the first invoice.

When to use it
a deal closes in your CRM and accounting needs the customer ready before billing starts.
Watch out
run a List All Clients search first if the same person could already exist, to avoid duplicates.
Fatture in Cloud3

Create an F24

Action

In Make“Creates a new F24.”

Adds a new F24 to Fatture in Cloud from the scenario, so the record is waiting in the account when you open it, instead of being retyped from an email or a spreadsheet row.

When to use it
your accountant sends F24 details in a structured sheet and you want each row turned into a record.
Watch out
read the result of a test run before switching on, because an F24 created with wrong values has to be fixed by hand.
Fatture in Cloud4

Create an Issued Document

Action

In Make“Creates a new document.”

Builds a new document in Fatture in Cloud, such as an invoice, from data your scenario already holds. Orders from a shop or hours from a timesheet can become a document without anyone opening the app.

When to use it
an online order is paid and the matching invoice should exist in Fatture in Cloud right after.
Watch out
add Get Issued Document Pre-Create Info before it when you are unsure which options the account accepts.
Fatture in Cloud5

Create a Product

Action

In Make“Creates a new product.”

Adds an item to your product list in Fatture in Cloud, so documents created later can reuse it instead of a free-text line typed each time.

When to use it
you launch a new item in your shop and want the catalog in Fatture in Cloud to match.
Watch out
a scenario that runs again on the same item creates it again, so search with List All Products before creating.
Fatture in Cloud6

Create a Receipt

Action

In Make“Creates a new receipt.”

Writes a new receipt into Fatture in Cloud from a sale recorded by another system, which keeps your takings in one place even when the till lives somewhere else.

When to use it
a counter sale is logged in your point-of-sale tool and the receipt needs to appear in your books.
Watch out
Get Receipt Pre-Create Info shows what the account expects before your first real run.
Fatture in Cloud7

Create a Received Document

Action

In Make“Creates a new received document.”

Logs a document you received, such as a supplier bill, in Fatture in Cloud. The expense is recorded as soon as the scenario handles it rather than when someone finds time for data entry.

When to use it
supplier invoices land in a shared inbox and you want each one registered without retyping.
Watch out
when a bill comes from someone new, place Create a Supplier earlier in the flow so the vendor gets its own record.
Fatture in Cloud8

Create a Supplier

Action

In Make“Creates a supplier for the company.”

Adds a supplier to your company in Fatture in Cloud, so received documents and payments can point to a real record from the start.

When to use it
a purchase request is approved and the vendor is not in your books yet.
Watch out
search with List All Suppliers first; a second record for the same vendor splits its history in two.
Fatture in Cloud9

Delete a Cashbook Entry

Action

In Make“Deletes a specific cashbook entry.”

Removes one cashbook entry from Fatture in Cloud. It is the clean-up step when a payment recorded by the scenario turns out to be cancelled or refunded in the source tool.

When to use it
a refund in your payment platform means the original entry should disappear from the cashbook.
Watch out
a delete cannot be undone from Make, so test with a dummy entry and Run once before going live.
Fatture in Cloud10

Delete a Client

Action

In Make“Deletes a specific client.”

Erases one client record from your Fatture in Cloud company. It keeps the list tidy when a contact was created by mistake or merged into another record in your CRM.

When to use it
your CRM flags a test contact or a duplicate that should not stay in accounting.
Watch out
nothing brings the record back afterwards, so add a filter that lets only the intended client through.
Fatture in Cloud11

Delete an Archived Document

Action

In Make“Deletes a specific archived document.”

Takes one document out of the Fatture in Cloud archive. It suits the end of a flow that uploaded files automatically and now needs to drop a wrong or duplicated upload.

When to use it
a file was uploaded to the archive twice and you only want the newest copy kept.
Watch out
the removal is permanent; confirm the document with Get an Archive Document before this step.
Fatture in Cloud12

Delete an F24

Action

In Make“Deletes a specific F24.”

Removes a specific F24 from Fatture in Cloud, useful when a scenario created it from bad data and you would rather start over than edit every value.

When to use it
an import of F24 rows went wrong and the faulty records should go before you retry.
Watch out
Update an F24 is the gentler option when only one value is off; deleting cannot be reversed.
Fatture in Cloud13

Delete an F24 Attachment

Action

In Make“Removes the attachment of the specified F24.”

Detaches the file linked to one F24 while leaving the F24 itself in place. You keep the record and simply clear the document that sits on it.

When to use it
the wrong receipt was attached to an F24 and you plan to attach the right one next.
Watch out
this only touches the attachment; to drop the whole record, use Delete an F24 instead.
Fatture in Cloud14

Delete an Issued Document

Action

In Make“Deletes a specific issued document.”

Deletes one issued document from Fatture in Cloud. It closes a loop when an order is cancelled before the document should have existed in the first place.

When to use it
a shop order is cancelled and the draft invoice your scenario created no longer makes sense.
Watch out
a delete cannot be undone from Make, so read the document with Get an Issued Document before removing it.
Fatture in Cloud15

Delete an Issued Document Attachment

Action

In Make“Removes the attachment of the specified document.”

Clears the file attached to a given issued document, while the document stays as it is. Handy when an automation attached the wrong PDF or an outdated contract.

When to use it
a corrected attachment is ready and the old one has to go before the new upload.
Watch out
the attachment is removed for good; keep the file elsewhere if you may need it later.
Fatture in Cloud16

Delete a Product

Action

In Make“Deletes a specific product.”

Removes an item from your Fatture in Cloud product list, keeping the catalog aligned with what you actually sell.

When to use it
a product is retired in your shop and should no longer be offered when documents are created.
Watch out
check with Get a Product that you target the right item, because a delete from Make cannot be rolled back.
Fatture in Cloud17

Delete a Receipt

Action

In Make“Deletes a specific receipt.”

Deletes one receipt from Fatture in Cloud. It is the reverse move to Create a Receipt when a sale recorded upstream is voided.

When to use it
your point-of-sale tool cancels a ticket and the matching receipt should leave your books too.
Watch out
make sure the scenario passes the exact receipt to remove; a wrong mapping deletes a valid one.
Fatture in Cloud18

Delete a Received Document

Action

In Make“Deletes a specific received document.”

Removes a received document, like a supplier bill, from Fatture in Cloud. It helps when a bill registered by the scenario turns out to be a duplicate or was sent by mistake.

When to use it
your supplier resends the same invoice and the first copy should not stay on file.
Watch out
use a filter so only documents you have confirmed as duplicates reach this module.
Fatture in Cloud19

Delete a Received Document Attachment

Action

In Make“Deletes the attachment of a specific received document.”

Removes the file attached to a specific received document but keeps the document record. The expense stays booked; only the scan or PDF goes.

When to use it
a blurry scan was attached to a supplier bill and a clean copy is on its way.
Watch out
the file is gone once the module runs, so store a copy elsewhere first if you may need it.
Fatture in Cloud20

Delete a Supplier

Action

In Make“Deletes a specific supplier.”

Deletes one supplier from your company in Fatture in Cloud. It clears vendors that were created by a test run or duplicated by an import.

When to use it
a supplier was added twice by an earlier scenario and you are cleaning up the list.
Watch out
deletion is final; run List All Suppliers and check the bundle before letting this module act.
Fatture in Cloud21

Download E-Invoice XML

Action

In Make“Downloads the e-invoice in XML format.”

Fetches the XML file of an e-invoice so the scenario can store it, forward it or hand it to another tool. You get the file itself, not only a record about it.

When to use it
your accountant wants every e-invoice XML dropped into a shared folder as soon as it exists.
Watch out
the next module must accept a file, such as an upload to cloud storage or an email attachment.
Fatture in Cloud22

Get a Cashbook Entry

Action

In Make“Gets a cashbook entry.”

Reads one cashbook entry and returns its details to the scenario, so later modules can reuse its details.

When to use it
a reconciliation step needs to compare one entry in Fatture in Cloud with a line from your bank.
Watch out
you need to know which entry to read; List All Cashbook Entries helps when you do not have it yet.
Fatture in Cloud23

Get a Client

Action

In Make“Gets a specified client.”

Pulls the full record of one client from Fatture in Cloud, so the scenario has its details at hand for an email, a document or a sync to another app.

When to use it
a new document arrives and you want the client's full details before notifying your sales rep.
Watch out
it returns one client; when you need several, List All Clients is the better fit.
Fatture in Cloud24

Get an Archive Document

Action

In Make“Gets a specific archive document.”

Reads one document stored in the Fatture in Cloud archive and brings its details into the scenario. That lets you check it before updating or deleting it.

When to use it
a flow must confirm that a file really sits in the archive before telling someone it is filed.
Watch out
the module reads a single archive document; List All Archive Documents covers a whole batch.
Fatture in Cloud25

Get an E-Invoice Rejection Reason

Action

In Make“Gets a specific e-invoice rejection reason.”

Tells you why an e-invoice was rejected, in a form the scenario can pass along. The person who has to fix the invoice gets the reason without logging in.

When to use it
a rejected e-invoice should create a task for your billing team with the reason written in it.
Watch out
it explains a rejection; it does not correct the invoice, so plan the fix and resend as separate steps.
Fatture in Cloud26

Get an F24

Action

In Make“Gets a specific F24.”

Retrieves one F24 from Fatture in Cloud with its details, ready to be mapped into a reminder, a report or another app.

When to use it
a payment reminder should quote the values of a specific F24 before its due date is reached.
Watch out
it needs a precise F24 to read; List All F24s finds it when the scenario does not know it yet.
Fatture in Cloud27

Get an Issued Document

Action

In Make“Gets a specific issued document.”

Loads the details of one issued document into the scenario, so later modules can use its content in an email, a report or a check against another tool.

When to use it
a new invoice was spotted by the trigger and you need more of its content for an email or a report.
Watch out
each call is one operation, so avoid it when the trigger already gives what you need.
Fatture in Cloud28

Get a Product

Action

In Make“Gets a specific product.”

Reads a single product from your Fatture in Cloud list and returns its details to the scenario, so another tool can show the same item.

When to use it
a price or description should be copied into your online shop or a quote template.
Watch out
it reads one item; for a full catalog sync, List All Products returns every product.
Fatture in Cloud29

Get a Receipt

Action

In Make“Gets a specific receipt.”

Fetches one receipt and its details from Fatture in Cloud, so a later module can reuse the amount or send it on.

When to use it
a customer asks for a copy and a helpdesk flow needs the receipt details to reply.
Watch out
you need the specific receipt to target; find it with List All Receipts when it is unknown.
Fatture in Cloud30

Get a Received Document

Action

In Make“Gets a specific received document.”

Reads one received document, such as a supplier bill, and puts its details in the scenario for approval flows or reports.

When to use it
a bill needs manager approval, and the approval message should show its amount and supplier.
Watch out
it reads a single document; List All Received Documents is the way to review many at once.
Fatture in Cloud31

Get a Supplier

Action

In Make“Gets a specific supplier.”

Returns the details of one supplier in Fatture in Cloud so a scenario can reuse them, for example in a purchase order or a message to your buyer.

When to use it
a received bill arrives and you want the supplier's details next to it in a Slack or email alert.
Watch out
only one supplier comes back per run; loop through List All Suppliers for more.
Fatture in Cloud32

Get Company Info

Action

In Make“Gets the company detailed info.”

Returns the detailed information of your company as Fatture in Cloud stores it. Other modules can then print or check those details without hard-coding them in the scenario.

When to use it
a document template elsewhere needs your company details and you want them to follow any change.
Watch out
it describes the company tied to the connection; with several companies, check which one you read.
Fatture in Cloud33

Get Issued Document Pre-Create Info

Action

In Make“Retrieves the information useful while creating a new document.”

Gathers the information that helps before you create a new document, so the scenario builds the document with choices the account actually offers.

When to use it
you are setting up Create an Issued Document and want to see what the account expects first.
Watch out
treat it as a helper for the creation step; on its own it creates nothing.
Fatture in Cloud34

Get Receipt Pre-Create Info

Action

In Make“Retrieves the information useful for creating a new receipt.”

Retrieves what is useful to know before creating a new receipt, which saves you guessing values and failing a first run.

When to use it
you are building a receipt flow for the first time and want to match the account's settings.
Watch out
it only prepares; the receipt appears only once Create a Receipt runs.
Fatture in Cloud35

Get Received Documents Pre-Create Info

Action

In Make“Retrieves the information useful while creating a new document.”

Brings back the information that makes creating a received document smoother, so your supplier-bill flow uses values the account knows.

When to use it
you are wiring Create a Received Document and want the right options before the first test.
Watch out
it feeds the creation step and writes nothing to your books by itself.
Fatture in Cloud36

Get User Info

Action

In Make“Gets the current user's info.”

Returns information about the user behind the connection. It is a quick way to confirm which Fatture in Cloud account a scenario really talks to.

When to use it
several people share a Make team and you want to check whose account a connection uses.
Watch out
it describes the connected user, not your clients or your company records.
Fatture in Cloud37

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Fatture in Cloud API with the connection you already set up. It covers what the other 60 action and search modules do not expose.

When to use it
you need an operation the listed modules lack and do not want a second login or a separate tool.
Watch out
you write the request yourself, so keep the Fatture in Cloud API documentation open while you set it up.
Fatture in Cloud38

Send E-Invoice

Action

In Make“Sends the e-invoice to SDI.”

Sends an e-invoice to SDI from inside the scenario. The invoice leaves Fatture in Cloud without anyone clicking send in the app.

When to use it
every new issued document should go to SDI as soon as the scenario picks it up.
Watch out
run Verify E-Invoice XML first, so a malformed file is caught before it is sent.
Fatture in Cloud39

Update a Cashbook Entry

Action

In Make“Updates a specific cashbook entry.”

Changes an existing cashbook entry in Fatture in Cloud, so a correction made upstream reaches your books without a manual edit.

When to use it
a payment amount is adjusted in your payment tool and the cashbook should reflect the new figure.
Watch out
map only the values that change; the scenario needs to point at the exact entry to edit.
Fatture in Cloud40

Update a Client

Action

In Make“Updates a specific client.”

Edits the record of an existing client in Fatture in Cloud using fresh data from another tool, so billing details stay current.

When to use it
a customer changes address in your CRM and the next invoice must carry the new one.
Watch out
if the client may not exist yet, check with List All Clients and branch to Create a Client.
Fatture in Cloud41

Update an Archive Document

Action

In Make“Updates a specific archive document.”

Keeps a document stored in your Fatture in Cloud archive accurate without opening the app: the scenario rewrites the archive entry you point it to, so the stored copy matches what your team now knows about it.

When to use it
A contract or statement filed earlier needs a corrected description after someone in the office spots an error in the shared tracker.
Watch out
the module acts on one existing archive document, so map its ID from List All Archive Documents or an earlier module first.
Fatture in Cloud42

Update an F24

Action

In Make“Updates a specific F24.”

Lets Make correct an F24 already recorded in Fatture in Cloud, so the figures or details your accountant sees stay in line with the source you trust, such as a spreadsheet the bookkeeper maintains.

When to use it
A payment line in your tracking sheet changes and the matching F24 in Fatture in Cloud has to follow.
Watch out
pick the right record: run List All F24s before this module when the scenario does not already carry the F24 ID.
Fatture in Cloud43

Update an Issued Document

Action

In Make“Updates a specific issued document.”

Rewrites an invoice or other issued document straight from the scenario, which spares you a trip into Fatture in Cloud each time a detail shifts after the document was created.

When to use it
A deal updated in your CRM changes the terms of a quote you already issued, and the document should reflect it.
Watch out
an issued document may already have gone out to the customer, so decide in the scenario which documents Make may still change.
Fatture in Cloud44

Update a Product

Action

In Make“Updates a specific product.”

Brings a catalog item in Fatture in Cloud up to date from another tool, so the next quote or invoice picks the current wording or price instead of an old one.

When to use it
your online shop or product sheet is the reference, and a change there should land in the Fatture in Cloud catalog too.
Watch out
the module needs the product it should change; a List All Products step before it is the usual way to find that ID by name.
Fatture in Cloud45

Update a Receipt

Action

In Make“Updates a specific receipt.”

Adjusts a receipt already stored in Fatture in Cloud, so the corrected version is the one your records show without anyone retyping it by hand in the app.

When to use it
A till or booking system sends a correction for a sale that was already recorded as a receipt.
Watch out
A receipt changed here is likely to show up in the totals of Get Receipts Monthly Total too, so test with Run once, the editor button that executes the scenario one time.
Fatture in Cloud46

Update a Received Document

Action

In Make“Updates a specific received document.”

Fixes the data of a supplier bill or other received document once it sits in Fatture in Cloud, useful when the first version was entered from incomplete information.

When to use it
A purchase approval tool confirms the final amount or category of a bill that the team logged earlier.
Watch out
if the scenario starts from List All Received Documents, each bundle (one item passed to the next module) is one document, so filter before updating.
Fatture in Cloud47

Update a Supplier

Action

In Make“Updates a specific supplier.”

Keeps a supplier card in Fatture in Cloud identical to the one in your purchasing tool or shared contact base, so bills are matched to the correct details.

When to use it
A vendor sends new details and your procurement sheet is updated first.
Watch out
choose the supplier by ID; two suppliers with close names are easy to confuse if you match on text alone.
Fatture in Cloud48

Upload an Archive Document

Action

In Make“Uploads a file and creates an archive document.”

Sends a file from your scenario into the Fatture in Cloud archive and creates the archive document at the same time, so paperwork stops living in email attachments.

When to use it
A signed PDF lands in cloud storage or an inbox and should be filed next to your accounting data.
Watch out
the module expects the file itself, so map the file data from a module that downloads it, not just its name or link.
Fatture in Cloud49

Verify E-Invoice XML

Action

In Make“Verifies the e-invoice xml format, mandatory fields and format.”

Checks an e-invoice XML before you rely on it: Make asks Fatture in Cloud to validate the format and the mandatory fields, and returns the verdict to the next module.

When to use it
you want a safety step right before Send E-Invoice, so a faulty file is caught instead of going out.
Watch out
the check hands back a result, so add a filter before Send E-Invoice that only lets a validated file through.
Fatture in Cloud50

Get Receipts Monthly Total

Search

In Make“Returns the monthly totals by year and receipt type.”

Returns the receipt totals for each month of a year, broken down by receipt type, which gives a reporting scenario ready figures instead of adding up receipts one by one.

When to use it
A dashboard or shared sheet should show how sales on receipts evolve through the year.
Watch out
ask for the year you need; the answer is grouped by month and receipt type, so a report per client or per product needs List All Receipts instead.
Fatture in Cloud51

List All Archive Documents

Search

In Make“Lists all documents in archive for the company.”

Pulls the documents stored in your company archive, each one arriving as its own bundle, so the next modules can sort, copy or report on them.

When to use it
you need to find the archive entry to change or remove, or send an inventory of filed papers to a spreadsheet.
Watch out
A search module can return zero, one or many items; each item then runs the following modules and costs operations, the executions Make counts on your plan.
Fatture in Cloud52

List All Cashbook Entries

Search

In Make“Lists all cashbook entries for the company.”

Reads the cashbook of your company as a list of entries, handy to mirror money movements in a spreadsheet or to spot one entry before editing it.

When to use it
an owner wants the cashbook visible in a shared sheet without giving everyone access to Fatture in Cloud.
Watch out
every entry becomes a separate bundle, so a long cashbook multiplies the operations of the modules placed after this one.
Fatture in Cloud53

List All Clients

Search

In Make“Lists all clients for the company.”

Gives the scenario every client of the company as separate items, which is the starting point when you want to sync your customer base with a CRM or mailing tool.

When to use it
you set up a first sync and need all existing clients, not only the new ones Watch New Clients will catch from now on.
Watch out
for new clients only, prefer the Watch New Clients trigger; this search reads the whole list each time it runs.
Fatture in Cloud54

List All F24s

Search

In Make“Lists all F24s for the company.”

Lists the F24s recorded for your company so the scenario can report on them or find the one to update, attach or clean up.

When to use it
your accountant asks for an overview of F24s in a shared file, or a later step needs a specific F24 ID.
Watch out
each F24 found starts the modules that follow once, so add a filter if only some of them matter.
Fatture in Cloud55

List All Issued Documents

Search

In Make“Lists the issued documents of the company.”

Fetches the issued documents of the company, invoices and quotes included, as individual bundles ready for a report, an export or a follow-up step.

When to use it
A sales review needs every issued document copied to a sheet, or you must locate one document before editing it.
Watch out
this search reads what exists now; to react to documents as they are created, Watch New Issued Documents is the better fit.
Fatture in Cloud56

List All Products

Search

In Make“Lists all the products for a company.”

Returns the full product catalog stored in Fatture in Cloud, one product per bundle, so you can compare it with your shop or pricing sheet.

When to use it
before Update a Product, to find the right item, or when you audit catalog wording against another source.
Watch out
A big catalog means many bundles and as many operations downstream; filter early to keep the scenario light.
Fatture in Cloud57

List All Receipts

Search

In Make“Lists all receipts for the company.”

Collects every receipt of the company as separate items, useful when you need the detail behind the monthly figures rather than the totals alone.

When to use it
A reconciliation step compares receipts one by one with payments recorded in another tool.
Watch out
for totals only, Get Receipts Monthly Total is lighter, since it returns figures instead of each receipt.
Fatture in Cloud58

List All Received Documents

Search

In Make“Lists all received documents for the company.”

Retrieves the supplier bills and other received documents of the company, each one ready to be checked, copied or updated by the next module.

When to use it
an approval flow needs all received documents in a sheet, or you want to spot the one to correct with Update a Received Document.
Watch out
the list can be empty; add a filter or error route so the scenario does not fail silently when nothing comes back.
Fatture in Cloud59

List All Suppliers

Search

In Make“Lists all suppliers for the company.”

Brings back all suppliers of the company as individual bundles, the base for keeping a purchasing tool or shared vendor list aligned with Fatture in Cloud.

When to use it
you prepare a one-time sync of vendors, or need a supplier ID before Update a Supplier.
Watch out
match on the supplier ID in later steps rather than on the name, which can vary from one tool to another.
Fatture in Cloud60

List User Companies

Search

In Make“Lists the companies controlled by the current user.”

Shows which companies the connected user controls in Fatture in Cloud, so the scenario knows which company every other module should work on.

When to use it
your connection, the Fatture in Cloud account linked to Make, gives access to more than one company and you want to pick the right one.
Watch out
most modules act on a single company; check this list when results look like they come from the wrong business.
Need help

Need help automating Fatture in Cloud with Make?

A person reads every message.

FAQ

Fatture in Cloud and Make: common questions

01Is the Fatture in Cloud Make integration free?
Yes, you can use it on the Free plan, because Fatture in Cloud is a standard app in Make and standard apps are open on every plan. The Free plan caps you at 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution and files up to 5 MB. Paid plans lift those limits and count usage in credits, meaning operations. Fatture in Cloud has its own subscription, and some features need a paid plan on that side.
02What do you need to connect Fatture in Cloud to Make?
You need an active Fatture in Cloud account and an API token. In Make you add any Fatture in Cloud module, click Create a connection, optionally name it, then paste your credentials or follow the on-screen steps. If you prefer your own OAuth2 app, you create it under Impostazioni then Sviluppatore in Fatture in Cloud, set the callback URI given by Make, and copy the Client ID and Client secret into the connection.
03Does the Fatture in Cloud trigger work in real time?
No. Both Fatture in Cloud triggers, Watch New Clients and Watch New Issued Documents, are scheduled. Make checks the account on the scenario's schedule, which is every 15 minutes by default on a new scenario. The Free plan cannot go below 15 minutes; paid plans allow intervals down to 1 minute. A new client or document therefore shows up at the next check, not at the second it is saved.
04What if a Fatture in Cloud module is missing in Make?
Use Make an API call. It reaches any endpoint of the Fatture in Cloud API with the connection you already have, so you are not stuck with the 49 actions and 11 searches on the list. You write the request yourself, which takes a look at the Fatture in Cloud API documentation. The official Make documentation for this app gives no specific limits to plan around, so check vendor details with Fatture in Cloud directly.
05Should you use Make or n8n for Fatture in Cloud?
It depends on the tool your team already knows. In Make, Fatture in Cloud comes with 62 ready modules, a visual editor and a Free plan to test a first scenario. Many apps also have an n8n node, so look at what exists there for this one before choosing. Compare the modules you need on each side, the way usage is counted and who will maintain the flow, rather than a general ranking of the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations