Resources · Zapier integration

Fatture in Cloud Zapier integrationAutomate Fatture in Cloud with Zapier.

The Fatture in Cloud Zapier integration gives you 2 triggers, 86 actions and 19 searches on the Italian invoicing tool: issued and received documents, e-invoices, clients, suppliers, receipts and tax forms, all from one Zap.

See the 107 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Fatture in Cloud Zapier integration actually does

It links your Fatture in Cloud company to Zapier so that an event in the invoicing tool, on the resource types you choose, starts an automation on its own. From there, Zapier can create, read, update, send or delete almost every record the app keeps: documents, clients, products, receipts, cashbook entries and tax payment forms.

Three results you can build on day one. A clean e-invoice run: an event on an issued document starts the Zap, Verify E-Invoice XML checks the mandatory fields, then Send E-Invoice passes it to the SDI. A document that reaches the client by itself: Schedule Email queues the sending of an invoice, PDF attached if you want it. A tidy back office: Create Client, Create Supplier and Create Product keep your registry in step with what happens elsewhere.

Now the limits. Both triggers are generic: they report events on the resource types you pick, they are not ready-made events like "invoice paid". Nothing on the Zapier side offers a find-or-create shortcut for this app, so a missing client means a search, then a separate create step. An uploaded attachment is not tied to its document until you do that link yourself in a later step. And no Zap ever reaches back to documents created before it was switched on.

If you are weighing tools, the same app has a Fatture in Cloud Make integration page, and the n8n vs Zapier comparison is the place to weigh the two.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here is what each one means in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier simply waits for that event to show up.
Action
What the Zap does once it has started: the step that writes, sends or changes something in an app for you.
Task
The unit Zapier bills: one action your Zap finishes successfully. The count on your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer by Zapier. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Cost

What it really costs to run

Fatture in Cloud is not a premium app on Zapier, so it works from the free plan. The real question is how many tasks your Zaps burn.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, two-step Zaps only
  • Trigger costNone, only completed actions count
  • Triggers of this app2, both instant

The trigger itself never costs a task, and neither does Zapier looking for new data. Each action that completes is billed on its own: a Zap that verifies an XML and then sends the e-invoice eats two tasks per document. An action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but only two-step Zaps: one trigger, one action. Add a filter, a search or a second action and you have a multi-step Zap, which needs a paid plan. The plan grid of polling intervals does not touch this app, since both of its triggers are instant.

Connect

Connect Fatture in Cloud to Zapier

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Fatture in Cloud account linked once, then reused by every step that touches the app.

  2. 02

    Pick Fatture in Cloud

    Type Fatture in Cloud in the search box of the dialog, select it, then click Add connection. You need an account on the app, plus access to any company you do not own yourself.

  3. 03

    Sign in and grant access

    Log in to Fatture in Cloud in the tab that opens and allow Zapier to use the account. From then on, every Fatture in Cloud step of every Zap can reuse this one connection.

First Zap

Your first Zap: check and send each e-invoice

GoalAn event on an issued document starts the Zap, a filter keeps only the ones you care about, the XML is checked, then the e-invoice goes out.

  1. 01

    Build the trigger

    In Build, choose Fatture in Cloud as the app and Receive Enriched Event as the event. Pick your connection, then the company, the resource type and the event types to listen to.

  2. 02

    Test it on a real document

    Click Test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real document rather than an invented one.

  3. 03

    Add the filter

    From the plus icon, add Filter and set the field, the rule and the value. Use a rule that matches the data type, or the filter never lets anything through.

  4. 04

    Check, then send

    Add Verify E-Invoice XML, then Send E-Invoice, and map the company and the document ID from the trigger into both steps.

  5. 05

    Publish

    Run each step once with Test, read what came back, then click Publish. With a filter and two actions, this is a multi-step Zap on a paid plan.

Triggers

Fatture in Cloud triggers on Zapier

2 events start a Zap when something happens in Fatture in Cloud, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Receive Enriched Event

Instant trigger

In Zapier“Triggers when a webhooks arrives from Fatture in Cloud, returns an array of resources.”

Fires when Fatture in Cloud reports an event on the resource types you chose, and hands over the records involved rather than bare IDs. That makes it the comfortable choice: the steps that follow can use their content straight away, with no extra lookup.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want to act on what the document contains, for example pass a freshly issued invoice to the e-invoice checks without a separate read step.
Watch out
the company, the resource type and the event types are all mandatory, so decide up front which events you really want before you test.
2

Receive Raw Event

Instant trigger

In Zapier“Triggers when a webhooks arrives from Fatture in Cloud, returns an array of ids.”

Starts your Zap on the same kind of events, but only passes along a list of IDs. It is the lean version: you know which records moved, and you decide later which ones are worth reading in full.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your Zap only needs to know which document changed, or you plan to read just one record with a Get Issued Document step.
Watch out
every detail you need later costs an extra action, and so an extra task, because the event itself carries nothing but identifiers.
Actions

Fatture in Cloud actions on Zapier

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

1

Create Archive Document

