Abby

Abby is the French invoicing and bookkeeping app for sole traders and micro-entrepreneurs. Agents manage business and individual clients, the product catalog, invoices, estimates, and credit notes, and keep the accounting registers current from inside a workflow.

50 actions API key available

Abby website Platform Documentation Capability data verified 2026-08-24

A proposal is accepted upstream and the agreed lines arrive with it

Create Invoice opens an empty draft against the client and returns its id

Update Document Lines writes the complete line set, then Update Invoice Timeline sets the issue date and payment terms

List Documents re-reads the draft and pulls back the stored line amounts

The agent converts those amounts out of cents and compares them line by line against the accepted proposal

The VAT code and the tax inclusive flag are checked against the client's record

The operator approves the draft, and only then does Finalize Document assign the legal number

What This Integration Enables

Abby is built for the French sole trader and the micro-entrepreneur, which means the interesting part of this connector is not the invoice. It is the pair of accounting registers French law requires you to keep. Create Income Book Entry and Create Purchase Register Entry write directly into them, so the register stops being a quarterly reconstruction from bank statements and becomes a side effect of the money moving. FlowRunner agents also manage business and individual clients, keep the product catalog current, and run the estimate to deposit to final invoice chain end to end.

Abby builds a document in four calls rather than one, and that shape is worth understanding before you automate it. Create Invoice returns an empty draft, Update Document Lines writes the line set as a full replacement, the timeline call sets the dates, and Finalize Document assigns the legal number. Every amount on a document line travels in cents, so 1500 is fifteen euros. A flow that sends 15 produces a valid invoice for fifteen cents and no error anywhere. That is precisely the class of failure FlowRunner's human-in-the-loop design exists for: the agent does the assembly, and a person confirms the numbers before the document becomes permanent.

Without FlowRunner

Retyping the agreed price The proposal is agreed in one place and typed again into the invoice, where a decimal point has nothing checking it

Drafts that never became documents Half built invoices sit unfinalized with no number, invisible to the accountant and to the ledger

Registers filled in at the deadline The income book and the purchase register get reconstructed from bank statements once a quarter

With FlowRunner

The price travels with the agreement The agent carries the agreed lines from the source record into the draft and reads them back before anyone signs off

Nothing sits half built The draft either passes its checks and gets finalized, or it becomes a flagged exception a person sees

Registers stay current Payouts and supplier invoices are filed into the registers as they happen rather than rebuilt at quarter end

Use Case Scenarios

Proposal to deposit to final invoice

An accepted proposal lands from HubSpot or a signed thread in Gmail. The agent resolves the client, choosing between an organization and a contact because Abby accepts either in the same identifier slot, then calls Create Estimate and Update Document Lines to build the quote. Update Estimate Advance Lines sets the deposit schedule. When the client signs, Sign Estimate records it and Create Advance From Estimate raises the deposit invoice. On delivery, the balance invoice follows the same four call sequence. Nobody retypes a line, and the deposit percentage is set once rather than recalculated per project.
The purchase register keeps itself

Supplier invoices arrive by email or land as receipts in Dext. The agent reads each one, classifies it into an expense account, and calls Create Purchase Register Entry with the amount in ordinary currency units, because the registers are the one place in this API that does not use cents. Anything it cannot classify with confidence goes to a person as a flagged item rather than into a default account. The register that a French accountant will ask for is complete on the day it is asked for, and the entries that needed judgment were judged.
Payments reconciled against the invoice that earned them

A payout from Stripe or a credit on a Qonto account reaches the agent. It finds the invoice through List Documents filtered on the payment date range, then calls Mark Invoice As Paid carrying the provider's own reference in the payment's transaction id. That reference is what makes a retried provider webhook safe, because the agent can see the payment is already recorded. Mark Invoice As Paid takes the invoice's whole payment list, so a second instalment resends the first one too, and the agent builds the complete list rather than appending blindly. A digest of what settled posts to Slack.

Human-in-Loop Highlight

Finalize Document is the one way door on this connector. It assigns the legal number, and from that moment French numbering rules forbid editing or deleting the invoice: the only lawful correction is Create Credit Note From Invoice, which is a second document your client also receives. So the agent assembles the draft and then stops. It posts what it built: "Draft invoice for Atelier Ricard, 3 lines, total 4,180.00 EUR. Source proposal says 4,180.00. VAT code FR_2000. The line set was replaced in full and matches the proposal line for line. Finalize and assign a number?" The operator answers in the channel they already use. What earns the pause is not that finalizing is risky in general. It is that a cents error and a dropped line both produce a perfectly valid document, and after the number is assigned the only route back is a credit note with the customer's name on it.

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

