--- title: "Vyfakturuj.cz Integration" description: "Vyfakturuj.cz is the Czech online invoicing platform. Agents create billing documents and their items, manage the address book, run templates and recurring invoices, and maintain tags, number series, and payment methods." url: https://flowrunner.ai/integrations/vyfakturuj-cz date_modified: 2026-09-04T14:53:04-07:00 --- # Vyfakturuj.cz [Accounting](https://flowrunner.ai/integrations/category/finance-accounting) Vyfakturuj.cz is the Czech online invoicing platform. Agents create billing documents and their items, manage the address book, run templates and recurring invoices, and maintain tags, number series, and payment methods. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 28 actions · Basic auth · available [Vyfakturuj.cz website](https://vyfakturuj.cz/) · [Platform Documentation](https://api.vyfakturuj.cz/scalar/) · Capability data verified 2026-08-24 1. A completed order arrives from the storefront or the order system 2. Agent reads the buyer identity, the lines, the VAT treatment, and the payment terms 3. List Contacts resolves the buyer by registration number, VAT number, or email 4. Render Invoice Preview builds the PDF without saving it and without consuming a number 5. Create Invoice issues the document once the preview matches the order 6. The agent sends the payment link that comes back on the document record 7. A person reviews any document whose preview priced differently from the order before it is issued ## What This Integration Enables Vyfakturuj.cz is a Czech invoicing platform for businesses that bill in a numbered series they may one day have to defend line by line. Its API reflects that. Document type and document state are bit values rather than words, so a proforma is type 4 and a document that is both VAT bearing and paid carries flags 3. FlowRunner's [connectors](https://flowrunner.ai/concepts/connectors) decode both on the way through, which means an agent can branch on the state a controller would recognize instead of on a number nobody remembers. Agents issue and amend billing documents of every kind, keep the address book current, run templates and recurring schedules, and read the number series and payment methods a document depends on. Two capabilities are worth calling out because they change how a flow is built. Render Invoice Preview is a genuine dry run that returns the PDF and keeps nothing, consuming no number from any series. Send Invoice By Email in test mode renders the email and returns it without sending it. Together they let an agent prove a document before it exists, which is the safest possible place to put a review. The same API serves SimpleShop.cz, so a connection points at whichever product the account lives on. ### Without FlowRunner **Numbering treated casually**: Test invoices and corrections burn numbers out of a series an auditor will later read in sequence **State read by eye**: Whether a document is paid, sent, canceled, or overpaid is checked by opening it **Corrections improvised**: Canceling a document and stopping a recurring schedule are done by hand, when someone remembers ### With FlowRunner **Numbering protected**: Drafts are rendered as previews first, so a number is consumed only by a document that will stand **State read by name**: Documents arrive decoded, so a flow branches on Paid or Sent To Customer rather than on arithmetic **Corrections routed**: Cancellations and schedule stops are proposed with evidence and confirmed by a person ## Use Case Scenarios ### The order becomes an invoice, and the preview comes first An order lands from [WooCommerce](https://flowrunner.ai/integrations/woocommerce) or a payment settles in [Stripe](https://flowrunner.ai/integrations/stripe). The agent resolves the buyer with List Contacts against the registration number, creating the record with Create Contact when there is no match. It assembles the lines and calls Render Invoice Preview, which returns a PDF built from exactly what would be sent. The agent compares the preview totals against the order totals. When they agree it calls Create Invoice, reads the document back with Get Invoice for its public payment link, and posts the link to the customer. When they disagree, nothing has been issued and no number has been spent. ### Recurring revenue that reports on itself Create Template sets up the recurring schedule once, with its interval, its document settings, and its lines. Each week the agent calls List Templates and Get Template to read which schedules are due next, then appends the forecast to a sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and posts the week ahead to [Slack](https://flowrunner.ai/integrations/slack). Finance sees what will be billed before it is billed rather than discovering it in the export. When a customer cancels, the change is a stop on the template rather than a deletion, so the record and its history survive. ### The overdue sweep that never guesses A daily sweep calls List Invoices filtered on unpaid documents past their due date. Because the connector decodes the flags bitmask, the agent can separate a document that is genuinely unpaid from one already marked reminder sent, overpaid, or archived, which a naive equality check on the raw number would confuse. For each genuinely overdue document it calls Send Invoice By Email in reminder mode. Mark Invoice As Paid records settlements as the bank feed confirms them, in full or in part. Anything that looks like a dispute rather than a delay is routed to a person instead of a second reminder. ## Human-in-Loop Highlight Canceling a document in Vyfakturuj.cz is not its own operation. It is Update Invoice with Storno switched on, which means the most consequential write in this connector wears the same name as the routine one that fixes a typo. There is no un-cancel action anywhere in the API, the number stays spent, and the document stays in the series as a canceled entry an auditor will read. So an agent that finds a billing error gathers the evidence and stops. It posts to the finance owner: "Invoice 2026-0418 for 84,500 CZK to Novak s.r.o. was issued against the wrong VAT rate. Correcting the lines is an ordinary update. Canceling and reissuing consumes a new number and leaves a canceled document on file. Which one?" The same gate covers the quieter version of the problem: Update Template with End Type set to Stopped ends a recurring schedule while leaving the record in place, so the failure is not an error message, it is an invoice that silently never goes out again. 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 28 actions ### Billing Documents 9 - **List Invoices** Searches billing documents by type, state, contact, date range, amount, or free text, with sorting and paging. The read behind every overdue sweep and revenue report. - **Get Invoice** Reads one document with its items, its decoded type and state, and the four ready made links the platform returns: the public web page, the online payment page, and the PDF with and without the stamp. - **Create Invoice** Issues a billing document with its items, supplier and customer details, VAT treatment, and payment terms. Consumes a number from the series, so it runs after the preview agrees. - **Update Invoice** Amends a document. Sending items replaces the whole set rather than merging, and switching Storno on cancels the document, which is why this operation sits behind the review gate above. - **Delete Invoice** Removes a billing document. Reserved for records that should never have existed, not for corrections. - **Mark Invoice As Paid** Records a settlement in full or in part. The platform's own convention also lets this operation reverse a recorded payment, which makes it the one write here that can be taken back. - **Send Invoice By Email** Emails the document as a new invoice, a reminder, or a payment confirmation, with the PDF and any further attachments. In test mode it renders the message and returns it without sending, which is how a template change is checked. - **Download Invoice PDF** Fetches the document as a PDF, with or without the stamp, into FlowRunner file storage for archiving or forwarding. - **Render Invoice Preview** Builds a document as a PDF and keeps nothing. No record is created and no number is consumed. The dry run that lets an agent show a customer or a reviewer exactly what would be issued. ### Address Book 5 - **List Contacts** Searches the address book by registration number, VAT number, name, note, telephone, email, or free text. The matching step that stops a repeat customer becoming a second record. - **Get Contact** Reads one contact with its addresses, tax numbers, and document defaults. - **Create Contact** Adds a contact with its billing and delivery addresses, tax identifiers, and the defaults its documents inherit. - **Update Contact** Amends a contact. Used for enrichment passes and for correcting registration details before the next document is issued. - **Delete Contact** Removes a contact from the address book. ### Templates and Recurring Invoices 5 - **List Templates** Searches templates and recurring schedules. Used to report on what is due to bill before it bills. - **Get Template** Reads one template or recurring schedule, including when the next document is due. - **Create Template** Defines a template or recurring schedule with its interval, its document settings, and its items. - **Update Template** Amends a schedule. Setting End Type to Stopped ends the recurring run while leaving the record on file, which is why this operation is treated as consequential rather than routine. - **Delete Template** Removes a template or recurring schedule outright. ### Catalog, Tags, and Settings 9 - **List Products** Reads the product list, so a document's lines can be assembled from the catalog rather than typed. - **List Tags** Lists the tags documents can be marked with, which is how a flow segments revenue without inventing its own labels. - **Get Tag** Reads one tag by its identifier. - **Create Tag** Adds a tag that documents can then carry. - **Update Tag** Renames or amends a tag. - **Delete Tag** Removes a tag. - **List Number Series** Lists the series that generate document numbers. The read that tells an agent which sequence a document is about to draw from. - **List Payment Methods** Lists the configured payment methods whose identifiers a document takes, so a flow sets a real method rather than guessing an ordinal. - **Test Connection** Verifies the credentials work without reading or writing anything. Used as a startup check before a batch runs. ## Frequently Asked Questions ### What can FlowRunner do with Vyfakturuj.cz? FlowRunner agents can run List Invoices, Get Invoice, and Create Invoice in Vyfakturuj.cz, plus 25 more actions. ### Does connecting Vyfakturuj.cz to FlowRunner require OAuth? No. Vyfakturuj.cz connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Vyfakturuj.cz trigger a FlowRunner workflow automatically? Vyfakturuj.cz doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Vyfakturuj.cz?** This integration exposes Vyfakturuj.cz 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/vyfakturuj-cz. Site index: https://flowrunner.ai/llms.txt