Action

In Zapier“Creates a new archive document.”

Files a paper in the archive section of the company, a space for documents that are neither invoices nor receipts, such as contracts or certificates.

When to use it
signed contracts collected in an e-signature tool should be kept in the same company as your accounting.
Watch out
the file itself goes up through Upload Archive Document Attachment; this step only creates the record.
2

Create Cashbook Entry

Action

In Zapier“Creates a new cashbook entry.”

Records a money movement in the cashbook of the company, on an incoming or an outgoing payment account, outside of any invoice.

When to use it
money moves without a document, a cash withdrawal or a bank fee for example, and the cashbook should still show it.
Watch out
the entry has an incoming and an outgoing payment account side; map the account on the side that matches the movement.
3

Create Client

Action

In Zapier“Creates a new client.”

Adds someone to your client registry, along with their defaults: VAT type, payment method, discount display and whether this client uses e-invoices.

When to use it
a new customer signs up in a form or a CRM and should exist on the invoicing side before the first document is issued.
Watch out
run a List Clients search first; nothing in this app checks for an existing client on its own, so a blind create gives you duplicates.
4

Create F24

Action

In Zapier“Creates a new F24.”

Records a new F24 payment form in the company and links it to the payment account it will be paid from, so tax payments show up next to the rest of your money flows.

When to use it
your accountant shares the forms through another tool and you want each one tracked in Fatture in Cloud without copying it.
Watch out
the proof of payment is a separate upload, handled by Upload F24 Attachment.
5

Create Issued Document

Action

In Zapier“Creates a new document.”

Writes a brand new outgoing document in your company, of the type you pick, with its client, its lines and its payments.

When to use it
a deal closed in your CRM or a paid order in your shop should become a proper invoice without anyone retyping the lines.
Watch out
the step exposes a long list of options, from split payment to delivery notes and the Sistema Tessera Sanitaria, so map only the ones you understand and leave the rest on their defaults.
6

Create Payment Account

Action

In Zapier“Creates a new payment account.”

Adds a payment account to the company, which documents can then use as the place their payments land.

When to use it
a new bank account opens and the documents your Zaps create from now on should be paid into it.
Watch out
accounts can be flagged as virtual; check that flag before relying on the account for reconciliation.
7

Create Payment Method

Action

In Zapier“Creates a new payment method.”

Defines a new way of being paid, can make it the default for new documents, and can point it at a default payment account.

When to use it
you start accepting a new method, a payment link for instance, and want it ready on the next documents.
Watch out
the default flag is set in this very step, so leave it off unless this method really should become the default.
8

Create Product

Action

In Zapier“Creates a new product.”

Puts a new item into the catalogue with its default VAT type, a choice between gross and net pricing, and a flag for whether you track stock on it.

When to use it
your catalogue lives in a shop or an ERP and Fatture in Cloud should mirror each item added there.
Watch out
the default VAT type and the gross or net choice are set right here, so map them on purpose instead of leaving them to chance.
9

Create Receipt

Action

In Zapier“Creates a new receipt.”

Adds a receipt to the company, with its lines, its VAT types and the payment account the money went into.

When to use it
a shop, a till or a booking tool records a sale that should land in Fatture in Cloud as a receipt.
Watch out
an option numbers the receipt progressively for you, which spares a lookup of the last number used.
10

Create Received Document

Action

In Zapier“Creates a new document.”

Books a supplier bill or another incoming document, lines and payments included, so your purchases sit in the same company as your sales and your totals stay complete.

When to use it
expenses reach you by email, in a drive or through a purchasing tool, and you want them recorded without a manual entry for each one.
Watch out
one option allows the item total and the payment total to differ; leave it on its default unless your accountant asks for it.
11

Create Supplier

Action

In Zapier“Creates a new supplier.”

Registers a vendor in the company, ready to be attached to the incoming documents you book later.

When to use it
you onboard suppliers through a form or a spreadsheet and want each one available before its first bill arrives.
Watch out
like clients, suppliers have no automatic duplicate check, so look them up with List Suppliers before creating.
12

Create Vat Type

Action

In Zapier“Creates a vat type.”

Creates a VAT type in the company and states whether it may be used on e-invoices, so later documents and products can rely on it.

When to use it
a new rate or exemption starts to apply and the documents built by your Zaps must be able to use it.
Watch out
a VAT type not flagged for e-invoices cannot carry an e-invoice later, so set that flag deliberately.
13

Delete Archive Document

Action

In Zapier“Deletes the specified archive document.”

Removes a record from the archive section of the company, from its ID.

When to use it
archived papers past their keeping period should leave the company.
Watch out
check the record ID twice before publishing; a Zap runs without asking anyone.
14

Delete Bin Issued Document

Action

In Zapier“Delete Bin Issued Document”

Removes an outgoing document from the bin itself.

When to use it
a clean-up routine should empty the bin of invoices you are sure about.
Watch out
a filter in front of it keeps the Zap from emptying documents you still want.
15

Delete Bin Received Document

Action

In Zapier“Delete Bin Received Document”

