--- title: "Celoxis Integration" description: "Celoxis is a project and portfolio management suite for planning, tracking and reporting on projects at scale. Agents create projects and tasks, post task updates, log time and expenses, manage users and read and write the account's custom apps." url: https://flowrunner.ai/integrations/celoxis date_modified: 2026-09-04T14:21:17-07:00 --- # Celoxis [Project Management](https://flowrunner.ai/integrations/category/project-management-productivity) Celoxis is a project and portfolio management suite for planning, tracking and reporting on projects at scale. Agents create projects and tasks, post task updates, log time and expenses, manage users and read and write the account's custom apps. 49 actions · API key · available [Celoxis website](https://www.celoxis.com/) · [Platform Documentation](https://www.celoxis.com/) · Capability data verified 2026-08-18 1. A signed statement of work lands in the contract system 2. Agent reads the client, the delivery dates, the named manager, and the fee schedule 3. Create Project opens the engagement, resolving manager and client by name rather than by ID 4. Create Records builds the task tree with allocations set per assignee 5. List Tasks confirms the plan totals match the hours the statement of work was priced on 6. The delivery lead gets the plan and the variance called out 7. The delivery lead confirms the allocation before anyone is scheduled against it ## What This Integration Enables Celoxis is built for teams whose project plan is also a financial record. Hours, expense claims, custom risk and issue registers, and the people who can be billed out all hang off the same small set of entities, which is why the API repeats one shape across all of them: query, fetch, create, update, delete, upsert, clone. FlowRunner agents work that shape directly. They open projects from approved scopes, build task trees with per-person allocations, post progress updates that move percent complete, log time and expenses against the right work item, and read and write the custom apps where a team keeps its risks, issues, and change requests. The operation that makes Celoxis a genuine sync target is Upsert Record, which matches on an External Key you own rather than a Celoxis ID. A billing system, a CRM, or a ticketing queue can therefore push the same record repeatedly without keeping a mapping table and without ever creating a second copy. That removes the usual reason a sync goes wrong. It does not remove the reason FlowRunner keeps a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) gate on this connector, which is that some of these writes are permanent and Celoxis will carry them out without asking. ### Without FlowRunner **Plans rebuilt by hand**: Every new engagement starts with someone retyping a signed scope into the planner **Time and money in separate places**: Hours live in the plan, spend lives in a spreadsheet, and the two are reconciled late **Portfolio views built from exports**: Rolling up status means pulling reports and pasting them into a deck ### With FlowRunner **Plans opened from the signed scope**: The contract that priced the work also seeds the project, the tasks, and the allocations **One record carries both**: Time entries and expense reports attach to the same project structure the plan uses **Portfolio state queried live**: Roll-ups read current records instead of last week's export ## Use Case Scenarios ### The signed scope opens the project A statement of work is countersigned in [DocuSign](https://flowrunner.ai/integrations/docusign) and the agent picks up the executed copy. It reads the client, the phases, the delivery window, and the named engagement manager, then calls Create Project, passing manager and client as the names they appear under in Celoxis rather than looking IDs up first. Create Records builds the phase and task tree in one call, with Resources expressed in Celoxis notation so each assignee carries the allocation the pricing assumed. Get Project Manager confirms the plan landed under the right owner, and a summary posts to the delivery channel in [Slack](https://flowrunner.ai/integrations/slack). What used to be an afternoon of retyping is now a plan that matches the document it was priced from. ### Time and expenses reconciled before they become an invoice On a weekly schedule the agent calls List Time Entries and List Expenses for the billing period, joins them to their projects, and compares the totals against the plan with List Tasks. Entries booked against no work item, expense reports whose items carry no expense code, and tasks that are over their allocation get pulled into an exception list rather than passed through. The clean lines append to a sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) for the invoice run, and the exceptions go to the project accountant with the specific record and the specific field named. The reconciliation runs every week without a person starting it, and a person only reads the part that disagrees. ### A risk register that fills itself Celoxis keeps risks, issues, and change requests in the account's custom apps, which means the shape of a team's register is whatever that team modeled. An agent watching a support queue in [Zendesk](https://flowrunner.ai/integrations/zendesk) or a monitoring feed in [Sentry](https://flowrunner.ai/integrations/sentry) classifies incoming items, and for anything that meets the threshold calls Create App Item against the right app with the custom fields that app defines. List App Items then feeds a weekly digest of open risks by project. The register stops being the thing everyone forgets to update after the status meeting. ## Human-in-Loop Highlight Celoxis draws its own line about what an API may destroy: users and clients cannot be deleted through it at all. It draws no such line around projects, and Delete Project removes the project and everything under it, including the tasks, the progress notes people posted, and the time and expense records booked against them. That is a financial history, not just a plan. So a cleanup agent working through stale engagements never calls it directly. It gathers the evidence first with Get Project, List Tasks, List Time Entries, and List Expenses, then asks the portfolio owner in Slack: "Project ACME Phase 2 has had no activity for 180 days. It carries 412 logged hours across 9 tasks and 3 expense reports. Delete it, or archive the plan and keep the records?" The owner answers. The same gate governs Move Tasks, because moving a task into another project moves the logged work that hangs off it, and the machine cannot tell you which client that work belonged to. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 49 actions ### Any Entity 8 - **List Records** Queries any Celoxis entity with filters, sorting, field selection, and paging. The general-purpose read behind reporting and reconciliation flows. - **Get Records** Fetches specific records by ID in a single call. Used to hydrate a batch of IDs collected from an earlier query. - **Get Association** Fetches what a record is joined to, such as a task's predecessors or a project's clients. Used to walk relationships without a second round of queries. - **Create Records** Creates one record or several in one call. The bulk write behind opening a whole task tree from an approved plan. - **Update Record** Changes one record of any entity type. Used for status changes and enrichment passes across the portfolio. - **Delete Record** Deletes one record. Used sparingly and with review, since Celoxis does not undo it. - **Upsert Record** Creates a record or updates the one already carrying the same External Key. The default write for any sync driven by an outside system's IDs, because it cannot produce a duplicate. - **Clone Record** Copies a record, overriding whatever fields you name. Used to stand up repeatable structures from a known-good original. ### Projects 8 - **List Projects** Returns projects with filtering and paging. The entry point for portfolio reporting and health sweeps. - **Get Project** Returns one project. Used to gather full context before a decision or a write. - **Create Project** Opens a project. Manager, workspace, client, state, and type accept names as well as IDs, so an agent can open a project straight from a signed document without a lookup pass. - **Update Project** Changes a project's fields. Used to move state, adjust dates, and reflect approved scope changes. - **Delete Project** Deletes a project and everything beneath it. The operation this page's human gate exists for. - **Clone Project** Copies a project, overriding named fields. Used to launch a repeat engagement from the shape of the last one. - **Get Project Manager** Returns the person managing a project. Used to resolve the right owner before routing a decision. - **Get Project Clients** Returns the clients a project is for. Used to attribute work and route client-facing communication correctly. ### Tasks 9 - **List Tasks** Returns tasks with filtering and paging. Used for plan validation, overdue sweeps, and allocation checks. - **Get Task** Returns one task with its fields. Used before any update that depends on current state. - **Create Task** Creates a task in a project, with resources expressed in Celoxis's own allocation notation so each assignee carries a percentage rather than a bare name. - **Update Task** Changes a task. Bulk syncs set the silent option so a hundred small corrections do not produce a hundred emails to the people on those tasks. - **Delete Task** Deletes a task. Used in cleanup flows that have already been reviewed. - **Clone Task** Copies a task, overriding named fields. Used to repeat a standard work package across projects. - **Move Tasks** Moves one or more tasks into another project. Reviewed rather than automated, because the work logged against a task moves with it. - **Upsert Task** Creates a task or updates the one carrying the same External Key. The safe write for a ticketing system pushing work into a plan. - **Get Task Association** Returns what a task is joined to: its project, its parent, its predecessors, or its assignments. Used to reason about sequence before rescheduling. ### Time and Expenses 10 - **List Time Entries** Returns tracked time for a period, a project, or a person. The read behind billing reconciliation and utilization reporting. - **Get Time Entry** Returns one tracked time entry. Used to inspect a disputed line. - **Create Time Entry** Records time worked, booked against a task, against a workflow, or against neither for non-project time. Used to push hours captured elsewhere into the system that bills them. - **Update Time Entry** Changes a tracked time entry. Used for approved corrections, not for silent recategorization. - **Delete Time Entry** Removes a tracked time entry. Reserved for duplicates confirmed by a person. - **List Expenses** Returns expense reports. Used to pull the spend side of a project into the same review as the hours. - **Get Expense** Returns one expense report with its items. - **Create Expense** Creates an expense report. The money sits in the items, each carrying its own date, expense code, and amount, so an agent building one from receipts must resolve the code, not just the total. - **Update Expense** Changes an expense report. Used to attach corrected items after a review. - **Delete Expense** Deletes an expense report. Used only where a person has confirmed the report was filed in error. ### Custom Apps 5 - **List App Items** Returns items from the account's custom apps, which is where a Celoxis team keeps its risks, issues, bugs, and anything else it chose to model. - **Get App Item** Returns one app item with its custom field values. - **Create App Item** Creates an item in one of the account's custom apps. The app named on the call decides which custom fields the item accepts, so an agent reads the model before it writes to it. - **Update App Item** Changes an app item. Used to move a risk through its states as evidence arrives. - **Delete App Item** Deletes an app item. Used in reviewed cleanup of a register. ### Task Updates 4 - **List Task Updates** Returns the progress notes people have posted against tasks. Used to detect work that has stalled without anyone saying so. - **Get Task Update** Returns one progress note. - **Create Task Update** Posts a progress note against a task. Percent complete set here moves the task itself, which makes this the ordinary way an agent advances work rather than editing the task record directly. - **Delete Task Update** Deletes a progress note. ### Users 5 - **List Users** Returns the people in the account. Used to resolve owners and to check who is schedulable. - **Get User** Returns one person's record. - **Create User** Adds a person. Giving them a login counts against the account's license; leaving it empty creates a resource who can be scheduled but cannot sign in, which is the right shape for a subcontractor. - **Update User** Changes a person's details, including their schedulable status. - **Clone User** Copies one person's setup onto a new one, which is how a joiner inherits a colleague's dashboards and preferences on day one. ## Frequently Asked Questions ### What can FlowRunner do with Celoxis? FlowRunner agents can run List Records, Get Records, and Get Association in Celoxis, plus 46 more actions. ### Does connecting Celoxis to FlowRunner require OAuth? No. Celoxis connects to FlowRunner with an API key, no OAuth flow required. ### Can Celoxis trigger a FlowRunner workflow automatically? Celoxis doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Celoxis?** This integration exposes Celoxis 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/celoxis. Site index: https://flowrunner.ai/llms.txt