--- title: "OneDeck Integration" description: "OneDeck is a no-code business management platform built on boards holding records, plus generated documents such as work orders and quotes. Agents read and write records on any board and pull the documents produced from them." url: https://flowrunner.ai/integrations/onedeck date_modified: 2026-09-04T14:21:17-07:00 --- # OneDeck [Project Management](https://flowrunner.ai/integrations/category/project-management-productivity) OneDeck is a no-code business management platform built on boards holding records, plus generated documents such as work orders and quotes. Agents read and write records on any board and pull the documents produced from them. 12 actions · API key · available [OneDeck website](https://onedeck.com/) · [Platform Documentation](https://onedeck.com/) · Capability data verified 2026-08-18 1. A job is marked finished in the field system, or a schedule reaches the end of the week 2. List Board Fields reads the board's field identifiers, because record values are addressed by identifier and not by name 3. List Records narrows the board to the jobs that claim to be complete 4. Get Record pulls each candidate in full, including its attachments and when it last changed 5. Update Record writes the completion date and the signed-off flag back onto the record 6. The resolved set and its count are posted to the operations channel alongside the documents about to be closed 7. An operator confirms the set is the intended one before Update Document closes or cancels anything ## What This Integration Enables OneDeck is a no-code business management platform built on boards, and a board is a table of records with its own fields. That much is familiar. What makes OneDeck a system of record rather than a spreadsheet is the second half: documents. Work orders, quotes and invoices are generated in a document builder from the records on those boards, which means the board holds the state of the work and the document is the artifact somebody outside the company receives. FlowRunner agents work both halves. They read boards and their field definitions, create and update records, upload attachments, and read and close the documents the records produced. The connector is deliberately small, and it has no delete operation anywhere. That is not a gap to work around, it is the shape of the surface: an agent can add to a OneDeck account and change what is already there, but it cannot destroy. The pressure moves accordingly. The risk in a OneDeck flow is not deletion, it is scope, because OneDeck accepts a badly formed filter and answers with the whole board instead of an error. An agent has no way to tell a correctly narrowed result set from an unnarrowed one, which is precisely the sort of blind spot that should end in a person rather than in a sweep. ### Without FlowRunner **Boards are read by hand**: Somebody opens the board every Friday and eyeballs which jobs finished and which quotes went cold **Documents drift from records**: The work order says open long after the work stopped, because closing it is a separate task nobody owns **Field identifiers block automation**: Anything scripted against OneDeck breaks the first time a board's fields change, because values are keyed by identifier ### With FlowRunner **Boards are read on a schedule**: Records are narrowed, pulled in full and reconciled without anyone opening the account **Documents close when the work does**: The record write and the document close are one flow, and the second waits on a person **Field identifiers are resolved first**: Every write starts by reading the board's fields, so a renamed or added field is discovered rather than assumed ## Use Case Scenarios ### Quotes that chase themselves On a schedule, the agent calls List Board Fields to resolve the identifiers on the sales board, then List Documents narrowed by type and date to find quotes issued more than a fortnight ago. For each one, Get Document reads the recipient, the serial number and the amount, and Get Record pulls the customer record it was built from. The agent drafts a follow-up per quote and sends it through [Gmail](https://flowrunner.ai/integrations/gmail-service), then writes the contact date back with Update Record so the next run does not chase the same person twice. Nothing about the quote itself changes until somebody decides it should. ### The field job that closes its own paperwork A completion signal arrives from the scheduling system. The agent finds the matching record with List Records, confirms it with Get Record, and calls Upload Attachment to pull the signed job sheet from its public address onto the record. Update Record stamps the completion date and the technician. The generated work order is then closed with Update Document, which is the operation that tells OneDeck the work the document describes is finished. The record and the document move together, which is the whole point of doing this in one flow rather than two. ### A shared view a client can actually see When a project reaches the stage where the client should be watching it, the agent assembles the summary from List Records and Get Document, posts it to [Slack](https://flowrunner.ai/integrations/slack) for the account owner to read, and holds. On approval, Invite To Share Studio issues the invitation and returns the registration link, which the flow then delivers through the client's usual channel. The invitation goes to a real person and grants them sight of live board data, so the owner names the recipient rather than the agent inferring one from a field. ## Human-in-Loop Highlight Update Document is the operation that closes or cancels a work order, a quote or an invoice, and it is where the OneDeck gate belongs, for a reason that is specific to this API. OneDeck takes its list filters as a single query parameter holding a JSON encoded array. Send them any other way and OneDeck does not complain: the call succeeds and returns the whole board. An agent asking for "the three work orders whose jobs closed this week" and an agent accidentally asking for "every work order in the account" get responses that look identical, and there is no error to catch. The agent cannot tell those two situations apart, so it does not try to. It posts the resolved set with its count and the filter it used: "Twelve work orders matched. Expected three to five for a normal week. Close them, or should I re-check the filter?" An operator looks at the number and answers. The one thing an agent should never do is act confidently on a result set it has no way to validate. 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 12 actions ### Boards and Fields 2 - **List Boards** Retrieves the account's boards. A board is a table of records with its own fields, and it is the container everything else hangs off. - **List Board Fields** Retrieves the fields defined on a board, including the options a choice field offers. Read this before writing a record, because OneDeck addresses record values by field identifier rather than by name, and a board whose fields have changed is discovered here rather than at the write. ### Records 5 - **List Records** Retrieves the records on a board, optionally narrowed by field values. The lookup behind every reconciliation and reporting flow. - **Get Record** Retrieves one record in full, including its attachments and when it was last changed. Used to gather the whole picture before a decision rather than acting on a list row. - **Create Record** Creates a record on a board, with field values addressed by the identifiers List Board Fields returns. The new record's identifier comes back under its own key rather than as an ordinary id. - **Update Record** Changes field values on a record. Only the fields supplied are touched, and the record's own name is changed by supplying a field whose identifier is the word name. - **Upload Attachment** Uploads a file from a public address and attaches it to a record. OneDeck takes the raw bytes as the request body and the file name from a header, which this connector handles so a flow can pass a URL and move on. ### Documents 3 - **List Documents** Retrieves the account's documents, optionally narrowed by type, recipient, date, serial number or amount. This is how a flow finds the quotes, work orders and invoices that need attention. - **Get Document** Retrieves one document, such as a work order, quote or invoice built in the document builder, with the detail a follow-up or a reconciliation needs. - **Update Document** Closes or cancels a document, or links it to a record. This is the operation a flow reaches for when the work a document describes is finished, and the one this page's human gate exists for. ### People and Sharing 2 - **List Users** Retrieves the people in the account, with their email addresses and whether they are still active. Used to resolve an owner before a record is assigned or a notification is routed. - **Invite To Share Studio** Invites somebody to a shared view and returns the registration link to send them. This creates an invitation for a real person and grants sight of live board data, so a flow should point it only at addresses it was told to reach. ## Frequently Asked Questions ### What can FlowRunner do with OneDeck? FlowRunner agents can run List Boards, List Board Fields, and List Records in OneDeck, plus 9 more actions. ### Does connecting OneDeck to FlowRunner require OAuth? No. OneDeck connects to FlowRunner with an API key, no OAuth flow required. ### Can OneDeck trigger a FlowRunner workflow automatically? OneDeck doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at OneDeck?** This integration exposes OneDeck 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/onedeck. Site index: https://flowrunner.ai/llms.txt