Clears one supplier document out of the bin.

When to use it
duplicate bills were binned and should not linger there.
Watch out
if a bill may still be needed, Recover Received Document From the Bin is the step to use instead.
16

Delete Cashbook Entry

Action

In Zapier“Deletes the specified cashbook entry.”

Erases one movement from the cashbook of the company, identified by its ID.

When to use it
a movement was recorded twice by two different Zaps and one copy has to go.
Watch out
the movement ID comes from List Cashbook Entries for the right dates.
17

Delete Client

Action

In Zapier“Deletes the specified client.”

Deletes a client from your registry in Fatture in Cloud, from its ID.

When to use it
a customer is removed from your CRM and you want both lists aligned.
Watch out
it needs the client ID, which List Clients can find.
18

Delete F24

Action

In Zapier“Removes the specified F24.”

Removes an F24 form from the company, from the ID of the form.

When to use it
a form was recorded by mistake or replaced by a corrected version.
Watch out
if only the file is wrong, Delete F24 Attachment is the lighter move.
19

Delete F24 Attachment

Action

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

Detaches the file from an F24 form, leaving the form itself untouched.

When to use it
the proof of payment was attached to the wrong form.
Watch out
re-attach the right file afterwards with an upload step and a modify step.
20

Delete Issued Document

Action

In Zapier“Deletes the specified document.”

Deletes one outgoing document, found by its ID.

When to use it
a draft created by an earlier Zap turns out to be a duplicate and should vanish.
Watch out
a Zap acts without asking, so a filter that checks the status is a cheap safety net.
21

Delete Issued Document Attachment

Action

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

Takes the attached file off an outgoing document and leaves the document itself in place.

When to use it
the wrong file went out with an invoice and must be swapped for the right one.
Watch out
uploading the replacement is a separate step with its own token.
22

Delete Payment Account

Action

In Zapier“Deletes the specified payment account.”

Removes a payment account from the company, from its ID.

When to use it
a bank account is closed and should no longer be offered on new documents.
Watch out
the account ID is mandatory; List Payment Accounts gives it.
23

Delete Payment Method

Action

In Zapier“Deletes the specified payment method.”

Deletes a payment method you no longer accept from the company.

When to use it
a way of paying is dropped and new documents should not show it.
Watch out
the method ID is required; List Payment Methods gives it.
24

Delete Product

Action

In Zapier“Deletes the specified product.”

Deletes an item from the product catalogue of the company, from its ID.

When to use it
a product is discontinued in the shop or ERP that owns your catalogue.
Watch out
List Products confirms the ID before anything is removed.
25

Delete Receipt

Action

In Zapier“Deletes the specified receipt.”

Deletes one receipt from the company, starting from its ID.

When to use it
a sale is voided in the till and its receipt must disappear too.
Watch out
List Receipts finds the ID when only the sale reference is known.
26

Delete Received Document

Action

In Zapier“Deletes the specified document.”

Removes a supplier document from the company.

When to use it
a supplier cancels a bill in their portal and your books should follow.
Watch out
it needs the document ID, so a search or a trigger has to hand it over.
27

Delete Received Document Attachment

Action

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

Strips the attached file from a supplier document while keeping the booked record itself.

When to use it
a scan was unreadable and a better copy is on its way.
Watch out
the record stays booked; only the file goes.
28

Delete Supplier

Action

In Zapier“Deletes the specified supplier.”

Removes a vendor from the supplier list of the company, from its ID.

When to use it
a supplier is retired from your purchasing list in another tool and should leave Fatture in Cloud too.
Watch out
find the ID with List Suppliers first.
29

Delete Vat Type

Action

In Zapier“Deletes the specified vat type.”

Removes a VAT type from the company, starting from its ID.

When to use it
a rate was created by mistake and nobody should pick it.
Watch out
for a rate that merely stopped applying, disabling it with Modify Vat Type is gentler.
30

Get Archive Document

Action

In Zapier“Gets the specified archive document.”

Brings back one record from the archive section, by ID.

When to use it
a filed contract needs to be shared with a colleague or copied to a document tool.
Watch out
you get the archive record; its file is a separate attachment.
31

Get Bin Issued Documents List

Action

In Zapier“Get bin issued documents detail”

Despite its plural name, this action reads one outgoing document sitting in the bin, from its ID.

When to use it
you want to see what a deleted invoice contained before deciding whether to restore it.
Watch out
the search with the same name lists the bin; this action reads a single item.
32

Get Bin Received Documents List

Action

In Zapier“Get bin issued documents detail”

Reads one supplier document that ended up in the bin, by its ID, even though the label sounds like a list.

When to use it
an expense was thrown away and someone needs to see it before it goes for good.
Watch out
do not confuse it with the search of the same name, which returns the whole bin.
33

Get Cashbook Entry

Action

In Zapier“Gets the specified cashbook entry.”

Reads one cashbook movement in detail, with its accounts.

When to use it
a reporting sheet should hold each movement with its full content, not only the total.
Watch out
you need the movement ID, which the list search returns.
34

