Invio's REST API can create draft invoices, quotes and clients from your online store, booking system or CRM. Here is what is ready-made, what a developer builds, and which plan includes it.
Every business has events that trigger invoicing.
A customer places an order. Someone books a service. A new client submits a website form.
These events often lead to the same manual tasks:
- Collecting customer details.
- Transferring order or service information.
- Creating a quote or invoice.
- Updating customer records.
Invoice automation connects these activities to your invoicing software.
With the Invio REST API, businesses can build workflows that turn business events into invoicing actions.
Instead of repeatedly entering the same information, you can connect Invio with the systems you already use.
What is ready-made, and what is not
Invio has no ready-made Shopify, WooCommerce, Make or n8n app. There is nothing to install from an app store and no one-click connection. A developer connects those systems to Invio through the REST API. An owner who already uses Make or n8n can call the same API from a generic HTTP step in a workflow. Invio does not have a Make or n8n module to add.
The REST API is included on paid plans only, not on Starter, the free plan. Pro is NZ$19 a month in New Zealand and A$19 in Australia. Growth is NZ$59 and A$59. Care, sold in Australia, is A$79 a month and includes 3 workers.
The endpoints, examples and limits are in the REST API guide.
Drafts first, and sending needs an explicit switch
The API creates drafts. Creating an invoice, quote, client or expense never emails anyone.
Sending an invoice is a separate call, and Invio sends it to the client only when all of these are true:
- The key has Can send switched on. The account owner switches it on for each key in Settings > AI connections. It is off by default, so a new key can draft but cannot send.
- The request includes
confirm: true. That is a field in the request, so the Can send switch is the real limit: only keys the owner has switched on can send at all. - The invoice passes the same checks as a send from the app: bank details, a verified email address, the client's email address and the free-plan invoice limit.
When Can send is off, the call returns a 403 with the code sending_off_for_key, and nothing is sent. Every send is written to the account's audit log together with the key that made it. Quotes cannot be sent through the API at all. An invoice set to repeat also needs startsRecurringSeries: true when the send would start the series.
The workflows below create drafts. Whether a key may send at all is the owner's decision.
1. Automate invoicing for Shopify and WooCommerce stores
Online retailers use platforms such as Shopify and WooCommerce to manage their orders.
Each order contains information that may be needed for invoicing.
This can include customer details, purchased products, order value and relevant tax information.
An API integration can transfer this information into an invoicing workflow.
Example: order-to-invoice automation
Consider an online store processing dozens of orders each day.
A typical workflow could look like this:
- A customer places an order.
- The integration retrieves the order information.
- The integration creates the customer in Invio. If a client with that name already exists, Invio returns that client instead of creating a duplicate. A new customer needs an email address.
- The integration creates a draft invoice from the order details. Invio works out the GST from your settings, so the store does not send tax amounts.
- Someone at the business reviews the draft and approves it. Only then is it sent.
The workflow can follow your business rules.
For example, you may choose to create drafts only after an order reaches a particular status.
This reduces manual data entry and helps your team process orders more efficiently.
2. Connect booking systems to invoicing
Service businesses often receive bookings through online booking platforms.
Each booking can contain information about the customer, service and agreed price.
This information can become the starting point for an invoicing workflow.
Example: booking-to-invoice automation
A customer books a service through an online booking system.
The integration retrieves the booking details and uses them to create a draft invoice in Invio.
Depending on your business process, the draft could be created:
- When the booking is confirmed.
- After the service is delivered.
- When the booking reaches a specific status.
This approach can reduce the time spent transferring booking information into your invoicing system.
It can also feed the same figures into your reporting, as section 5 explains.
3. Automate invoicing with Make and n8n
You do not always need a developer to build an integration from scratch.
Workflow automation platforms such as Make and n8n allow businesses to connect applications and automate repetitive processes.
Invio's REST API can be called from these workflows through a generic HTTP step. There is no Invio app to add, so the workflow sends the request itself.
Example: website enquiry to quote
Imagine a service business receiving enquiries through a website form.
The manual process might involve reviewing the enquiry, creating a customer record and preparing a quote.
A workflow can automate the repetitive steps.
Example workflow:
Website form → Make or n8n → Invio customer record → Invio draft quote
When a new enquiry arrives, the workflow captures the information and creates the customer record and a draft quote in Invio.
The business can then review the quote, send it to the client from Invio (the API cannot send quotes), and continue its normal sales process.
Example: CRM to Invio
A business may already use a CRM to manage customers.
When a new customer is created in the CRM, an integration can create the corresponding customer record in Invio. Invio needs an email address for a new customer, so the CRM record has to include one.
This helps keep information aligned between systems.
It also reduces duplicate data entry.
| Business event | Potential automated action |
|---|---|
| New CRM customer | Create a customer record in Invio |
| Website enquiry | Create a customer record or draft quote |
| E-commerce order | Create a draft invoice |
| Booking completed | Start an invoicing workflow |
The exact workflow depends on the operations the Invio REST API offers, which the REST API guide lists.
4. Build integrations using the Invio API
IT freelancers, developers and small digital agencies often help businesses connect their software systems.
Many clients use separate applications for sales, customer management, bookings and accounting.
These applications may work well individually but require manual effort to keep information aligned.
The Invio API provides an opportunity to connect invoicing with existing business workflows.
What can developers and agencies build?
Depending on the client's requirements, an integration could involve:
- Connecting a website or online store to Invio.
- Automating customer creation from a CRM.
- Generating quotes from website enquiries, as drafts.
- Creating draft invoices from completed orders.
- Retrieving invoicing data for reporting.
- Integrating Invio into an existing Make or n8n workflow.
For freelancers and small agencies, these integrations can become repeatable solutions for multiple clients. Each client business needs its own API key, because a key works for one business only.
Rather than building an entire invoicing system, developers can use Invio as the invoicing component of a wider business automation solution.
5. Retrieve invoicing data for accounting and reporting
Invoice automation is not limited to creating invoices.
Accountants, bookkeepers and virtual assistants may manage several businesses simultaneously.
Each business can have its own customers, invoicing records and reporting requirements.
Collecting information from multiple systems manually can be time-consuming.
An API integration can help automate the retrieval of invoicing data.
Example: multi-business reporting
Imagine an accountant supporting several small businesses.
Instead of manually collecting invoicing information from each business, an integration can retrieve the data from each business with that business's own API key.
The results can then be combined in a central reporting workflow. Possible applications include:
- Consolidated invoice reporting.
- Business-specific revenue summaries.
- Custom financial dashboards.
- Automated management reports.
- Data collection for accounting workflows.
A key reads one business only, and no single request reaches another business. A consolidated report is therefore built by your script, which calls each business with its own key and combines the results. A list call returns at most 20 rows, newest first, so a script reads a long period one date window at a time. A business can hold up to 10 live keys, and only the account owner can create them.
This can help accounting professionals spend less time collecting data and more time analysing it.
Why use an API for invoice automation?
An API allows different software applications to communicate with one another.
For businesses, this means invoicing can become part of a wider operational workflow.
Reduce manual data entry
Customer, order and service information can move between connected applications without repeatedly entering the same details.
Keep information consistent
Automated workflows can reduce discrepancies caused by manually copying information between systems.
Support business growth
A workflow can often be adapted to handle larger transaction volumes, subject to the capabilities and limits of the connected applications. Each API key can make 600 requests an hour.
Build flexible workflows
Businesses can design processes around their own operations rather than relying entirely on a fixed invoicing workflow.
Make better use of existing software
Instead of replacing every application, businesses can connect their existing systems and use each application for the tasks it handles best.
How to get started with Invio API automation
The first step is to identify a repetitive business process that involves invoicing.
Ask yourself:
- Which event triggers the need for an invoice or quote?
- Where is the customer information stored?
- Which application contains the order or service details?
- Which steps are performed manually?
- What should happen automatically?
- Which steps require human approval?
Once the workflow is defined, identify the relevant API operations and configure the integration. Turn Can send on only for a key that really needs to send, and test with drafts first.
Businesses using Make or n8n can build visual workflows.
Developers can use the Invio API to build more customised integrations.
The most effective starting point is usually one repetitive process.
Automate it, test it and measure the results before expanding to additional workflows.
Automate your invoicing workflows with Invio
Whether you operate an online store, manage a service business, build integrations for clients or prepare reports for multiple businesses, invoice automation can reduce repetitive administrative work.
Invio provides an API that can be incorporated into business automation workflows.
Connect invoicing with the systems you already use.
Make invoicing part of your business process.
Read the REST API guide for the endpoints, or compare plans to see which one includes the API.