VosFactures

VosFactures is the French online invoicing platform. Agents issue billing documents of every kind, manage contacts and their delivery addresses, maintain products, and send and track documents from a workflow.

Verified 1 trigger 77 actions API key available

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

A bank receipt arrives for a customer with no document reference on it

Agent reads the payer, the amount, the currency, and the value date

List Clients resolves the payer by tax number, reference, or email address

List Invoices reads that contact's open documents with the period filter lifted

Agent tests whether the amount settles exactly one open document

Create Payment records the settlement when a single document matches

A person orders the allocation when one amount has to be spread across several documents

What This Integration Enables

VosFactures is the French face of a billing platform also sold as Fakturownia and InvoiceOcean, and its shape gives away who it is built for. An account issues documents from several seller departments, each with its own legal name, bank details, and logo. It runs warehouses and stock documents beside the invoices. Its API can create an entire billing account, add users to it, and start its deletion. That is not a solo freelancer's invoicing tool. It is billing infrastructure for a business running several trading entities, or for a platform that bills on behalf of its own customers.

FlowRunner agents work across that whole surface: documents of every kind with their line items and attachments, contacts and their delivery addresses, products, bundles and per contact price lists, payments, recurring schedules, warehouse movements, and the webhooks that report changes back. FlowRunner connectors are built and verified against each vendor's official API, and here that verification does real work, because the platform's most expensive failure mode is not an error. Fields sent at the wrong level are accepted and silently discarded, and every listing defaults to a period rather than the whole book. Both look like success.

That is the argument for putting a person on the decisions where a plausible wrong answer costs the most.

Without FlowRunner

Partial payments allocated ad hoc A short payment gets applied to whichever invoice is on screen, and the aged balance drifts

Duplicate contacts merged on instinct Two records for the same buyer are combined without anyone comparing what each one carries

Reads that quietly narrow A listing returns a plausible answer that covers a period rather than the whole book

With FlowRunner

Allocation ordered deliberately The agent proposes the sequence, shows what each document ends at, and a person confirms it

Merges evidenced first Both contacts are read in full and the surviving record is named before anything moves

Reads that state their scope Period and paging are set explicitly, so a decision is never made on a partial set

Use Case Scenarios

Cash application that shows its working

A receipt clears in Stripe, Mollie, or GoCardless with a payer name and no document reference. The agent resolves the contact with List Clients against the tax number, then calls List Invoices for that contact's open documents with the period widened past the default so the candidate set is genuinely complete. If the amount settles one document to the cent, Create Payment records it and Change Invoice Status marks it paid. If it does not, the agent stops rather than guessing, because the platform applies a multi document payment in the order it is given.
Recurring billing across trading entities

A business issuing from several seller departments keeps each one's numbering, bank details, and branding separate. The agent reads List Departments to resolve which entity a contract belongs to, then Create Recurring sets up the schedule against that department using a price list resolved by Get Price List Prices, so a negotiated rate is applied rather than the catalog price. Each week List Recurrings reports what is due to issue, the forecast appends to Google Sheets, and a summary posts to Slack. Update Recurring moves a next issue date or stops a schedule when a contract ends.
Documents that arrive with their evidence attached

A signed order comes back from DocuSign and a delivery note is produced in the warehouse. The agent creates the invoice with Create Invoice, then Add Invoice Attachment files the signed order and the delivery note against it, running the platform's signed upload in a single step. Create Warehouse Document records the goods leaving stock, and List Warehouse Actions gives the movement history a dispute is settled from. When the customer asks what they were charged for, Download Invoice Attachments returns the whole evidence pack as one archive rather than a hunt through three systems.

Human-in-Loop Highlight

Create Payment accepts a list of documents to settle, and that list is a sequence rather than a set. The amount is applied to the first document until it is settled, then to the next, which means reordering the same list changes which invoice is left part paid and which customer's aged balance shows the shortfall. Nothing errors either way. Worse, the candidate set the agent assembled came from a listing that filters on a period by default, so an old open document can sit outside the read entirely and never be offered. So the cash application agent proposes and stops: "Received 7,400 EUR from Ateliers Bourdon, no reference. Four documents open, 9,150 EUR in total, the oldest from March. Applying oldest first settles three and leaves FA-2026-0611 short by 1,750 EUR. Applying to the two documents they queried last week settles both and leaves the March one untouched. Which order?" A person answers, the agent records it once, and the balance the collections team argues from is the one somebody chose. The same discipline governs Merge Clients, which moves documents across and deletes the duplicates with no undo.

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

77 actions

Billing Documents

List Invoices Lists documents filtered by period, kind, contact, or order, optionally with their line items. Set the period deliberately, because the platform's own default covers a window rather than the whole book.
Get Invoice Reads one document, optionally with its payments, reminders, and extra fields. The response carries a public token, which is the link to send a customer rather than re-hosting a PDF.
Create Invoice Issues an invoice, credit note, estimate, proforma, order, or receipt with its line items.
Update Invoice Amends a document. Sending line items replaces the whole set rather than merging, so a flow reads them, edits the array, and sends it all back.
Delete Invoice Removes a document outright.
Cancel Invoice Cancels a document and keeps it on file, optionally recording why. The auditable alternative to deleting.
Change Invoice Status Moves a document's state, such as marking it sent, paid, or accepted.
Send Invoice By Email Emails the document to its recipient, optionally copying other addresses and attaching the PDF. The platform declines a repeat send of the same document within a few days unless the flow deliberately forces it.
Download Invoice PDF Fetches the document as a PDF into FlowRunner file storage.
Download Invoice Attachments Fetches every attachment on a document as a single archive. The one call behind a complete evidence pack.
Add Invoice Attachment Attaches a file to a document, running the platform's three step signed upload in one operation.
Get Invoice Reminders Reads how many payment reminders a document has had, of which kinds, and when. The evidence a collections decision rests on.
Get Reminders Report Reports every reminder sent in a window of up to seven days, with the document, contact, and user behind each. A longer range has to come from the interface.