Get Client

Action

In Zapier“Gets the specified client.”

Reads one client record from its ID, with all the defaults stored on it.

When to use it
a step needs the client's details, say for a CRM update, and only the ID reached the Zap.
Watch out
a client found by List Clients often already carries what you need, so this step can be skipped.
35

Get Client Info

Action

In Zapier“Retrieves the information useful while creating a new Client.”

Retrieves the helper information Fatture in Cloud relies on when a client is created.

When to use it
a sign-up flow creates clients and you want the allowed options before writing anything.
Watch out
it describes options; it does not read an existing client, which is Get Client.
36

Get Company Info

Action

In Zapier“Gets the company detailed info.”

Reads the detailed information of the company you work on.

When to use it
a document or an email built in another tool should carry your own company details.
Watch out
it covers the company chosen in the step, not every company of the account.
37

Get Company Plan Usage

Action

In Zapier“Gets the company limits usage.”

Reports how much of its Fatture in Cloud limits the company has used, for the category you pick.

When to use it
you want a warning before you hit what your Fatture in Cloud subscription allows.
Watch out
the category field is mandatory and decides which limit you read.
38

Get E-Invoice Rejection Reason

Action

In Zapier“Get e-invoice rejection reason”

Fetches the explanation behind a rejected e-invoice, so the reason can travel to whoever has to fix it.

When to use it
your team should get the actual reason for a rejection in their chat tool, not just a red status to investigate.
Watch out
it needs the ID of the rejected document, which an enriched event can carry into the Zap.
39

Get E-Invoice XML

Action

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

Downloads the e-invoice of a document as an XML file, with its attachment included if you ask for it.

When to use it
a copy of every e-invoice should be stored in a drive or passed to your accountant automatically.
Watch out
the document must already have an e-invoice; a plain invoice has no XML to give.
40

Get Email Data

Action

In Zapier“Gets the pre-compiled email details.”

Reads the email details Fatture in Cloud has already prepared for a document, the copy address included.

When to use it
you want to check who will receive a document before a Schedule Email step sends it, or reuse that address in another tool.
Watch out
it only reads; nothing is sent until the scheduling step runs.
41

Get Existing Issued Document Totals

Action

In Zapier“Returns the totals for a specified document.”

Returns the totals of an outgoing document already in the company.

When to use it
a dashboard or a sheet should record the real totals of each invoice as Fatture in Cloud computes them.
Watch out
it needs the document ID, so it often follows a trigger or a search.
42

Get Existing Received Document Totals

Action

In Zapier“Returns the totals for the specified document.”

Gives back the totals of a supplier document already booked, computed by Fatture in Cloud from its lines and payments.

When to use it
your purchase tracking needs the computed totals rather than the raw lines.
Watch out
the document ID is required.
43

Get F24

Action

In Zapier“Gets the specified F24.”

Fetches one F24 form from its ID, account included.

When to use it
you remind a colleague of a form before its due date and want its details in the message.
Watch out
the form ID comes from List F24 or from an enriched event.
44

Get Issued Document

Action

In Zapier“Gets the specified document.”

Reads one outgoing document in full from its ID.

When to use it
you started from Receive Raw Event, which only gives IDs, and now need the details behind one of them.
Watch out
each read is one more task on every run, so skip it when an enriched event already carries the data.
45

Get Issued Document Pre-Create Info

Action

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

Gathers what Fatture in Cloud offers as helper data before an outgoing document of a given type is created.

When to use it
you want valid defaults in hand before a Create Issued Document step, especially for a type you rarely use.
Watch out
the document type is mandatory, so one call covers one type.
46

Get New Issued Document Totals

Action

In Zapier“Returns the totals for a new document.”

Computes the totals of an outgoing document that does not exist yet, from the lines you pass.

When to use it
you want to show a client the final amount, taxes included, before the invoice is actually issued.
Watch out
nothing is created; you still need Create Issued Document afterwards.
47

Get New Received Document Totals

Action

In Zapier“Returns the totals for a new document.”

Works out the totals of an incoming document before it is recorded.

When to use it
you want to compare the amount a supplier announced with what Fatture in Cloud computes from the lines.
Watch out
this is a dry calculation; the bill is booked by another step.
48

Get Payment Account

Action

In Zapier“Gets the specified payment account.”

Returns the settings of one payment account.

When to use it
you want to show which bank account a document will be paid into, for example in a reminder.
Watch out
it reads one account; the full list comes from List Payment Accounts.
49

Get Payment Method

Action

In Zapier“Gets the specified payment method.”

Fetches one payment method along with its default account, so a later step can read where that method sends the money.

When to use it
a document step should reuse the details of a method you only hold by ID.
Watch out
the method ID comes from List Payment Methods.
50

Get Pending Received Document

Action

In Zapier“Gets the specified pending received document.”

Reads an incoming document still sitting in the pending list, before anyone has booked it.

When to use it
someone should review a pending expense in their chat tool before it becomes a real record.
Watch out
the ID comes from List Pending Received Documents.
51

