- Home
- Resources
- Integrations
- Invoicing.plus
Invoicing.plus Zapier integrationAutomate Invoicing.plus with Zapier.
Invoicing.plus Zapier integration: 2 triggers, 3 actions and 1 search to plug this French invoicing tool into the rest of your work. What each one does, what it costs in tasks, and where it tends to break before you go live.
Verified Trustpilot reviews · AI, automation & growth agency
What the Invoicing.plus Zapier integration actually does
It links your Invoicing.plus account to your other apps through Zapier, without code. A Zap (the automation you build on Zapier) watches for validated invoices or new payments, then creates customers, creates invoices or fetches a PDF for you. Six operations in total, and the whole page is about those six, nothing more.
Three results come up again and again. A PDF archive that fills itself: New Invoice starts the Zap, PDF Invoice fetches the file, and a storage app files it where your accountant looks. A payment alert: New Payment starts the Zap and a message or a spreadsheet row tells the team the money is in. A billing hand-off from sales: Find Customer checks an email address, Create Customer adds whoever is missing, then Create Invoice bills them, as long as the item already sits in your account.
What Zapier does not do here matters just as much. Neither trigger is instant, so nothing reaches Zapier the second it happens in Invoicing.plus. No action updates or deletes an invoice, none records a payment, and no step creates the items that Create Invoice asks for. If one of those gaps is a deal-breaker, our Zapier review and the Make vs Zapier comparison show how the platforms differ on coverage and pricing logic.
Zapier vocabulary, in one minute
Eight words you will meet in the editor. Each one is used on this page exactly as defined here.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts a Zap. With this app, it is a newly validated invoice or a newly recorded payment in Invoicing.plus.
- Action
- What the Zap does once started: the step that creates a customer or an invoice, or fetches a PDF, on your behalf.
- Task
- The unit Zapier bills. One action that completes successfully is one task, and your plan is a monthly count of those.
- Polling vs instant
- Polling: Zapier asks the app for new items on a timer. Instant: the app calls Zapier itself. Both Invoicing.plus triggers poll.
- Filter
- A step that lets the Zap go on only when what arrived meets a condition you set, and stops it otherwise.
- Search step
- A step that looks up something that already exists in an app, like a customer by email, so later steps can reuse it.
- Connection
- Your Invoicing.plus account linked to Zapier once, then reused by every step of every Zap that touches the app.
What an Invoicing.plus Zap really costs
Invoicing.plus is not a premium app, so it runs on Zapier's free plan. The trigger never costs a task, however often Zapier checks. Only a successful action is billed.
- Trigger check0 tasks
- Each successful action1 task
- Free plan100 tasks a month, two steps per Zap
- Premium appNo, works on Free
The free plan gives 100 tasks a month, unlimited Zaps, and two-step Zaps only: one trigger, one action. Add a filter, a Find Customer step or a second action and you have a multi-step Zap, which needs a paid plan. In practice, New Invoice plus PDF Invoice fits on Free, but filing that PDF in a folder does not. Every action that succeeds counts on its own, so a Zap with two actions burns tasks twice as fast. An action that fails is not counted.
Connect Invoicing.plus to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need an Invoicing.plus account first, plus read or write access to anything you do not own but want the Zap to touch.
- 02
Pick Invoicing.plus
Type Invoicing.plus in the search box of the dialog, select it, then click Add connection. A new tab opens on the Invoicing.plus side, where the rest happens.
- 03
Sign in and grant access
Log in to Invoicing.plus in that tab and allow Zapier to reach the account. The connection then appears in your list, and every Invoicing.plus step of every Zap reuses it.
Your first Zap: every validated invoice saved as a PDF
GoalEach invoice you validate in Invoicing.plus lands as a PDF file in a Google Drive folder.
- 01
Start the build
Create a new Zap. Building means picking the app and event that start it, then the app and action that follow, then mapping fields between them.
- 02
Set the trigger
Choose Invoicing.plus as the app, New Invoice as the event, then the connection you added earlier. No other setting is needed at this stage.
- 03
Test it on a real invoice
Run the test: Zapier brings back the three most recent invoices of your account. Pick one you recognise, since it feeds the mapping of every step below.
- 04
Fetch the PDF
Add PDF Invoice as the first action and map the invoice ID from the trigger into its required field. Test it and check that a file comes back.
- 05
File it in Drive
Add Google Drive with Upload File and map the PDF from the previous step. This third step makes it a multi-step Zap, so a paid plan is required.
- 06
Publish
Once each step has returned what you expected, click Publish to switch the Zap on. Only invoices validated from that moment are picked up.
Invoicing.plus triggers: what starts a Zap
2 events start a Zap when something happens in Invoicing.plus. Zapier checks for them at the interval your plan allows.
New Invoice
Polling triggerIn Zapier“Triggers when a new invoice is validated.”
Starts your Zap each time an invoice reaches the validated stage in Invoicing.plus. That moment, rather than the first keystroke on a new document, is what Zapier watches, and the invoice then travels down the Zap so later steps can reuse it.
New Payment
Polling triggerIn Zapier“Triggers when a new payment is filled.”
Wakes the Zap when a payment is recorded in your Invoicing.plus account, which makes it the natural starting point for anything that should follow money coming in: a thank-you, an alert, a line in a cash sheet.
Invoicing.plus actions: what the Zap can do
Invoicing.plus gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Customer
ActionIn Zapier“Create a customer in the system”
Adds a new customer record to Invoicing.plus from data another app hands over. Only the Name is mandatory, so even a short form entry is enough.
Create Invoice
ActionIn Zapier“Creates a Invoice in the system”
Builds an invoice in your account from inside a Zap. It insists on two identifiers, a Customer ID and an Item ID, both pointing to records that already exist.
PDF Invoice
ActionIn Zapier“Get invoice pdf file”
Retrieves the PDF file of an existing invoice from its invoice ID, so a later step can store or send the document itself.
Invoicing.plus search: finding a customer
1 search step looks for data that already exists in Invoicing.plus, so a later step can use it.
Searches sit at the bottom of the action-event list, under the SEARCH heading. Some action fields also offer + Add search step, which inserts the lookup just before and wires its result in for you.
Find Customer
SearchIn Zapier“Finds customer by Email”
Looks up a customer already stored in Invoicing.plus from an email address, the one field it requires, and hands the record to the steps that follow.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nobody stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. Invoicing.plus offers no such variant, so you will not see it on Find Customer: a missing customer needs your own Create Customer step.
- If multiple search results are found?Three ways out when several customers match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When an Invoicing.plus Zap breaks
Zapier links no help article to this app, so the known failure points are the ones every Zap shares. Here is how each one shows up with invoices and payments.
Most problems below are about timing and loops, not about the connection. If a Zap still misbehaves after these checks, the Zapier troubleshooting page goes through the general method.
Old invoices are never picked up
A Zap only reacts to what happens after you switch it on. Invoices validated last month stay where they are, and moving that backlog is a separate job.A Zap that sets itself off
A Zap that writes into the very place its trigger watches starts itself again and again. New Invoice followed by Create Invoice is the pairing to watch here.A bulk import held back
Load a big batch of invoices or payments at once, after a migration for instance, and Zapier's flood protection can hold the trigger back.No second run for the same payment
Zapier remembers what a polling trigger has already seen, so the same invoice or payment never starts the Zap twice. If you expected a rerun, that is why.Find Customer comes back empty
With the default setting, a search that finds no customer stops the Zap and Create Invoice is skipped. Switch the setting on only if the next steps can cope.A failed action costs nothing
When Create Invoice is rejected, say for a missing Item ID, the task is not counted. Fix the mapping before the next invoice comes through.
Need help automating Invoicing.plus with Zapier?
A person reads every message.