Recurring Schedules

List Recurrings Lists the recurring schedules on the account. The read behind a forecast of what is about to bill.
Get Recurring Reads one schedule with its settings and next issue date.
Create Recurring Sets up a schedule from an existing document or from a contact and a product.
Update Recurring Amends a schedule, including moving its next issue date or stopping it.
Delete Recurring Removes a schedule outright.

Contacts

List Clients Lists contacts, or finds one by external reference, tax number, name, short name, or email. The five exact lookup keys behind reliable matching.
Get Client Reads one contact, optionally with its bank details.
Create Client Adds a contact as a business or a private individual, with addresses, tax numbers, and billing defaults.
Update Client Amends a contact.
Delete Client Removes a contact from the account.
Merge Clients Combines duplicate contacts into one, moving their documents across and deleting the duplicates. There is no undo, so this runs after a person names the survivor.
Create Address Adds a delivery address to a contact, for buyers who receive goods somewhere other than where they are invoiced.

Products and Price Lists

List Products Lists products, optionally with per warehouse quantities or restricted to inactive ones.
Get Product Reads one product, optionally with its quantity in a named warehouse.
Create Product Adds a product, including a bundle of other products, with sales and purchase prices and stock settings.
Update Product Amends a product, typically from a catalog sync.
Delete Product Removes a product.
List Price Lists Lists the price lists holding per contact or per group pricing.
Get Price List Reads one price list.
Get Price List Prices Reads what a price list charges for specific products. The lookup that puts a negotiated rate on a document instead of the catalog price.
Create Price List Builds a price list with a fixed price or a percentage adjustment per product.
Update Price List Amends a price list, including the prices it holds for individual products.
Delete Price List Removes a price list.

Seller Departments

List Departments Lists the seller departments, which are the trading entities documents are issued from. The read that resolves which company a contract belongs to.
Get Department Reads one seller department with its legal name, tax settings, and bank details.
Create Department Adds a seller department, the entity whose details print on its documents.
Update Department Amends a seller department.
Upload Department Logo Uploads the logo image that prints on that department's documents.
Delete Department Removes a seller department.

Payments

List Payments Lists recorded payments, optionally with the documents each one settles.
Get Payment Reads one payment.
Create Payment Records a payment against one document or several, optionally generating an invoice for it. When several documents are named, the amount is applied in the order given, which is why the ordering is a human decision.
Update Payment Amends a recorded payment.
Delete Payment Removes a payment, which puts the documents it settled back to open.

Warehouses and Stock

List Warehouses Lists the configured warehouses.
Get Warehouse Reads one warehouse.
Create Warehouse Adds a warehouse.
Update Warehouse Amends a warehouse.
Delete Warehouse Removes a warehouse.
List Warehouse Documents Lists goods received notes, delivery notes, and transfers.
Get Warehouse Document Reads one stock document with its movements.
Create Warehouse Document Raises a goods received note, a delivery note, or a transfer between warehouses. Sending its movements replaces the whole set.
Update Warehouse Document Amends a stock document.
Delete Warehouse Document Removes a stock document.
List Warehouse Actions Lists individual stock movements filtered by warehouse, product, kind, date, or stock document. The history a quantity dispute is settled from.

Account, Users, and Templates

Get Account Reads the account this connection belongs to, including its prefix and URL.
Create Account Creates a billing account from your own application, with its owner and company details. The operation that makes this a platform product rather than a single company's tool.
Add Account User Adds a user to the account, either inviting an existing one or creating a new one, with a role and department access.
Delete Account Starts the account deletion procedure. The platform sends a confirmation email rather than deleting immediately.
Login Signs in with a login and password to read that account's prefix, URL, and API token. Used when a platform provisions connections for its own customers.
List Invoice Templates Lists the print templates whose identifiers the template parameters take. This route is undocumented by the vendor and was proven by probing, so its response shape is the server's rather than a published contract.
List Users Lists the users on the account. Also an undocumented route proven by probing.
List Roles Lists the custom roles whose identifiers Add Account User takes. Also undocumented and proven by probing.
List Activities Lists the account's activity log. Also undocumented and proven by probing.

Webhooks

List Webhooks Lists the webhooks on the account, including any this connection's triggers created.
Get Webhook Reads one webhook.
Create Webhook Registers a webhook for one event kind. The platform allows exactly one kind per webhook, so covering several means registering several.
Update Webhook Amends a webhook, such as changing its target URL or switching it off.
Delete Webhook Removes a webhook.

Triggers

1 triggers

Event Triggers

On VosFactures Event Fires when a document, contact, or product is created, updated, or deleted. Because the platform allows one event kind per webhook, subscribing to everything registers a webhook per kind, and they are removed together when the trigger is. The vendor documents the event names but nothing about the delivery body, so the trigger takes the kind from the callback URL it registered rather than from the payload, and hands the flow the parsed record alongside the raw payload. Follow it with Get Invoice, Get Client, or Get Product to be certain what changed before acting on it.

Frequently Asked Questions

What can FlowRunner do with VosFactures?

FlowRunner agents can run List Invoices, Get Invoice, and Create Invoice in VosFactures, plus 74 more actions.

Does connecting VosFactures to FlowRunner require OAuth?

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

Can VosFactures trigger a FlowRunner workflow automatically?

Yes. VosFactures supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with VosFactures

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us