Get PriceList Items List

Action

In Zapier“Retrieves all the Items of a PriceList”

Returns every item of one price list, with the prices that list applies.

When to use it
a catalogue export to your shop or a sheet should carry the prices of a specific reseller list.
Watch out
the price list ID is required; Get PriceLists gives it.
52

Get PriceLists

Action

In Zapier“Retrieves all price lists of the company”

Returns every price list defined in the company.

When to use it
you sell at different prices to resellers and end clients, and a step must know which lists exist.
Watch out
it returns the lists, not their items; that is the job of the next step.
53

Get Product

Action

In Zapier“Gets the specified product.”

Reads one catalogue item from its ID, price and VAT type included.

When to use it
a quote built in another tool should use the current price as Fatture in Cloud knows it.
Watch out
if you only know the product by name, start with List Products.
54

Get Receipt

Action

In Zapier“Gets the specified receipt.”

Loads a single receipt from its ID, lines and payment account included.

When to use it
you report each receipt to a sheet or a BI tool and need its full content.
Watch out
a raw event gives you the ID only, so this step usually follows it.
55

Get Receipt Pre-Create Info

Action

In Zapier“Retrieves the information useful while creating a new receipt.”

Returns the information useful before a new receipt is created in the company.

When to use it
receipts come from a till system and their values should match what the app accepts.
Watch out
it reads only; the receipt is created by Create Receipt.
56

Get Receipts Monthly Totals

Action

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

Returns receipt totals month by month, for one year and one receipt type.

When to use it
a sales report should show how counter sales evolve over the year.
Watch out
both the receipt type and the year are mandatory, so one run gives one series.
57

Get Received Document

Action

In Zapier“Gets the specified document.”

Fetches one supplier document with everything it holds.

When to use it
a later step needs the supplier, the amount or the lines of a bill that reached the Zap as a bare ID.
Watch out
it reads booked documents; pending ones have their own step, Get Pending Received Document.
58

Get Received Document Pre-Create Info

Action

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

Collects the helper data needed to create an incoming document of a given type.

When to use it
your Zap books supplier bills and should know the accepted values before writing.
Watch out
like its issued twin, it needs the document type.
59

Get Supplier

Action

In Zapier“Gets the specified supplier.”

Loads the full record of one supplier.

When to use it
a payment request in your bank tool needs the supplier's name and details.
Watch out
it needs the supplier ID, so pair it with a search or an enriched event.
60

Get Tax Profile

Action

In Zapier“Gets the Tax Profile”

Returns the tax profile of the company, read-only, with nothing to fill in but the company ID.

When to use it
a step needs the company's tax profile in hand before it builds a document.
Watch out
it reads the profile; it cannot change it.
61

Get Template

Action

In Zapier“Gets a specified template.”

Loads one document template, the layout used when a document is printed.

When to use it
a Zap should check which layout a document will use before it goes to the client.
Watch out
the template ID comes from List Templates.
62

Get User Info

Action

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

Reads the details of the user behind the connection. It is the one action of this app that asks for no company ID.

When to use it
you manage several companies and want to confirm which account a Zap actually runs as.
Watch out
it tells you who is connected, not which companies that user can reach.
63

Get Vat Type

Action

In Zapier“Gets the specified vat type.”

Reads a VAT type of the company, including whether it can go on e-invoices.

When to use it
you want to confirm a rate is fit for an e-invoice before the document is created.
Watch out
the ID comes from List Vat Types.
64

Join Issued Documents

Action

In Zapier“Joins issued documents.”

Merges several outgoing documents into a single one, starting from the list of their IDs.

When to use it
a client should receive one document instead of several separate ones covering the same work.
Watch out
the step wants every ID at once, so a List Issued Documents search usually comes right before it, and that search makes the Zap multi-step.
65

Modify Archive Document

Action

In Zapier“Modifies the specified archive document.”

Edits a record of the archive section, found by its ID, and is the natural place to use an upload token.

When to use it
a contract was archived without its file, or its description has to change after signing.
Watch out
the record ID is mandatory; List Archive Documents finds it.
66

Modify Cashbook Entry

Action

In Zapier“Modifies the specified cashbook entry.”

Adjusts a movement already written in the cashbook, its amount or its accounts.

When to use it
a reconciliation in your banking tool shows a different amount and the cashbook has to match.
Watch out
it needs the ID of the movement, which List Cashbook Entries returns for a date range.
67

Modify Client

Action

In Zapier“Modifies the specified client.”

Rewrites a client record from its ID, defaults and e-invoice setting included.

When to use it
a customer updates their details in your CRM and the invoicing side must stay identical without a second edit.
Watch out
the client ID is required, and List Clients is the usual way to get it.
68

Modify F24

Action

In Zapier“Modifies the specified F24.”

Updates an F24 form already recorded, including the account it is paid from.

When to use it
the payment account of a form changes before its due date, or the attachment token from an upload must be applied.
Watch out
the step needs the ID of the form; List F24 finds it.
69

Modify Issued Document

Action

In Zapier“Modifies the specified document.”