50 actions

Organizations (business clients)

List Organizations Lists the business clients on the account with paging and search. The lookup behind matching an incoming order to an existing customer.
Create Organization Creates a business client record. Used when a new company reaches the workflow from a CRM or a storefront.
Update Organization Updates a business client. Abby requires the name on every update even when it is unchanged, so the agent reads the record before writing.
Delete Organization Deletes a business client record.
List Organization Contacts Lists the people attached to a business client. These are distinct from individual clients and are not billable in their own right.
Create Organization Contact Adds a person to a business client, which is how an invoice reaches a named recipient rather than a generic mailbox.
Update Organization Contact Updates a person attached to a business client.
Set Default Organization Contact Marks which contact is the default for the organization, and therefore who correspondence goes to.

Contacts (individual clients)

List Contacts Lists individual clients. Used when the payer is a private person rather than a company.
Get Contact Retrieves a single individual client by id.
Create Contact Creates an individual client record.
Update Contact Updates an individual client. First name and last name are required on update even when neither is changing.
Delete Contact Deletes an individual client record.

Documents

List Documents Lists invoices, estimates and credit notes together, filtered by type, search term and date range. This is the read path for an invoice, because Abby publishes no read by id for one.
Update Document Lines Writes the line set on a draft. It replaces the entire document, so adding one line means resending every line already there.
Finalize Document Assigns the legal number and locks the document. The step this page's human gate exists for.
Download Document PDF Fetches the rendered PDF for archiving or for attaching to a message.
Send Document By Email Emails a finalized document to the client with your own wording.

Invoices

Create Invoice Opens an empty invoice draft against a client and returns its id. The first of the four calls that make a document.
Update Invoice General Information Sets the invoice's title, wording and other header fields on the draft.
Update Invoice Timeline Sets the issue date and payment delay. Both are required on the call even when only one is changing.
Mark Invoice As Paid Records the invoice's payments. It takes the whole payment list, so partial settlement means resending the earlier instalments alongside the new one.
Mark Invoice As Unpaid Clears the recorded payments and returns the invoice to unpaid.

Estimates and purchase orders

Create Estimate Opens an empty estimate draft against a client.
Update Estimate General Information Sets the estimate's header fields and wording.
Update Estimate Timeline Sets the issue date, expiry date and payment delay on an estimate.
Update Estimate Language Sets the language the estimate is rendered in.
Update Estimate Currency Sets the estimate's currency.
Update Estimate Advance Lines Sets the deposit schedule on an estimate. Like the line set, it is a full replacement.
Sign Estimate Records the client's acceptance. The manual equivalent of Abby's online signature, and reversible.
Unsign Estimate Reverses a recorded signature.
Refuse Estimate Records that the client declined the estimate.
Unrefuse Estimate Reverses a recorded refusal.
Create Advance From Estimate Turns a signed estimate's deposit schedule into a real deposit invoice.

Credit notes

Create Credit Note From Invoice Raises a credit note carrying the original invoice's lines across. The lawful way to correct a finalized invoice.
Create Credit Note From Advance Raises a credit note against a deposit invoice.
Create Credit Note Raises a standalone credit note not tied to an existing document.
Get Credit Note Retrieves a credit note by id. Credit notes are the only document type with a read by id route.
Update Credit Note General Information Sets the credit note's header fields and wording.
Update Credit Note Timeline Sets the issue date and payment delay on a credit note.
Update Credit Note Language Sets the language the credit note is rendered in.
Update Credit Note Currency Sets the credit note's currency.

Catalog

List Products Lists catalog products with their prices and VAT codes.
Get Product Retrieves a single catalog product.
Create Product Adds a product to the catalog. Prices are stored in cents.
Update Product Updates a catalog product. Designation, type, unit and VAT code are all required on update.

Accounting registers

Create Income Book Entry Files an entry in the income book, one of the two registers French law requires. Amounts here are in ordinary currency units, not cents.
Delete Income Book Entry Removes an income book entry, used when a duplicate or a misfiling is caught.
Create Purchase Register Entry Files a supplier expense in the purchase register against the right accounting account.
Delete Purchase Register Entry Removes a purchase register entry.

Frequently Asked Questions

What can FlowRunner do with Abby?

FlowRunner agents can run List Organizations, Create Organization, and Update Organization in Abby, plus 47 more actions.

Does connecting Abby to FlowRunner require OAuth?

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

Can Abby trigger a FlowRunner workflow automatically?

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

Start building with Abby

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us