What can you do with the Green Invoice API?
Connecting Morning (Green Invoice) via API allows you to issue invoices, update clients, and sync data between systems without touching the interface. Instead of manually typing each invoice or copying data between sheets and your accounting system, you can build a process that receives an order from a form or CRM, checks that the details are complete, and sends a document issuance request directly to Morning.
We build automations that connect accounting systems like Morning to the rest of the business infrastructure - CRM, sheets, forms, and WhatsApp. The connection is made through Morning’s official API, which allows reading and writing of clients, items, invoices, and receipts. The process runs on a predetermined schedule or is triggered by an event - for example, when a deal reaches “closed” stage in the CRM, or when payment is received through an online payment method.
This kind of connection reduces typing errors, eliminates duplicate work, and allows you to track invoice status without switching between systems. Instead of sending a manual email with an invoice link, you can send an automatic WhatsApp message to the client with the exact link, or update a row in a sheet with the invoice number and issue date.
How do you connect Morning to the API?
Connecting Morning via API starts with issuing an API key from the account settings in the Morning system. This key is a unique string that identifies the account and allows access to the data. We store it in the n8n work environment or in a secrets management system, not in the code itself.
Once you have a key, you build a workflow in n8n that makes HTTP requests to the Morning system. Each request includes the key in the Authorization header, the type of action (GET, POST, PUT), and the relevant data in the request body. For example, to issue a new invoice, you send a POST to the /documents endpoint with client details, line item breakdown, and amount.
Morning returns a response in JSON format with the document number, download link, and issuance status. If there’s an error - for example, a missing detail or a client that doesn’t exist in the system - the response contains an error code and explanation. We build the workflow so it checks the response code before continuing, and sends an alert if something fails.
The connection itself doesn’t require a dedicated server. n8n runs on cloud or on an internal server, and makes the requests from its own environment. If the business already works with sheets or CRM, we add Morning as an additional step in the same process.
What happens when a new order arrives?
When a new order arrives - through a website form, WhatsApp message, or new row in a sheet - the workflow wakes up and begins processing the data. The first step is to check that all required fields exist: client name, email, service or product description, and amount. If something is missing, the workflow sends a message back to the orderer or updates the row in the sheet with a “waiting for details” status.
If everything is valid, the workflow checks whether the client already exists in Morning. It sends a GET request to the /clients endpoint with the client name or ID number. If the client exists, the workflow pulls their ID. If not, it creates a new client with a POST request to the same endpoint, and saves the returned ID.
After that, the workflow builds the invoice body: a list of lines with description, quantity, unit price, and VAT. It sends everything to Morning, receives back a download link and document number, and updates the original row in the sheet or CRM with these details. If needed, it also sends a WhatsApp message to the client with the link.
This process runs within minutes of receiving the order, and requires no manual intervention unless there’s an error that cannot be handled automatically.
How do you handle errors and edge cases?
Errors happen. A client forgets to enter an email, the Morning system is temporarily unavailable, or a field contains an illegal character. We build the workflow so it catches errors and handles them in a controlled manner.
Every API request is wrapped in a try-catch block. If the request fails, the workflow doesn’t crash - it moves to an error branch that logs the details, sends an alert to a dedicated Slack channel or email, and updates the original row with a “failed” status. If the error is temporary - for example, a timeout - the workflow tries again after a minute, up to three times.
If the problem is in the data itself - for example, a negative price or empty client name - the workflow sends a message back to the source and requests a correction. It doesn’t continue until the data is valid. This saves time and prevents incorrect invoices that need to be cancelled and reissued.
We also build a weekly report that summarizes how many invoices were issued, how many failed, and what the common failure reasons are. This helps identify recurring problems and fix them at the source.
What’s the difference between manual connection and full automation?
Manual connection means someone logs into Morning, types the invoice details, saves, and copies the link back to the client or sheet. It works, but it takes time and is open to errors. If there are dozens of invoices per month, this becomes a task that consumes hours.
Full automation means the process runs from start to finish without touch. Data flows from the source - form, CRM, sheet - through checks and validations, to Morning, and back to the original system with updated details. A person sees only the final result, and intervenes only when there’s an exception or error that requires a decision.
| Aspect | Manual Connection | Full Automation |
|---|---|---|
| Time to issue | 5-10 minutes per invoice | Less than a minute |
| Typing errors | Occur | Don’t occur if source data is valid |
| CRM or sheet update | Manual, sometimes forgotten | Automatic, always updated |
| Error handling | Discovered only when checking | Immediate alert |
Automation isn’t suitable for every business. If there are fewer than ten invoices per month and the process is simple, the savings may not justify the investment in building. But if there’s high volume, a complex process, or a need to sync with additional systems, automation pays for itself within months.
How long does it take to set this up?
Setting up a basic connection between one data source - for example, a sheet or form - and Morning typically takes one to two weeks. This includes setting up the key, building the workflow, testing on real data, and handling common errors.
If you need to connect multiple sources - CRM, forms, and WhatsApp - or build more complex logic - for example, partial invoices, credits, or differential VAT calculation - it can take three to four weeks. The process includes an opening meeting where we map the existing process, building and testing in a development environment, and then moving to production with support during the first two weeks.
We don’t launch automation all at once. The process starts with a pilot - for example, only one type of invoice or only new clients - and after it runs stably for a week or two, we expand to the rest of the volume. This reduces risk and allows fixing problems while they’re still small.
After launch, we monitor the process through alerts and reports. If something changes - for example, Morning changes the API structure or the business adds a new product type - we update the workflow accordingly. Most businesses we work with see full stability after a month.
What else can you connect to Morning?
Morning is one endpoint in the process. We build automations that connect it to additional systems to create a complete business process.
For example, you can connect Morning to a CRM so that every deal that moves to “closed” stage triggers automatic invoice issuance, then updates the client record in the CRM with the invoice number and issue date. You can also connect to an online payment system - when payment is received, the workflow checks if there’s an open invoice, issues a receipt in Morning, and sends the client a WhatsApp message with the receipt.
You can also connect to sheets for reporting purposes. Every issued invoice adds a row to a summary sheet with date, client, amount, and status. At the end of the month, you can build an automatic report that summarizes revenue by client, by service type, or by month, and sends it to email or Power BI.
These kinds of connections are built on the same principle: data flows between systems through APIs, with checks and validations at each stage, and with alerts when something requires attention. We plan the flow together with the business, so it reflects the actual process and doesn’t force a new one.
You can read more about how we build connections between systems on the integrations page, and see another example of business automation in the post about invoice issuing for businesses.
Frequently asked questions
Does API connection to Morning require a dedicated server?
No. The connection runs on an automation platform like n8n, which can run on cloud or on an internal server. There's no need for a dedicated server just for the Morning connection. We build the workflow on the business's existing infrastructure or on a managed environment we provide.
What happens if Morning changes the API?
When Morning changes the API, we receive advance notice and update the workflow accordingly. Most changes are additions - new fields or new endpoints - and don't break the existing connection. If there's a change that requires adaptation, we test it in a development environment before moving to production. The business doesn't feel the change.
Can you also issue credits and receipts through the API?
Yes. Morning's API supports issuing invoices, tax invoices, credits, and receipts. We build the workflow so it knows which document type to issue according to the event - for example, a credit when cancelling a deal, and a receipt when payment is received. The logic is determined by the specific business process.
How much does it cost to set up this kind of connection?
The cost depends on the process complexity and the number of systems that need to be connected. A basic connection between one data source and Morning starts at a few thousand shekels. A more complex process with multiple sources, custom logic, and connection to CRM or additional systems can reach tens of thousands of shekels. We build a quote after a mapping meeting, when we understand exactly what's needed.