Updates an outgoing document you already have, found by its ID: client, lines, payments or display options.

When to use it
something changes after issue, a payment date or a reference, and the document must follow what your other tools know.
Watch out
an issued document can be locked against edits; a locked one will not take your changes.
70

Modify Payment Account

Action

In Zapier“Modifies the specified payment account.”

Changes the settings of a payment account that already exists, its name or its virtual flag.

When to use it
a bank account is renamed and the label on your documents should follow.
Watch out
the account ID is required; List Payment Accounts gives it.
71

Modify Payment Method

Action

In Zapier“Modifies the specified payment method.”

Edits a payment method, including whether it is the default and which account it pays into.

When to use it
you switch your default way of being paid and want new documents to pick it up from now on.
Watch out
the method ID is required, and List Payment Methods returns it.
72

Modify Product

Action

In Zapier“Modifies the specified product.”

Changes a catalogue item: its price, gross or net pricing, VAT type or stock flag.

When to use it
prices are decided in your shop or ERP and Fatture in Cloud should always show the current one.
Watch out
the product ID is mandatory, so a List Products search often runs first.
73

Modify Receipt

Action

In Zapier“Modifies the specified receipt.”

Changes a receipt already recorded: its lines, its VAT, or the account the money went into.

When to use it
a counter sale was booked with the wrong item in the till and the correction should flow through.
Watch out
you need the receipt ID, which List Receipts can find.
74

Modify Received Document

Action

In Zapier“Modifies the specified document.”

Edits a supplier document already booked, for example to complete its payments or correct a line.

When to use it
a bill gets paid through your bank tool and the record in Fatture in Cloud should say so.
Watch out
like issued documents, received ones can be locked, and a locked record refuses changes.
75

Modify Supplier

Action

In Zapier“Modifies the specified supplier.”

Updates an existing supplier record, located by its ID.

When to use it
a vendor changes address or bank details, and your master list of vendors lives in another tool that should stay the reference.
Watch out
without the supplier ID the step cannot run; a List Suppliers search provides it.
76

Modify Vat Type

Action

In Zapier“Modifies the specified vat type.”

Updates a VAT type of the company: its use on e-invoices or its disabled flag.

When to use it
a rate stops applying and should no longer be offered when someone creates a document.
Watch out
the VAT type ID is required, and List Vat Types returns it.
77

Recover Issued Document From the Bin

Action

In Zapier“Recover Issued Document From the Bin”

Pulls an outgoing document back out of the bin and returns it to the company.

When to use it
an invoice was deleted by mistake and should reappear in the list without being recreated.
Watch out
you need the ID of the binned document, which the bin search provides.
78

Recover Received Document From the Bin

Action

In Zapier“Recover Received Document From the Bin”

Restores a supplier document from the bin to the company.

When to use it
a bill was removed too early and is still needed for the books.
Watch out
same as for issued documents, the bin search gives you the ID.
79

Schedule Email

Action

In Zapier“Schedules the sending of a document by email.”

Queues the sending of a document by email from Fatture in Cloud, with buttons to view it, its delivery note or its attachment, and the PDF attached if you tick that box.

When to use it
an invoice should reach the client as soon as your Zap has created it, with no one opening the app.
Watch out
the copy option sends to the address Get Email Data returns, not to one you type in the step.
80

Send E-Invoice

Action

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

Hands the e-invoice of a document over to the SDI.

When to use it
the invoice is complete and verified, and the Zap should send it without a person clicking the button.
Watch out
a dry-run option keeps the e-invoice from reaching the SDI; switch it on while you test the Zap, and off before you publish.
81

Transform Issued Document

Action

In Zapier“Transforms the document.”

Converts an existing outgoing document into another type, from the original ID and the new type you pick.

When to use it
a sale moves to its next stage in another tool and the follow-up document should exist at once, without anyone copying the lines.
Watch out
both the original ID and the target type are required, so the trigger or a search has to provide that ID.
82

Upload Archive Document Attachment

Action

In Zapier“Uploads an attachment destined to an archive document. The actual association between the document and the attachment must be implemented separately, using the returned token.”

Uploads the file meant for an archive record and hands you a token to connect the two.

When to use it
contracts or certificates collected elsewhere should be stored in the archive with their actual file.
Watch out
this step creates no link on its own; another step has to use the token to tie the file to the archive record.
83

Upload F24 Attachment

Action

In Zapier“Uploads an attachment destined to a F24. The actual association between the document and the attachment must be implemented separately, using the returned token.”

Sends the file of an F24 form, its receipt for instance, and returns a token that represents it.

When to use it
proof of payment should sit with each F24 your Zaps record, ready for an audit.
Watch out
the token still has to be applied to the form in another step.
84

Upload Issued Document Attachment

Action

In Zapier“Uploads an attachment destined to an issued document. The actual association between the document and the attachment must be implemented separately, using the returned token.”

Sends a file to Fatture in Cloud on behalf of an outgoing document and gives back a token that stands for that file.

