--- title: "Plutio Integration" description: "Plutio is the all-in-one business app for freelancers and small agencies: projects, tasks, time, clients, invoices and files in one workspace. Agents create and update projects and tasks, log time, manage clients and issue invoices from a single connection." url: https://flowrunner.ai/integrations/plutio date_modified: 2026-09-04T14:21:17-07:00 --- # Plutio [Project Management](https://flowrunner.ai/integrations/category/project-management-productivity) Plutio is the all-in-one business app for freelancers and small agencies: projects, tasks, time, clients, invoices and files in one workspace. Agents create and update projects and tasks, log time, manage clients and issue invoices from a single connection. 82 actions · OAuth · available [Plutio website](https://plutio.com/) · [Platform Documentation](https://www.plutio.com/) · Capability data verified 2026-08-18 1. The billing week closes, or a project reaches the stage that triggers a draw 2. List Time Entries pulls the period's logged seconds, narrowed by project and billing state 3. List Projects reads which of those projects are billable and at what rate they were set up 4. List Tasks confirms the work behind the hours actually reached a done status 5. Create Invoice raises the invoice for the client, and its lines are added afterwards as blocks 6. The assembled totals and the entries behind them are posted to the person who owns the account 7. That person approves what the period bills before Bulk Update Time Entries marks any of it ## What This Integration Enables Plutio's whole proposition is that a freelancer or a three-person agency should not be running five subscriptions to do one job. Projects, tasks, time, clients, invoices, notes and files live in one workspace, and the person doing the work is usually the same person doing the admin. That is a specific kind of customer, and it changes what automation is for: the value is not coordinating a large team, it is giving one operator a back office they do not have to staff. FlowRunner agents create and copy projects, move tasks between boards and groups, log and reconcile time, manage clients and companies, and raise invoices and record the payments against them. The API's shape is unusual and worth understanding, because it explains why the risky operations here are the ones they are. Plutio has no per-record paths: a single record is addressed by posting its identifier to the collection, so update, delete, archive and move all speak to the same endpoint. That design is also why the connector carries a family of bulk operations, on companies, projects, tasks and time entries, each taking a list of identifiers and applying one set of changes across all of them. A bulk write is efficient, and it is also a single call that commits a judgment about many records at once with no per-record confirmation, which is exactly the sort of operation FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) design puts a person in front of. ### Without FlowRunner **One person is the whole back office**: The same freelancer doing the work also reconciles the timesheet, raises the invoice and chases it **Billable and non-billable blur**: Hours get marked billed by memory at the end of a month, which is when the ambiguous ones get decided **Client-facing writes have no draft stage**: The invoice email goes out the moment somebody has the energy to send it, correct or not ### With FlowRunner **The back office runs without being staffed**: Hours, tasks and projects are read and reconciled on a schedule, not when somebody finds the time **Billable state decided against evidence**: Each entry is matched to a task and a project rate before anything is marked, and the ambiguous ones are named **Client-facing writes wait for a yes**: The invoice is drafted, the totals are shown, and the send happens after somebody agrees with the number ## Use Case Scenarios ### A repeatable engagement stood up from the last one A new client agrees to the same package the previous one bought. The agent calls Create Company to group the client's contacts under one organization, adds the people with Create Person at the client role so their view of the workspace is limited, and then Copy Project on the engagement that already ran. Copy Task Board brings the standard delivery board across if the copy settings did not carry it. Create Task adds the client-specific items, with Assigned To sent as a list because Plutio lets several people own one task, and Set Custom Field Value writes the account code that the reporting later keys on. The whole setup takes one flow and no clicking. ### A workspace that keeps itself clean Plutio distinguishes archiving from deleting on almost every record, and the agent uses that distinction deliberately. On a schedule it finds projects with no open tasks and no time logged for a month, checks each one with List Tasks, and calls Archive Project rather than Delete Project so the history survives. Finished boards are cleared with Bulk Archive Tasks in a single call rather than one per card. People who have left are archived through Archive Person, which keeps everything they are attached to. Nothing in this flow is destructive, which is what makes it safe to run unattended, and the deletes are left for a person who has decided the record genuinely should not exist. ### Payments recorded where the money actually landed A bank transfer clears, seen through [Stripe](https://flowrunner.ai/integrations/stripe) or reconciled from a feed in [Xero](https://flowrunner.ai/integrations/xero). The agent finds the matching invoice with List Invoices, using a query rather than a plain field match so it can select on amount and date together, then calls Record Invoice Payment. Plutio updates the amount paid and moves the invoice's status itself. A note goes onto the client record with Create Note so the context is findable later, and a line appends to a sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) for the operator who prefers to look at cash in one place. Reconciliation stops being a monthly session. ## Human-in-Loop Highlight Bulk Update Time Entries is the operation this connector should never run unattended, and the reason is what it actually decides. It applies one set of changes across a list of time entries in a single request, which is how a week of work is marked billed without a call per entry. That means a single call settles what a period bills, before any invoice exists and before anybody sees a number. The agent does the work leading up to it well: it reads every entry with List Time Entries, matches each to its task and project, checks whether the project is billable and at what rate, and separates the clean entries from the ones where the task never reached a done status or the project rate was never set. Then it stops. "Week ending 12 September: 61 entries, 38.5 hours. 34 entries are clean and billable at the project rate. 5 entries totaling 4.2 hours sit on tasks still in progress. 2 entries have no project and no rate. Mark the 34 billed, or should the other 7 be resolved first?" The operator answers once, the bulk write runs on the approved set, and Email Invoice, which reaches a real inbox outside Plutio, happens downstream of a number somebody agreed with. 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 82 actions ### Connection and Workspace 3 - **Verify Credentials** Checks the Plutio connection by exchanging the client credentials for an access token and reading the workspace behind it. The first call to make when calls are being refused, because it separates a credential problem from a header problem. - **Get Workspace** Returns the workspace this connection belongs to, with its name, currency, address and the settings that decide how invoices, proposals and tasks behave. Everything else in Plutio hangs off a workspace, and one connection covers exactly one. - **Update Workspace** Updates the workspace name, currency or about text. Only the properties supplied change, and the nested option groups pass through as given. ### People 6 - **List People** Returns the people in the workspace: clients, collaborators and team members alike, since Plutio keeps them all as people and tells them apart by role. A query expression handles anything a plain field match cannot, including text search. - **Create Person** Adds a person to the workspace. The role decides what they can see, and client is the usual one for somebody outside the team. - **Update Person** Updates a person. Only the properties supplied change, and the identifier travels in the body because Plutio has no path for a single record. - **Delete Person** Permanently removes a person from the workspace. Archive Person keeps their history and takes them out of the main views instead. - **Archive Person** Archives a person, taking them out of the main views while keeping everything they are attached to. Fully reversible. - **Get Invitation Code** Returns the invitation code for a person, which is what lets somebody outside the team join the workspace as themselves rather than being added by hand. ### Companies 5 - **List Companies** Returns the companies in the workspace. A company groups people, so a client organization with several contacts is one company holding several people. - **Create Company** Creates a company and optionally puts people in it straight away, so an invoice can be addressed to the organization rather than to a person. - **Update Company** Updates a company. Only what is supplied changes, and the people list replaces the whole membership rather than adding to it. - **Delete Company** Permanently removes a company. The people who were grouped under it stay in the workspace. - **Bulk Update Companies** Applies changes to several companies in one request, each entry naming a record and the fields to change on it. The way a batch import stays inside Plutio's hourly request budget. ### Projects 8 - **List Projects** Returns the projects in the workspace, with their clients, contributors, budget, dates and task counts. A query expression finds a project by name or by a custom field value. - **Create Project** Creates a project. Clients are the people it is being done for and contributors are the people doing it, which is the distinction Plutio uses to decide what a client can see. A billable project carries the rate that time entries are costed against. - **Update Project** Updates a project. Only what is supplied changes, and the people lists replace rather than add to what is there. - **Delete Project** Permanently deletes a project along with its boards, groups and tasks. Archive Project keeps all of it and takes the project out of the main views instead. - **Archive Project** Archives a project, taking it out of the main views while keeping its data. The reversible way to close an engagement down. - **Copy Project** Copies a project, which is how a repeatable engagement is stood up from one that already ran. Plutio copies the structure, and the workspace's own copy settings decide what else comes across. - **Move Project** Changes where a project sits in the workspace's ordering. - **Bulk Update Projects** Applies changes to several projects in one request, each entry naming a record and the fields to change on it. ### Task Boards 5 - **List Task Boards** Returns the task boards of a project, or of the whole workspace when no project is given. A board holds groups and a group holds tasks, which is the three level structure Plutio arranges work in. - **Create Task Board** Creates a task board inside a project. - **Update Task Board** Renames a task board or recolors it. Only the properties supplied change. - **Delete Task Board** Permanently deletes a task board along with the groups and tasks inside it. - **Copy Task Board** Copies a task board, optionally into a different project, which is how a standard workflow is reused across engagements. ### Task Groups 5 - **List Task Groups** Returns the task groups of a board, or of the whole workspace when no board is given. A group is the column a task sits in. - **Create Task Group** Creates a task group on a board. Marking one as the default puts new tasks there when none is named. - **Update Task Group** Renames a task group, recolors it or makes it the default. - **Delete Task Group** Permanently deletes a task group along with the tasks inside it. - **Move Task Group** Moves a task group to another board, to another position, or both. ### Tasks 9 - **List Tasks** Returns tasks, narrowed by project, board, group, status or assignee. Because a task's assignees are an array, filtering by one person is a containment query rather than an equality one, and unassigned work is found by asking for an empty array. - **Create Task** Creates a task. It belongs to a project through its board and group, several people can own it, and naming a parent task is what makes it a subtask. - **Update Task** Updates a task. Only the properties supplied change, and the assignee list replaces the whole list rather than adding to it. - **Delete Task** Permanently deletes a task and its subtasks. Archive Task keeps the record. - **Archive Task** Archives a task, taking it off the board while keeping its history, comments and time entries. Fully reversible. - **Copy Task** Copies a task, optionally into another group. Useful for recurring work that is not worth a template. - **Move Task** Moves a task to another group or another position, which is what dragging a card between columns does. - **Bulk Update Tasks** Applies changes to several tasks in one request, so reassigning a sprint or closing a batch is one call rather than one per task. That matters against Plutio's hourly request budget. - **Bulk Archive Tasks** Archives or restores several tasks at once, which is how a finished board is cleared without a call per card. ### Statuses 5 - **List Statuses** Returns the statuses defined in the workspace. Statuses are per record type rather than per project, so one set applies to tasks and another to invoices. - **Create Status** Creates a status for one kind of record. Its kind decides which of the three board groupings it falls under, so a status of the done kind marks work finished however it is named. - **Update Status** Renames a status, recolors it or changes which grouping it belongs to. Every record carrying it is updated at once. - **Delete Status** Removes a status from the workspace. Records that carried it lose it, so check what uses it first. - **Move Status** Changes where a status sits in its list, which is the order it appears in on a board. ### Time Tracking 5 - **List Time Entries** Returns logged time, narrowed by project, task, person or billing state. Plutio stores the amount in seconds, and a flag distinguishes a typed entry from one a running timer produced. - **Create Time Entry** Logs time against a task or a project, in seconds. The start and stop timestamps record when the work happened, which is what a timesheet report groups by. - **Update Time Entry** Updates a logged time entry. Only the properties supplied change, and the duration is still in seconds. - **Delete Time Entry** Permanently removes a logged time entry. - **Bulk Update Time Entries** Applies changes to several time entries in one request, which is how a week of work is marked billed without a call per entry. The operation this page's human gate exists for, because one call settles what a period bills. ### Categories 4 - **List Categories** Returns the categories in the workspace. A category groups records of one kind, and its scope says which kinds it applies to. - **Create Category** Creates a category for one kind of record. - **Update Category** Renames a category or changes its description. - **Delete Category** Removes a category. Records filed under it lose the category but are otherwise untouched. ### Custom Fields 5 - **List Custom Fields** Returns the custom fields defined in the workspace, each with the kind of record it applies to and the sort of value it holds. This is what tells a flow the field identifiers a task or project write needs. - **Create Custom Field** Creates a custom field for one kind of record. A dropdown or multi select needs its options as well, and marking it added by default puts it on every new record of that kind. - **Update Custom Field** Renames a custom field or changes its choices. The record kind and the value type cannot be changed once records carry it. - **Delete Custom Field** Removes a custom field from the workspace, along with the values every record held for it. - **Set Custom Field Value** Puts a custom field's value on one record, adding the field to that record if it is not already there. The targeted alternative to sending the whole custom field list on an update, which replaces every value at once. ### Comments 4 - **List Comments** Returns the comments on one record. The record type and the record together say what to read them from, because Plutio keeps comments in one place for every kind of record. - **Create Comment** Adds a comment to a record. Mentions notify the people named, and marking a comment as a note keeps it internal, which is how a team holds a remark back from a client's view of the same record. - **Update Comment** Edits a comment's text. - **Delete Comment** Permanently removes a comment. ### Notes 4 - **List Notes** Returns notes, optionally only those attached to one record. A note is longer than a comment and can stand on its own. - **Create Note** Creates a note, optionally attached to a record. Attaching one to a project or a person is how background that is not a task becomes findable. - **Update Note** Updates a note's title or body. Only the properties supplied change. - **Delete Note** Permanently removes a note. ### Files and Folders 7 - **List Files** Returns files, optionally only those in one folder or attached to one record, each with a URL, a size and a type. - **Create File** Registers a file in Plutio from a URL. This records a file already hosted elsewhere rather than uploading bytes, so the URL has to stay reachable. - **Delete File** Permanently removes a file record from Plutio. Where the file itself is hosted is not affected. - **Download File** Downloads a Plutio file into FlowRunner file storage and returns its URL for later steps to use. - **List Folders** Returns the file folders in the workspace, optionally only those inside one parent. Folders nest, so a parent identifier walks the tree one level at a time. - **Create Folder** Creates a file folder, optionally inside another one or attached to a record. - **Delete Folder** Permanently removes a folder along with what is inside it. ### Invoices 7 - **List Invoices** Returns invoices with their client, totals, dates and payment state. A query expression selects on more than a plain field match, for example everything issued in a date range. - **Create Invoice** Creates an invoice for a client. The line items are not part of this call: Plutio keeps an invoice's content as separate block records, so the invoice is created first and its lines added afterwards. - **Update Invoice** Updates an invoice's name, dates, currency or status. Only the properties supplied change. - **Delete Invoice** Permanently deletes an invoice. Archive Invoice keeps the record for the books. - **Email Invoice** Sends an invoice to its recipients by email. This reaches real inboxes outside Plutio and cannot be recalled from them, so the recipient list and the total are both worth confirming before a flow runs it. - **Record Invoice Payment** Records a payment against an invoice, which is how money taken outside Plutio gets onto the books. Plutio updates the amount paid and the invoice status itself. - **Archive Invoice** Archives an invoice, taking it out of the main views while keeping it for the books. Fully reversible. ## Frequently Asked Questions ### What can FlowRunner do with Plutio? FlowRunner agents can run Verify Credentials, Get Workspace, and Update Workspace in Plutio, plus 79 more actions. ### Does connecting Plutio to FlowRunner require OAuth? Yes. Plutio connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Plutio trigger a FlowRunner workflow automatically? Plutio doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Plutio?** This integration exposes Plutio 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/plutio. Site index: https://flowrunner.ai/llms.txt