Moon Invoice

Moon Invoice is an invoicing and billing platform for small businesses. Agents issue invoices, sales receipts, proforma invoices, estimates, delivery challans, and credit notes, and manage purchase orders, bills, and expenses on the other side.

Verified 111 actions API key available

Moon Invoice website Platform Documentation Capability data verified 2026-08-24

A project milestone is marked complete in the delivery tool

Get Time Log returns the time recorded against that project's tasks

Get Service resolves each billable line to a catalog rate rather than a typed one

The assembled total is compared against the estimate the client accepted

Create Invoice raises the document against the client's contact record

The invoice and the time detail behind it post to the account lead

The account lead reconciles the hours against the engagement and decides what gets written down

What This Integration Enables

Moon Invoice is small business invoicing and billing software, and its API makes one structural choice that decides how you automate it. Nine document types, meaning invoices, sales receipts, proforma invoices, estimates, delivery challans, credit notes, purchase orders, bills, and debit notes, are separate objects with the same four operations each. They are not statuses of a single document. That is why the surface is as wide as it is, and it is also why an agent can be precise here: raising a proforma is a different act from raising an invoice, and the API does not blur them.

The other half of the connector is the work behind the billing. Projects, tasks, and time logs live in the same system as the documents they eventually become, alongside products, services, taxes, payment methods, and sales people. Both sides of the ledger are modeled: payments received against invoices, and payments made against bills. FlowRunner agents can assemble an entire engagement's billing from the record of the work rather than from someone's recollection of it, which is the case this integration is genuinely good at. Recurring billing, worth knowing, is a flag on the invoice with an interval and an end date rather than a separate object, so a repeating charge is an invoice that says it repeats.

Without FlowRunner

Billing rebuilt from memory Hours, expenses, and scope changes are reassembled at month end from three places

Document types conflated Estimates, proformas, and delivery challans are treated as stages of an invoice rather than records in their own right

Deletions with no safety net A cleanup pass removes the wrong record and there is nothing to undo it with

With FlowRunner

Billing assembled as the work happens Time logs, tasks, and expenses accumulate against the project they belong to

Each document type kept as itself The estimate, the proforma, the challan, and the invoice are separate records with their own history

Deletions treated as one way Destructive passes present what they matched and how many rows before anything is removed

Use Case Scenarios

Milestone to invoice, built from the record of the work

Delivery runs in ClickUp and a milestone closes. The agent reads the project's tasks and calls Get Time Log for the hours booked against them, resolving each billable line through Get Service so the rate comes from the catalog rather than from whatever a template had in it. It compares the assembled total against the estimate the client accepted, then calls Create Invoice against the client's contact record. What it does not do is decide the write down. Hours that overran the estimate are presented to the account lead with the tasks that produced them, because the decision to bill a client for a scope overrun is a client relationship decision, not an arithmetic one.
Both sides of the ledger, kept in step

Purchases start as a purchase order, become a bill when the supplier invoices, and close with a payment made. The agent creates each in turn, attaching the supplier's reference so the chain is readable later, and records expenses that never had a purchase order behind them. On the sales side, payments settling through Stripe are recorded with Create Payment against the invoice they clear. Because Moon Invoice models a debit note as its own document type rather than as a negative bill, a supplier dispute produces a debit note that stays attached to the bill it corrects instead of quietly altering it.
A catalog that stops drifting

Product and service records carry the prices every document line inherits, and they drift. An agent audits them on a schedule: it reads the full product and service lists, compares each rate against what has actually been billed on recent invoices, and reports every record where the two disagree. It also reads the tax list and flags any document type still referencing a rate that has since changed. The findings post into Slack as a short list with the affected records named. Nothing is rewritten automatically, because a price that looks stale is sometimes a negotiated rate somebody agreed to on purpose.

Human-in-Loop Highlight