When to use it
a signed order, a timesheet or a delivery proof should travel with the invoice it justifies.
Watch out
the file is not attached yet: a later step has to apply the token to the document.
85

Upload Received Document Attachment

Action

In Zapier“Uploads an attachment destined to a received document. The actual association between the document and the attachment must be implemented separately, using the returned token.”

Pushes the file of a supplier bill to Fatture in Cloud and returns a token for it, ready to be tied to the record.

When to use it
scanned purchase invoices arrive by email or in a shared folder and should end up next to their booking.
Watch out
linking the file to the document remains a separate move that reuses the token, so plan two steps.
86

Verify E-Invoice XML

Action

In Zapier“Verifies the e-invoice XML format. Checks if all of the mandatory fields are filled and compliant to the right format.”

Runs a format check on the XML of an e-invoice and flags missing mandatory fields before anything leaves the company.

When to use it
you want a safety net in front of every e-invoice your Zap sends, so mistakes stop inside your company instead of at the SDI.
Watch out
the check costs a task like any action, even when the XML is perfect.
Searches

Fatture in Cloud searches on Zapier

19 search steps look for data that already exists in Fatture in Cloud, so a later step can use it.

A search step looks up records that already exist and hands them to the next steps. In the editor, the searches of this app sit at the bottom of the Action event list, under SEARCH. Each one, like the actions, asks for the company ID, except List Cities and List Default Templates. This app offers no find-or-create variant.

1

List Archive Documents

Search

In Zapier“Lists the archive documents.”

Browses the records kept in the archive section of the company and hands them to the next steps.

When to use it
a step needs to know whether a contract is already filed before creating it again.
Watch out
it returns archive records, not their files.
2

Get Bin Issued Documents List

Search

In Zapier“Get bin issued documents list”

Returns the outgoing documents currently sitting in the bin.

When to use it
a clean-up Zap should see what was deleted before the bin is emptied.
Watch out
the action with the same label reads one binned document; this search lists them.
3

Get Bin Received Documents List

Search

In Zapier“Get bin Received documents list”

Lists the supplier documents waiting in the bin.

When to use it
an accountant wants a look at binned bills before anyone empties the bin.
Watch out
pair it with Recover Received Document From the Bin to bring one back.
4

List Cashbook Entries

Search

In Zapier“Lists the cashbook entries.”

Pulls the cashbook movements of the company between a start date and an end date.

When to use it
a reconciliation step needs every movement of a period to compare with the bank.
Watch out
both dates are mandatory, so map them from an earlier step or type them.
5

List Cities

Search

In Zapier“Lists the Italian cities.”

Checks a name against the list of Italian cities the app knows. Unlike the other searches, it needs no company ID.

When to use it
an address typed in a form should match a known city before a client is created.
Watch out
it only covers Italian cities.
6

List Clients

Search

In Zapier“Lists the clients.”

Searches your client registry and returns the matching records.

When to use it
before Create Client, a lookup stops you from creating the same customer twice.
Watch out
if several clients match, the default keeps the first one, which may not be the one you meant.
7

List Default Templates

Search

In Zapier“Lists the default available templates.”

Shows the stock templates Fatture in Cloud offers, optionally grouped by type. No company ID is needed.

When to use it
you want to see the built-in layouts before choosing one for your documents.
Watch out
your own templates come from List Templates, not from this one.
8

List Emails

Search

In Zapier“List Emails.”

Returns the emails sent from the company, so a Zap can see what already went out.

When to use it
you want proof that a document actually went out before chasing a client for payment.
Watch out
it lists emails; it does not resend any.
9

List F24

Search

In Zapier“Lists the F24s.”

Finds the F24 payment forms recorded in the company.

When to use it
a Zap should locate the form tied to a payment before updating or attaching to it.
Watch out
it returns the forms themselves; their files are separate attachments.
10

List Issued Documents

Search

In Zapier“Lists the issued documents.”

Looks for outgoing documents of a given type in the company.

When to use it
a Zap must gather a client's delivery notes before Join Issued Documents merges them.
Watch out
the document type is mandatory, so one search covers one type.
11

List Payment Accounts

Search

In Zapier“Lists the available payment accounts.”

Returns the payment accounts available in the company.

When to use it
a document step needs the ID of the account the money should go into.
Watch out
each account carries a virtual flag, worth checking before you pick one.
12

List Payment Methods

Search

In Zapier“Lists the available payment methods.”

Finds the payment methods you have defined.

When to use it
a document created by a Zap should reuse an existing method instead of a new one.
Watch out
the default method is only one of the results; pick it on purpose.
13

List Pending Received Documents

Search

In Zapier“Lists the pending received documents.”

Searches the incoming documents still waiting to be booked in the company, for the type you choose.

When to use it
someone should review what is pending before it turns into real records.
Watch out
the type of pending document is required.
14

List Products

Search

In Zapier“Lists the products.”

Scans the catalogue for products and returns the ones that match.

When to use it
an order from your shop should be matched to existing products before a document is built.
Watch out
with no product found, the Zap stops unless you switch on the setting above.
15

List Receipts

