--- title: "Cflow Integration" description: "Cflow by Cavintek is a no-code approval workflow and business process automation platform. Agents submit and update records, move them through workflow stages, post comments, clarifications, and attachments, pull reports, and administer users, roles, and team access." url: https://flowrunner.ai/integrations/cflow date_modified: 2026-09-04T14:52:04-07:00 --- # Cflow [Productivity](https://flowrunner.ai/integrations/category/project-management-productivity) Cflow by Cavintek is a no-code approval workflow and business process automation platform. Agents submit and update records, move them through workflow stages, post comments, clarifications, and attachments, pull reports, and administer users, roles, and team access. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 53 actions · API key · available [Cflow website](https://apidocs.cflowapps.com/) · [Platform Documentation](https://apidocs.cflowapps.com/) · Capability data verified 2026-08-24 1. A supplier invoice arrives in the shared mailbox with a PDF attached 2. Agent reads the vendor, amount, cost center, and purchase order reference from the document 3. List Fields returns the stage's field definitions so every value is addressed by its display name 4. Submit Record creates the request in the approval workflow, as a draft until the data checks out 5. Attach Files To Record puts the source PDF on the record where the approver will look for it 6. Get Current Stage reports where the record sits and who it is waiting on 7. The approver is reminded on the channel they actually read, with the amount and the vendor named 8. The approver decides, and Update Record Status advances the record with their decision ## What This Integration Enables Cflow is an approval engine, and a capable one: it owns the stages, the routing, the clarification loop, and the reporting for the requests that live inside it. That is worth stating plainly, because it decides what an agent should and should not be doing here. FlowRunner is not a second approval layer stacked on top. It is the layer that gets requests into Cflow already correct, keeps the humans who have to decide from having to go looking, and carries the decision out to the systems Cflow does not reach. FlowRunner agents submit and update records, advance them through stages, post comments, raise and answer clarifications, attach and download files, pull all eleven of Cflow's reports, and administer users, roles, teams, and stage access. Two mechanics shape every flow built on this connector. Records are addressed by field display name rather than by identifier, which is why reading the field definitions for a stage is the first call a well-built flow makes rather than a hard-coded assumption. And there are two operations for changing a record, deliberately: the full update insists on a complete set of values and will overwrite what it is not sent, while the status operation advances a record without touching its data. An approval flow uses the second one. Every capability described here is built and verified against Cflow's published API. ### Without FlowRunner **Requests are typed twice**: The source document exists, and somebody retypes its values into the request form **Approvals stall out of sight**: A request waits on somebody who has not opened the tool this week, and nobody notices **The process ends at the boundary**: An approved request is approved, and then a person carries it into the finance system by hand ### With FlowRunner **Requests arrive already filled**: The agent reads the source document and submits the record with its fields already populated **Waiting is visible and chased**: Pending work is read per person and surfaced where that person actually is **Approval triggers the downstream act**: The decision moves the record and the systems on the other side of it in the same run ## Use Case Scenarios ### Invoices that arrive as requests, not as email A supplier invoice reaches a shared mailbox. The agent extracts the vendor, the amount, the cost center, and the purchase order reference, then calls List Workflow Stages and List Fields so it addresses each value by the display name the workflow actually uses rather than a name someone wrote down last quarter. Submit Record creates the request, saved as a draft while the agent checks the purchase order in [QuickBooks Online](https://flowrunner.ai/integrations/quickbooks-online). If everything reconciles, the record is submitted and Attach Files To Record puts the original PDF on it. If it does not, the discrepancy goes to the requester before an approver ever sees it. The approvals that follow are Cflow's, and they stay Cflow's. ### Chasing what is actually waiting on a person Every morning the agent calls List Pending Items for each approver, which answers the question a person actually has, namely what is waiting on me across every workflow. Anything past its threshold is posted to that person in [Slack](https://flowrunner.ai/integrations/slack) with the record, the amount, and how long it has been sitting. Where a clarification is open, List Pending Clarifications supplies the question itself so the reminder carries the thing being asked rather than a link to go find it. When the approver replies with a decision, Update Record Status advances the record, and Add Comment records who decided and on what basis. The comment is visible on the record to everyone who can see it, which is the point. ### Closing the loop past the boundary of the tool A contract request completes its final stage. Get Triggered Workflows tells the agent what that record set off downstream through Cflow's own process linking, so nothing is duplicated. Then the agent does the part Cflow does not: it sends the countersignature request through [DocuSign](https://flowrunner.ai/integrations/docusign), writes the approved terms to the vendor record, and appends the outcome to a reconciliation sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets). Monthly, Get Stage Visit Report and Get Stage Performance Report feed a process review, where repeated visits to a single stage are how a rework loop shows up in the data rather than in somebody's impression of it. ## Human-in-Loop Highlight Nearly everything on this connector is reversible: a record can be corrected, a comment can be superseded, a clarification can be answered again. Two operations are not, in the sense that matters. Update Stage Access sets which role acts at a stage and what it may see and edit, which changes who can read and alter real records across the whole workflow. Remove Role takes a role away from a person, and because roles decide what somebody may approve, removing the wrong one can leave a record with nobody able to act on it at all. There is also Create User, which sets a person's password directly rather than sending them an invitation, and Reset User Password, which changes a credential instead of emailing a reset link. So a FlowRunner agent runs the record work unattended and stops at the permission boundary: "The joiners and leavers feed asks to remove the Finance Approver role from two people and change stage access on the Purchase Approval workflow. Two records currently sit at that stage. If this applies, one of them will have no eligible approver. Apply, reassign the records first, or hold?" The workflow administrator answers. The agent can tell that the change will strand a record, because Get Stage Access and Get Current Stage let it check. What it should not do is decide that stranding it is acceptable. Moving requests through an approval process is an agent's work. Changing who is allowed to approve is not. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 53 actions ### Workflow structure 5 - **List Workflows** Returns every workflow in the account. The workflow name it returns is the identifier every other operation takes, which makes this the first call when a flow is being built. - **List Workflow Stages** Returns the stages of one workflow. Stage names are what the record and report operations address, and they are display names rather than identifiers. - **List Fields** Returns the field definitions of a workflow or lookup at one stage. Records are addressed by field display name, and this is where those names come from. - **List Pending Items** Returns everything waiting on one person across all workflows. It is the natural start of a reminder flow, because it answers the question a person actually has. - **Get Triggered Workflows** Returns the workflows a record set off downstream through Cflow's process linking, so a flow can follow what it started rather than duplicating it. ### Records 8 - **Submit Record** Creates a record in a workflow. Values are keyed by field display name, table sections travel separately from ordinary fields, and saving as a draft creates the record without starting the approval. - **Update Record** Changes a record's field values and its status in one call. Table rows are edited and removed in place rather than replaced wholesale. - **Update Record Status** Approves, rejects, or otherwise advances a record without touching its field values. This is the right operation for an approval flow, because the full update insists on a complete set of values and would overwrite what it is not sent. - **Get Record Details** Returns one record's field values. - **Get Current Stage** Returns where a record currently sits and who it is waiting on. It is cheaper than the full record read when a flow only needs to know whether something moved. - **Search Records** Finds records by field value. The criteria travel as query parameters keyed by field display name rather than in the body. - **List Initiated Records** Returns records created in a date range across all users. Pages hold one hundred records and start at one, so a busy range needs several calls. - **List Reviewed Records** Returns records updated or reviewed in a date range across all users, paged the same way. ### Comments and files 5 - **List Comments** Returns the comments on a record. - **Add Comment** Adds a comment to a record. Cflow shows it to everyone who can see the record, so it is a public note rather than an internal one. - **Attach File To Field** Uploads a file into a named file field on a record. Cflow caps a single file at twenty megabytes. - **Attach Files To Record** Uploads one or more files to a record's general attachment list, which is separate from a file field. - **Download Record File** Downloads the file held in a file or signature field and stores it in FlowRunner file storage, which is how an approved document reaches the systems on the other side. ### Clarifications 3 - **List Pending Clarifications** Returns the clarification questions waiting on the calling user. It is scoped to whoever the user key belongs to, so it answers what am I being asked rather than what is outstanding across the account. - **Request Clarification** Asks one or more people a question about a record, which parks the record until they answer. - **Answer Clarification** Answers a clarification question, or edits an answer already given. ### Reports 11 - **Get Approver Performance Report** Returns how each approver performed on a workflow over a date range: how much they handled and how long they took. - **Get Workflow Performance Report** Returns a workflow's overall throughput and cycle time over a date range. - **Get Current Status Report** Returns where every record of a workflow currently stands. - **Get Completed Requests Report** Returns the records of a workflow that finished within a date range. - **Get Stage Visit Report** Returns how often records passed through each stage. Repeated visits to a single stage are how a rework loop shows up in the data. - **Get Stage Performance Report** Returns how long records spend at each stage of a workflow. - **Get Pending Requests Report** Returns what is outstanding on one named person for a workflow over a date range. The person is required, which makes this the per-person view with dates rather than a whole backlog. - **Get Clarification Report** Returns the clarifications raised on a workflow, with filters that accept a literal all value to drop that part of the filter. - **Get Audit Trail Report** Returns the audit trail of a workflow, or of one record within it. The record is optional, which makes this both a per-record history and a workflow-wide audit. - **Get API Activity Report** Returns Cflow's own record of the API calls made against a workflow, and can be widened to an account-level view of API usage. - **Get SLA Report** Returns SLA compliance for a workflow. Stages here take an array of names rather than the single stage every other report expects. ### Users 7 - **List Users** Returns every user in the account. - **Get User** Returns one user by username. - **Create User** Adds a user to the account. It sets the person's password directly rather than inviting them, so it skips the invitation entirely and should only run where the credential is generated and delivered securely. - **Update User** Changes a user's details. Cflow requires the name, email, roles, and employee number on every update, so a flow reads the user first and sends back whatever should not change. - **Enable User** Reactivates a disabled user. - **Disable User** Deactivates a user, which stops them signing in while leaving their records in place. It is the reversible alternative to removing somebody. - **Reset User Password** Sets a user's password to a given value. It changes the credential rather than emailing a reset link, so the person cannot sign in until the new password reaches them. ### Roles 7 - **List Roles** Returns every role defined in the account. - **List User Roles** Returns the roles assigned to one person. - **Create Role** Creates a role. - **Delete Role** Deletes a role. Cflow carries the identifiers in a body on this call and wants both the role identifier and its name. - **Assign Role** Gives a role to a user, adding to the roles they already hold. - **Remove Role** Takes a role away from a user. Roles decide what a person may approve, so removing one can leave a record with nobody able to act on it. - **Check User Role** Answers whether a user holds a given role, which is a single call for a permission branch rather than listing and filtering in the flow. ### Teams 5 - **List Teams** Returns every team in the account. - **List Team Members** Returns the people in one team. - **Create Team** Creates a team and puts people in it. Teams are what the my-team visibility scope resolves against, so membership decides which records a person can see. - **Update Team** Renames a team or changes who is in it. The member list is complete and replaces the existing one, so omitting somebody removes them. - **Delete Team** Deletes a team. Cflow carries the team in a body on this call and wants the name as well as the identifier. ### Stage access 2 - **Get Stage Access** Returns the access configuration of every stage in a workflow: which role acts there, what records it can see, and what it may edit. - **Update Stage Access** Sets which role acts at a stage and what it may see and edit. This changes who can read and alter real records, which is why it sits behind this page's human gate. ## Frequently Asked Questions ### What can FlowRunner do with Cflow? FlowRunner agents can run List Workflows, List Workflow Stages, and List Fields in Cflow, plus 50 more actions. ### Does connecting Cflow to FlowRunner require OAuth? No. Cflow connects to FlowRunner with an API key, no OAuth flow required. ### Can Cflow trigger a FlowRunner workflow automatically? Cflow doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Cflow?** This integration exposes Cflow 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/cflow. Site index: https://flowrunner.ai/llms.txt