--- title: "Quipu Integration" description: "Quipu is the Spanish invoicing and accounting platform. Agents issue invoices, simplified invoices, and additional incomes, manage contacts, paysheets, and numbering series, attach files, and read the book entries underneath." url: https://flowrunner.ai/integrations/quipu date_modified: 2026-09-04T14:53:04-07:00 --- # Quipu [Accounting](https://flowrunner.ai/integrations/category/finance-accounting) Quipu is the Spanish invoicing and accounting platform. Agents issue invoices, simplified invoices, and additional incomes, manage contacts, paysheets, and numbering series, attach files, and read the book entries underneath. 26 actions · OAuth · available [Quipu website](https://quipuapp.github.io/) · [Platform Documentation](https://quipuapp.github.io/api-v1-docs/) · Capability data verified 2026-08-24 1. A subscription charge settles in the payment processor 2. Agent reads the payer, the amount, and the VAT treatment the sale needs 3. List Contacts resolves the payer inside the register that holds clients, suppliers, and employees together 4. List Numbering Series confirms the number will be drawn from the series already in use 5. Create Document issues the invoice against the income side of the books 6. Download Document stores the PDF and the agent delivers it to the customer 7. A finance lead decides whether a sale that fits no existing series justifies opening a new one ## What This Integration Enables Quipu is built around a small number of registers that carry a lot of meaning in a single field. Invoices, simplified invoices, and additional incomes share one shape, and a Document Kind decides which register a record belongs to and whether it lands as income or expense. Contacts work the same way: clients, suppliers, and employees live in one list, told apart by kind, and each contact carries the payment method, due date preference, and accounting category that later documents inherit. Automating against Quipu is therefore mostly about resolving the right discriminator before writing, which is exactly the kind of lookup work a person should not be doing by hand. FlowRunner agents issue and download documents, maintain contacts, extend the chart of accounts through subcategories, record payroll as paysheets so salaries reach the books without a supplier invoice, and file attachments against the book entries underneath. Two Quipu behaviors shape how those [connectors](https://flowrunner.ai/concepts/connectors) are used. Update Document replaces the whole item set rather than merging into it, so a partial edit means reading the document first. Attachments are filed against the book entry rather than the document, so the evidence and the booking are joined at the accounting layer rather than the presentation one. ### Without FlowRunner **One register, three meanings**: Clients, suppliers, and employees sit in the same list, and the distinction is a field somebody has to get right **Corrections retyped**: Changing one line on an invoice means restating the whole document from memory **Receipts filed separately**: The proof behind a booking arrives by email and is attached later, if at all ### With FlowRunner **The discriminator is read, not assumed**: The agent looks up the contact and the document kind before it writes, so the record lands on the right side of the books **Corrections built from the current record**: The agent reads the document first, then sends the complete set of lines back with the change applied **Evidence attached at the booking**: Files are uploaded against the book entry the moment the document is created ## Use Case Scenarios ### Recurring revenue becomes Spanish invoices A charge settles in [Stripe](https://flowrunner.ai/integrations/stripe) or [Mollie](https://flowrunner.ai/integrations/mollie). The agent resolves the payer with List Contacts, creating the contact with Create Contact when it is genuinely new so that the payment method and accounting category are set once rather than restated on every invoice. Create Document issues the invoice with the kind that books it as income, drawing its number from the existing series. Download Document stores the PDF, and the file goes back to the customer through the same channel the sale came from. A storefront on [PrestaShop](https://flowrunner.ai/integrations/prestashop) or [WooCommerce](https://flowrunner.ai/integrations/woocommerce) feeds the same path with simplified invoices instead. ### Supplier receipts filed where an auditor will look An expense arrives as a PDF in a shared mailbox. The agent extracts the supplier, amount, and tax, resolves the supplier in the contact register, and calls Create Document with the kind that books it as an expense. It then reads List Book Entries to find the entry the document produced and calls Upload Attachment against that entry, because Quipu files evidence at the book entry rather than the document. The result is a booking whose supporting file is attached at the accounting layer rather than sitting in an inbox. ### Payroll cost that reaches the books without an invoice Salaries do not arrive as supplier invoices, which is why Quipu has paysheets. Each month the agent reads the employee contacts, calls Create Paysheet against each one to post the payroll cost, and reconciles the total against the payroll provider's own figures. Any employee whose paysheet total disagrees with the payroll run is listed in a summary posted to [Slack](https://flowrunner.ai/integrations/slack) rather than corrected silently, because a mismatch here usually means the underlying employment change never reached one of the two systems. ## Human-in-Loop Highlight The gate here is not on an invoice. It is on Create Numbering Series. Spanish law requires an unbroken sequence per series, which is why a series is its own record in Quipu rather than a prefix on a document. That gives it a property no other write in this connector has: Delete Numbering Series is refused as soon as a single document has drawn a number from it, so the first invoice issued makes the series permanent. An agent that creates a series to keep things tidy, one per storefront or one per marketplace, has quietly committed the company to keeping every one of those sequences unbroken and to explaining them if anyone asks. So the agent never opens a series on its own. When a sale does not fit an existing one, it posts what List Numbering Series currently holds, which series the sale would otherwise have used, and the specific reason the match failed, then waits. Issuing invoices inside a series that already exists runs unattended all day. Deciding that the company now keeps another sequence forever is a person's decision, made once, on purpose. 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 26 actions ### Documents 7 - **List Documents** Lists invoices, simplified invoices, or additional incomes. The three registers share one shape, and Document Kind picks which one is read. - **Get Document** Reads one invoice, simplified invoice, or additional income by its identifier. The step before any correction, because the whole item set has to be sent back. - **Create Document** Creates an invoice, simplified invoice, or additional income. The kind decides whether the record is income or expense, which is what puts it on the right side of the books. - **Update Document** Updates a document. Sending items replaces the whole set rather than merging, so a workflow reads the document first when only one line is changing. - **Delete Document** Deletes an invoice, simplified invoice, or additional income. - **Download Document** Downloads a document as a PDF into FlowRunner file storage, which is how an issued invoice reaches a customer or an approval thread. - **List Book Entries** Lists the book entries, which are the accounting records underneath the documents and what an attachment is filed against. ### Contacts 5 - **List Contacts** Lists the contacts, which hold clients, suppliers, and employees in one register told apart by kind. The lookup that resolves a payer or a supplier before a write. - **Get Contact** Reads one contact by its identifier, including the defaults later documents will inherit. - **Create Contact** Creates a contact. It carries the payment method, due date preference, and accounting category that later documents inherit, separately for income and expenses. - **Update Contact** Updates a contact. Only the attributes supplied are changed, so enrichment passes are safe here. - **Delete Contact** Deletes a contact. Quipu refuses when documents already reference it, which makes this safe to attempt in cleanup flows. ### Chart of Accounts 4 - **List Accounting Categories** Lists the accounting categories, which are the chart of accounts a document books against. Categories are read only, and only their subcategories can be created. - **List Accounting Subcategories** Lists the accounting subcategories, which are the level of the chart of accounts that can be added to. - **Create Accounting Subcategory** Creates a subcategory under one of the fixed accounting categories. Used when a new cost or revenue line needs its own home in the books. - **Delete Accounting Subcategory** Deletes an accounting subcategory. ### Numbering Series 3 - **List Numbering Series** Lists the numbering series, which decide an invoice's number. The read an agent runs before issuing anything, and the evidence behind this page's human gate. - **Create Numbering Series** Creates a numbering series, which is what an invoice draws its number from. Permanent in practice once a document has used it, so this is the operation held for a person. - **Delete Numbering Series** Deletes a numbering series. Quipu refuses once documents have been numbered from it. ### Payroll 3 - **List Paysheets** Lists the paysheets, which record payroll as a cost so salaries reach the books without a supplier invoice. - **Create Paysheet** Records a paysheet against an employee contact, which posts the payroll cost to the books. - **Delete Paysheet** Deletes a paysheet. ### Attachments 3 - **Upload Attachment** Uploads a file against a book entry by fetching it from a URL. Attachments are filed against the book entry rather than the document, so the book entry identifier is required. - **Get Attachment** Reads one attachment by its identifier. - **Delete Attachment** Deletes an attachment. ### Account 1 - **Get User** Reads one user by identifier, which is how the owner slug behind a connection is confirmed before a flow starts writing. ## Frequently Asked Questions ### What can FlowRunner do with Quipu? FlowRunner agents can run List Documents, Get Document, and Create Document in Quipu, plus 23 more actions. ### Does connecting Quipu to FlowRunner require OAuth? Yes. Quipu connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Quipu trigger a FlowRunner workflow automatically? Quipu doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Quipu?** This integration exposes Quipu to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/quipu. Site index: https://flowrunner.ai/llms.txt