Search

In Zapier“Lists the receipts.”

Returns the receipts recorded in the company, so a Zap can compare them with your sales.

When to use it
a sync with your till should spot receipts already present and skip them.
Watch out
the default keeps only the first match when several receipts fit.
16

List Received Documents

Search

In Zapier“Lists the received documents.”

Finds supplier documents of one given type among those booked in the company.

When to use it
you check whether a bill is already booked before Create Received Document adds it again.
Watch out
the document type is mandatory, so one search covers a single type.
17

List Suppliers

Search

In Zapier“Lists the suppliers.”

Searches the suppliers of the company and returns the matching records.

When to use it
a bill arrives and the Zap needs the supplier's ID to attach it to the right vendor.
Watch out
a supplier not found stops the Zap by default.
18

List Templates

Search

In Zapier“Gets all the standard and private templates.”

Brings back both the standard and the private document templates set up in the company.

When to use it
a document should be printed with a specific layout picked by name.
Watch out
the template ID it returns feeds Get Template.
19

List Vat Types

Search

In Zapier“Lists the available vat types.”

Retrieves the VAT types set up in the company.

When to use it
the right rate must be picked by ID before a product or a document is created.
Watch out
each VAT type carries a disabled flag; check it before you use the ID.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and skips the steps that depended on it. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. No search of Fatture in Cloud offers it, so creating a missing record is always a separate action.
  3. If multiple search results are found?
    Three ways out when several records match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When the Zap breaks

Zapier ties no help article to this app and no app-specific limit is documented. What breaks here are the general rules of Zapier, and they bite hard on an invoicing tool.

Before you look further, keep in mind that the triggers report what you asked for and nothing else: if a Zap never starts, check the resource type and the event types it listens to. The three cases below are the general limits that apply here. When one of them hits you, start from our Zapier troubleshooting page.

  • Old documents are never picked up

    A Zap only reacts to what happens after you publish it. Invoices issued last month will not run through it, and moving that backlog is a separate job.

  • The Zap sets itself off again

    If the Zap edits the very documents its trigger listens to, every change it makes is a new event. It loops and burns through your tasks fast.

  • A bulk import is held back

    After a mass import or a migration, a sudden flood of events can be held by Zapier's flood protection instead of running one by one.
Need help

Need help automating Fatture in Cloud with Zapier?

A person reads every message.

FAQ

Fatture in Cloud and Zapier: frequent questions

01Is the Fatture in Cloud Zapier integration free?
Yes, Fatture in Cloud is not a premium app, so you can connect it on the free Zapier plan. That plan gives you 100 tasks a month and as many Zaps as you like, but each Zap stops at two steps: one trigger and one action. Checking an e-invoice and then sending it already takes two actions, so that kind of flow needs a paid plan. The same goes for any filter or search step you add, because each one turns the Zap into a multi-step Zap.
02How many tasks does a Fatture in Cloud Zap use?
One task per action that completes, and nothing for the trigger. A Zap that receives an event, gets the document and schedules an email uses two tasks each time it runs. If an action fails, it is not counted against your plan. Watch the raw trigger: because it only passes IDs, you often need an extra read step, and that step is one more task on every run. Plan the volume before you publish.
03Does the integration work in real time?
Yes. Both triggers, Receive Enriched Event and Receive Raw Event, are instant: Fatture in Cloud tells Zapier the moment the event happens, and the Zap starts right away. The polling grid of the Zapier plans does not apply to them, so the free plan reacts as fast as Enterprise. In the editor, a Zap built on one of these triggers shows a lightning bolt, which is how you can tell the difference at a glance.
04What does connecting a Fatture in Cloud account require?
An account on Fatture in Cloud, and access to every company you want the Zap to touch if you are not its owner. In Zapier, open the Apps page, click + Add connection, search for the app, then sign in and grant access in the tab that opens. Keep the company ID close: almost every trigger, action and search asks for it, so the connected user must be able to reach that company.
05Why does an uploaded attachment not show on the invoice?
Because uploading and attaching are two separate moves. The four upload actions send the file to Fatture in Cloud and return a token, but they do not tie it to any document. A later step has to use that token to make the link, so map the token from the upload step into it. Until that second step runs, the file exists in Fatture in Cloud but no invoice, bill, archive paper or tax form shows it.
06What if the operation needed is missing?
Check the searches first, because several reads only exist there, such as the list of clients or of cashbook entries. If nothing fits, the two triggers can still listen to many resource types, and a search step plus an action often rebuilds what a single missing operation would do. When even that falls short, the gap is in the Zapier app itself. The Make page for the same app is another place to compare what each tool exposes.
07Zapier, Make or n8n for Fatture in Cloud?
It depends on your criteria rather than on a winner. On Zapier, this app works from its free plan, but every completed action is billed and multi-step Zaps need a paid plan. Compare Make and n8n on the same points: which operations they expose for Fatture in Cloud, how they count what you run, and who looks after the tool day to day. The right pick follows from those answers.
Same platform

Other docs you might need on this stack.

Browse all integrations