--- title: "wflow Integration" description: "wflow is the Czech invoice approval and document workflow platform. Agents file incoming and outgoing documents with their attachments, drive approvals, read comments, manage tags and links, and administer access rights and custom fields." url: https://flowrunner.ai/integrations/wflow date_modified: 2026-09-04T14:53:04-07:00 --- # wflow [Accounting](https://flowrunner.ai/integrations/category/finance-accounting) wflow is the Czech invoice approval and document workflow platform. Agents file incoming and outgoing documents with their attachments, drive approvals, read comments, manage tags and links, and administer access rights and custom fields. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 trigger · 104 actions · OAuth · available [wflow website](https://account.wflow.com/) · [Platform Documentation](https://developers.wflow.com/) · Capability data verified 2026-08-24 1. On wflow Event reports a new incoming document has arrived 2. Add Document Task queues extraction and Get Document reads the fields back 3. Agent matches the supplier against the partners register and the total against the order 4. Set Document Approvals places the document on the route its template defines 5. The approval finishes as Approved, Rejected, or Returned and the flow branches on it 6. Export Documents writes an approved document into the accounting system's format 7. A finance owner rules on the documents the match could not resolve and on register changes ## What This Integration Enables wflow is not an invoicing tool, and reading it as one leads a team to build the wrong flow. It is the layer between an incoming supplier document and the accounting system that will eventually book it. Intake, extraction, an approval route with parallel and sequential levels, a document storage tree with its own rights, twenty four master data registers, and exports in the formats a dozen accounting products expect. The approval itself is the product. The document exists in wflow precisely so that a named person decides it before it reaches the ledger. That makes it an unusually natural fit for [Orchestration as a Service](https://flowrunner.ai/concepts/orchestration-as-a-service), because the platform and the connector agree about where the human belongs. FlowRunner agents handle the parts either side of the decision. They put the document in with Create Document With File, queue extraction, match the supplier against the partners register and the total against the order, place the document on the right approval route, wait, branch on the outcome, export the approved document, and record whether the export actually succeeded. Stamp Document File prints the approval details onto the PDF, so the file that leaves carries its own audit trail rather than pointing at one. The connector also covers the parts that are easy to forget until they break: users, teams, and roles; document types and custom property definitions; the storage tree and its per file and per folder rights; and the registers that every document's coding depends on. ### Without FlowRunner **Intake by inbox**: Supplier PDFs arrive in a shared mailbox and get filed when somebody has time **Approval status opaque**: Where a document sits in its route is answered by asking the person who has it **Export assumed to have worked**: A failed export leaves the document sitting in the queue looking finished ### With FlowRunner **Intake as a step**: Documents are uploaded, extracted, and matched before a person is asked anything **Approval status readable**: The route, its levels, and its outcome are data a flow branches on **Export reported honestly**: Success and failure are both recorded against the document, so the queue tells the truth ## Use Case Scenarios ### Supplier invoice from arrival to ledger A PDF lands in the accounts payable mailbox. The agent calls Create Document With File to put it into wflow, adds an extraction task, and waits for the ready to extract event rather than polling. When the fields come back, it matches the supplier against the partners register, checks the total against the purchase order, and calls Set Document Approvals to place the document on the route its template defines. Lower levels approve before higher ones, and teams at the same level approve in parallel. When the approval finishes, the flow branches on Approved, Rejected, or Returned. An approved document goes through Stamp Document File and Export Documents in the accounting system's format, and Complete Document Task records the export result including a failure, so nothing sits in the queue pretending to be done. ### The approval that goes where the approver already is wflow holds the route, but people answer where they work. The agent reads Get Document, Download Document Main File, and Get Document Comments, then posts the invoice, the matched order, and the specific field that disagrees into [Microsoft Teams](https://flowrunner.ai/integrations/microsoft-teams) or [Slack](https://flowrunner.ai/integrations/slack). The approver decides there. The agent carries the decision back, adds the reasoning as evidence, and lets wflow's own route record who approved what. The decision stays in the system of record; the interruption happens in the channel the approver already has open. ### Archive and access that expire with the project Set Document Rights and Set Storage Folder Rights control who can see what, and both replace the whole access list rather than adding to it, so a flow reads first and amends. When a project closes, the agent walks the storage tree with List Storage Folder Children, copies the finished pack into [SharePoint](https://flowrunner.ai/integrations/sharepoint) for long term retention, and narrows the wflow rights to the finance team. Restore Storage File exists for the file somebody deletes and needs back, which is worth knowing before anyone panics. ## Human-in-Loop Highlight Replace Register is a full import, and the vendor states plainly what that means: entries that are not in the list you send are marked invalid. Sync cost centers from a master system with an extract that happened to be filtered, and every cost center you did not send stops being usable on every future document, across the whole organization. No error is returned, because nothing went wrong. Merge Register is the operation almost every sync actually wants, since it processes only the records you send and leaves the rest alone. The gate here is therefore not whether to write, it is which verb runs. So the master data agent calls Get Register, diffs the incoming set against what is live, and stops when the diff includes removals: "The cost center extract holds 47 entries. The Cost Centers register currently holds 61. Replace Register would invalidate 14 of them, including 3 used on documents in the current period. Merge Register would add 0 and update 47 and touch none of the 14. Which one?" A person answers once, and the register that every future document codes against survives an incomplete extract. The same care applies to Partners, where omitting a field leaves existing values alone but sending it empty deletes them all. 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 104 actions ### Account and Organization 6 - **List My Organizations** Lists the organizations this API client can reach. The first read, because every route carries an organization. - **Get Account** Reads the account behind the credentials. - **Get Organization** Reads one organization's details. - **Get Organization Settings** Reads the organization's configuration, which is what tells a flow how the workspace is set up rather than assuming. - **Allow Integration** Grants an API client access to the organization. Registering a client is only half the setup, and without this step every call is refused even though the token is issued happily. - **Create API Client** Creates an API client. Its secret is shown once and cannot be read again. ### Documents 16 - **List Documents** Lists documents with the platform's expression style query, sorting, and zero based paging. The read behind every queue and report. - **Get Document** Reads one document with its fields. The follow up call after any trigger delivery, because deliveries carry identifiers rather than content. - **Upsert Document** Creates or updates a document from data you already hold, for cases where no file is being uploaded. - **Create Document With File** Uploads the scan or the emailed PDF and creates the document around it. The normal way an incoming invoice enters the platform. - **Delete Document** Removes a document. - **Add Document Task** Queues work against a document, such as extraction or export. The step that hands a document to the platform's own processing. - **Complete Document Task** Records a queued task as finished, with its success or failure. Report failures too, because a document whose export failed silently sits in the queue looking done. - **List Documents To Extract** Lists the documents waiting for extraction. - **List Documents To Export** Lists the documents waiting to be written to the accounting system. The accounting sync queue. - **Export Documents** Renders a selection of documents in an accounting system's own format. Its rendering parameters travel separately from the selection, and marking the documents exported is a switch, so a dry run leaves them alone. - **Set Document Lock** Locks or unlocks a document. A locked document refuses writes, which is the guard working rather than an error to route around. - **Get Document Metadata** Reads a document's metadata. - **Set Document Metadata** Writes a document's metadata. - **Get Document Events** Reads a document's event history. The audit trail behind who did what and when. - **Get Document Comments** Reads the comments on a document, which is where the human reasoning behind a decision usually lives. - **Set Document Payments** Writes a document's payment list. This replaces the whole list rather than appending, so a flow reads first. ### Approvals 7 - **Get Document Approvals** Reads the approval route on a document: its levels, its teams, and where it has got to. - **Set Document Approvals** Places a document on an approval route. Levels decide order, teams at the same level approve in parallel, and supplying teams replaces the template's own approvers. - **Delete Document Approvals** Removes a document's approval route. - **List Approvals Templates** Lists the approval templates the organization has defined. - **Get Approvals Template** Reads one approval template with its levels and teams. - **Upsert Approvals Template** Creates or updates an approval template. A change here reaches every document routed by it afterward. - **Delete Approvals Template** Removes an approval template. ### Links, Rights, and Tags 9 - **Get Document Links** Reads the documents linked to this one, such as the order a supplier invoice matches. - **Add Document Link** Links a document to another, which is how a matched set stays matched. - **Delete Document Link** Removes a link between documents. - **Get Document Rights** Reads who can see and act on a document. - **Set Document Rights** Writes a document's access list, replacing it rather than adding to it. Read first, amend, send back. - **List All Document Tags** Lists every tag in use across the organization. - **Get Document Tags** Reads the tags on one document. - **Add Document Tag** Tags a document, which is how a flow marks exceptions for a later sweep without inventing its own store. - **Delete Document Tag** Removes a tag from a document. ### Document Files 6 - **List Document Files** Lists the files attached to a document. - **Upload Document File** Attaches a file to a document. - **Download Document File** Fetches one attached file into FlowRunner file storage. - **Download Document Main File** Fetches the document's primary file without needing a file identifier. The shortest path from a trigger delivery to the actual invoice. - **Delete Document File** Removes an attached file. - **Stamp Document File** Prints the approval details onto the PDF, so the file leaving the platform carries its own audit trail. ### Document Types 4 - **List Document Types** Lists the document types configured on the organization. - **Get Document Type** Reads one document type. - **Upsert Document Type** Creates or updates a document type. - **Delete Document Type** Removes a document type. ### Document Properties 8 - **Get Document Properties** Reads a document's custom property values. - **Set Document Properties** Writes a document's custom property values. - **Set Document Properties With Definition** Writes property values against their definitions, for cases where the definition has to travel with the value. - **Delete Document Property Value** Clears one property value on a document. - **List Document Property Definitions** Lists the custom property definitions available to documents. The read that lets a flow adapt to the organization's own fields rather than hard coding them. - **Get Document Property Definition** Reads one property definition. - **Upsert Document Property Definition** Creates or updates a property definition. - **Delete Document Property Definition** Removes a property definition. ### Storage Files 22 - **List Storage Files** Lists the files in the storage tree. - **Get Storage File** Reads one storage file's record. - **Upload Storage File** Puts a file into the storage tree. - **Download Storage File** Fetches a storage file into FlowRunner file storage. - **Delete Storage File** Removes a storage file. - **Restore Storage File** Brings back a deleted storage file. The operation worth knowing about before anyone panics. - **Move Storage File** Moves a file to another folder, which also moves it under that folder's access rules. - **Rename Storage File** Renames a storage file. - **Set Storage File Lock** Locks or unlocks a storage file against changes. - **Get Storage File Approvals** Reads the approval route on a storage file. - **Set Storage File Approvals** Places a storage file on an approval route. - **Delete Storage File Approvals** Removes a storage file's approval route. - **Get Storage File Properties** Reads a storage file's custom property values. - **Set Storage File Properties** Writes a storage file's custom property values. - **Set Storage File Properties With Definition** Writes storage file property values against their definitions. - **Delete Storage File Property Value** Clears one property value on a storage file. - **List Storage File Property Definitions** Lists the property definitions available to storage files. - **Get Storage File Property Definition** Reads one storage file property definition. - **Upsert Storage File Property Definition** Creates or updates a storage file property definition. - **Delete Storage File Property Definition** Removes a storage file property definition. - **Get Storage File Rights** Reads who can see and act on a storage file. - **Set Storage File Rights** Writes a storage file's access list, replacing it whole. ### Storage Folders 6 - **List Storage Folder Children** Lists a folder's contents. The walk behind an archive sweep or a rights audit. - **Get Storage Folder** Reads one folder. - **Upsert Storage Folder** Creates or updates a folder. - **Delete Storage Folder** Removes a folder. - **Get Storage Folder Rights** Reads who can see and act on a folder. - **Set Storage Folder Rights** Writes a folder's access list, replacing it whole. The operation that quietly governs everything filed beneath it. ### Users, Teams, and Roles 14 - **List Users** Lists the organization's users. - **Get User** Reads one user with their roles, teams, and document type permissions. - **Upsert User** Creates or updates a user. Roles, teams, and document type permissions are each written as a complete list, so an omission removes rather than preserves. - **Delete User** Removes a user from the organization. - **List Teams** Lists the teams, which are what approval levels are made of. - **Get Team** Reads one team with its membership. - **Create Team** Creates a team. - **Update Team** Updates a team, replacing its membership with what you send. - **Delete Team** Removes a team. Approval routes built on it stop resolving, so this follows a check of where the team is used. - **List Roles** Lists the roles defined on the organization. - **Get Role** Reads one role with its rights. - **Create Role** Creates a role. - **Update Role** Updates a role, replacing its rights with what you send. - **Delete Role** Removes a role. ### Registers 3 - **Get Register** Reads a whole master data register, chosen from the twenty four the platform defines. The read a safe sync diffs against. - **Merge Register** Processes only the entries you send and leaves every other record untouched. The right operation for almost every incremental sync. - **Replace Register** Imports a register as a complete set, marking every entry you did not send as invalid. Powerful and unforgiving, which is why it sits behind the review gate above. ### Webhooks 3 - **List Webhook Registrations** Lists the webhook registrations on the organization, including any a trigger created. - **Upsert Webhook Registration** Creates or updates a webhook registration. One registration can carry several event actions. - **Delete Webhook Registration** Removes a webhook registration. ## Triggers 1 triggers ### Event Triggers 1 - **On wflow Event** Fires when a document is created, updated, reviewed, deleted, ready to extract, or ready to export, when its approval process finishes, or when a register changes. The approval finished event carries the status the flow branches on: Approved, Rejected, or Returned. Deliveries carry identifiers rather than content, so follow the trigger with Get Document and Download Document Main File to read what actually changed. The vendor signs nothing and sends no secret, so the trigger instead registers a callback URL carrying a generated token and checks that token back on every delivery, which proves the delivery arrived at a URL only the platform was given. That is stated plainly here rather than presented as a cryptographic signature check. ## Frequently Asked Questions ### What can FlowRunner do with wflow? FlowRunner agents can run List My Organizations, Get Account, and Get Organization in wflow, plus 101 more actions. ### Does connecting wflow to FlowRunner require OAuth? Yes. wflow connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can wflow trigger a FlowRunner workflow automatically? Yes. wflow supports 1 trigger that can start a FlowRunner workflow automatically. **Work at wflow?** This integration exposes wflow 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/wflow. Site index: https://flowrunner.ai/llms.txt