Moon Invoice has a delete on almost everything: invoices, credit notes, payments, bills, expenses, projects, time logs, products, taxes, contacts, and companies all have one. It has exactly one restore, and that restore is for a sales person. Nothing brings back a deleted invoice or a deleted payment. Delete Company is the sharpest edge of that, because almost every route in this API is scoped to a company identifier, and the connection usually carries one as its default. Deleting the company a flow is scoped to is not a record removal, it is the removal of the container everything else addresses. The API compounds this by reporting a delete as a message naming a count, so a call that matched more rows than intended still reports success, in a cheerful sentence, with the larger number in it.

So the gate is on any destructive pass, and it is built from the count rather than the intent. The agent reads what it is about to remove, states the number, and stops: "This cleanup removes 1 company record and would orphan 214 invoices, 61 bills, and 38 projects scoped to it. There is no restore operation for any of them. Proceed, or narrow the match?" A person answers. Deleting a single stale draft that the agent read back and can quote runs unattended, because a gate that fires on every tidy up is a gate nobody reads. The one that fires on a delete whose blast radius the agent had to count is the one worth stopping for.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

111 actions

Companies and Contacts

Get Company Lists the companies this login holds. One login can carry several businesses, and this is the route that does not need a company identifier, so it is where the identifiers come from.
Create Company Creates a company in the account.
Update Company Updates a company's details.
Get Company Details Reads one company in full.
Delete Company Deletes a company. Nearly every other route is scoped to a company identifier, so this is the widest destructive operation on the connector and the one this page's human gate exists for.
Get Contact Lists the contacts of a company, with the sort, page size, and status filters travelling in the request body.
Create Contact Creates a contact, with its billing and secondary addresses as nested blocks.
Update Contact Updates a contact's details.
Get Contact Details Reads one contact in full.
Delete Contact Deletes a contact. The answer names how many records were removed.

Invoices and Sales Receipts

Get Invoice Lists invoices, filtered, sorted, and paged by the invoice specific parameters.
Create Invoice Creates an invoice with its line items, taxes, and payment terms. Setting the recurring flag with an interval and an end date is what turns it into a repeating invoice, since recurring billing is a property of the invoice rather than a separate object.
Update Invoice Updates an invoice.
Get Invoice Details Reads one invoice in full, including its lines and totals.
Delete Invoice Deletes an invoice. There is no restore for one.
Get Sales Receipt Lists sales receipts, which record a sale already paid at the point of sale.
Create Sales Receipt Creates a sales receipt with its lines.
Update Sales Receipt Updates a sales receipt.
Get Sales Receipt Details Reads one sales receipt in full.
Delete Sales Receipt Deletes a sales receipt.

Proforma Invoices and Estimates

Get Proforma Invoice Lists proforma invoices, which commit to a price without being the bill.
Create Proforma Invoice Creates a proforma invoice with its lines.
Update Proforma Invoice Updates a proforma invoice.
Get Proforma Invoice Details Reads one proforma invoice in full.
Delete Proforma Invoice Deletes a proforma invoice.
Get Estimate Lists estimates, which are the quoted scope a client accepts before work starts.
Create Estimate Creates an estimate with its lines.
Update Estimate Updates an estimate.
Get Estimate Details Reads one estimate in full, which is what a later invoice is checked against.
Delete Estimate Deletes an estimate.

Delivery Challans and Credit Notes

Get Delivery Challan Lists delivery challans, the goods dispatch documents that travel with a shipment.
Create Delivery Challan Creates a delivery challan with its lines.
Update Delivery Challan Updates a delivery challan.
Get Delivery Challan Details Reads one delivery challan in full.
Delete Delivery Challan Deletes a delivery challan.
Get Credit Note Lists credit notes, which are how an issued invoice is corrected on the sales side.
Create Credit Note Creates a credit note against a customer with its lines.
Update Credit Note Updates a credit note.
Get Credit Note Details Reads one credit note in full.
Delete Credit Note Deletes a credit note.

Payments Received

Get Payment Lists the payments received, filtered and paged.
Create Payment Records a payment received against an invoice.
Update Payment Updates a recorded payment.
Get Payment Details Reads one payment in full.
Delete Payment Deletes a payment, which reopens what it settled. There is no restore for one.

Purchase Orders and Bills

Get Purchase Order Lists purchase orders, the commitments made to suppliers before a bill arrives.
Create Purchase Order Creates a purchase order with its lines.
Update Purchase Order Updates a purchase order.
Get Purchase Order Details Reads one purchase order in full.
Delete Purchase Order Deletes a purchase order.
Get Bill Lists bills, which are the supplier invoices owed.
Create Bill Creates a bill with its lines, normally against the purchase order it fulfills.
Update Bill Updates a bill.
Get Bill Details Reads one bill in full.
Delete Bill Deletes a bill.

Debit Notes and Payments Made

Get Debit Note Lists debit notes, which are how a supplier bill is corrected on the purchase side.
Create Debit Note Creates a debit note against a supplier with its lines.
Update Debit Note Updates a debit note.
Get Debit Note Details Reads one debit note in full.
Delete Debit Note Deletes a debit note.
Get Payment Made Lists the payments made to suppliers.
Create Payment Made Records a payment made against a bill.
Update Payment Made Updates a recorded supplier payment.
Get Payment Made Details Reads one supplier payment in full.
Delete Payment Made Deletes a supplier payment, which reopens the bill it settled.

Expenses

Get Expense Lists expenses, which are the costs with no purchase order behind them.
Create Expense Records an expense against a category and a payment method.
Update Expense Updates a recorded expense.
Get Expense Details Reads one expense in full.
Delete Expense Deletes an expense.

Products and Services

Get Product Lists the products, which carry the price a document line inherits.
Create Product Creates a product with its price and tax settings.
Update Product Updates a product.
Get Product Details Reads one product in full.
Delete Product Deletes a product from the catalog.
Get Service Lists the services, which are the billable rates a time based line resolves to.
Create Service Creates a service with its rate and tax settings.
Update Service Updates a service.
Get Service Details Reads one service in full.
Delete Service Deletes a service from the catalog.

Projects, Tasks and Time Logs

Get Project Lists the projects, which are what tasks and time logs are attributed to.
Create Project Creates a project against a client.
Update Project Updates a project.
Get Project Details Reads one project in full.
Delete Project Deletes a project, along with the attribution its tasks and time logs depended on.
Get Task Lists the tasks, which are the units work is booked against.
Create Task Creates a task within a project.
Update Task Updates a task.
Get Task Details Reads one task in full.
Delete Task Deletes a task from a project.
Get Time Log Lists the time logs, which is where the hours behind a billable line come from.
Create Time Log Records time against a task or a project.
Update Time Log Updates a recorded time log.
Get Time Log Details Reads one time log in full.
Delete Time Log Deletes a time log, which removes the evidence behind an hour that may already have been billed.

Taxes and Payment Methods

Get Tax Lists the taxes configured for the company.
Get All Tax List Reads the full tax list, which is where a document line's rate is chosen from.
Create Tax Creates a tax rate.
Update Tax Updates a tax rate. Documents already issued keep the figures they were written with.
Get Tax Details Reads one tax rate in full.
Delete Tax Deletes a tax rate.
Get Payment Method Lists the payment methods configured for the company.
Create Payment Mehotd Creates a payment method. The operation name carries the vendor's own spelling, which is reproduced here rather than corrected so that it matches what the platform shows.
Update Payment Method Updates a payment method.
Delete Payment Method Deletes a payment method.

Sales People

Get Sales Person Lists the sales people, who documents can be attributed to for commission and reporting.
Create Sales Person Creates a sales person record.
Update Sales Person Updates a sales person record.
Get Sales Person Details Reads one sales person in full.
Delete Sales Person Deletes a sales person record.
Restore Sales Person Restores a deleted sales person. The only restore operation on this connector, which is worth remembering before any other delete runs.

Frequently Asked Questions

What can FlowRunner do with Moon Invoice?

FlowRunner agents can run Get Company, Create Company, and Update Company in Moon Invoice, plus 108 more actions.

Does connecting Moon Invoice to FlowRunner require OAuth?

No. Moon Invoice connects to FlowRunner with an API key, no OAuth flow required.

Can Moon Invoice trigger a FlowRunner workflow automatically?

Moon Invoice doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Moon Invoice

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us