LiquidPlanner

LiquidPlanner, now sold as Tempo Portfolio Manager, is predictive project management built on ranged estimates and a scheduling engine. Agents create and update projects, tasks and assignments, adjust estimates and read the schedule to keep forecasts honest.

43 actions API key available

LiquidPlanner website Platform Documentation Capability data verified 2026-08-18

An approved company closure or a team absence lands in the HR system

Agent reads the dates, the people affected and whether the closure covers everyone

List Time Off confirms the dates are not already blocked from an earlier sync

Agent resolves each person against List Workspace Users before touching capacity

Create Time Off records personal absences for the individuals it matched

Agent posts the resulting change in scheduled finish dates to the delivery channel

A workspace-wide closure waits for the delivery lead to confirm before it is written

What This Integration Enables

LiquidPlanner takes a position most planning tools avoid: an estimate is a range, not a date. Low effort and high effort are the optimistic and pessimistic ends, and the scheduling engine turns them into probabilistic finish dates. That makes the product only as honest as the numbers feeding it, which is exactly the kind of upkeep nobody has time to do by hand. FlowRunner agents keep those numbers current. They create and update items, correct remaining estimates as work progresses, book time from wherever it was actually recorded, and read the resulting schedule back out for anyone who needs to know when the work lands.

The model to understand first is that everything plannable is an item. Packages, projects, folders, tasks and assignments are rows in one collection told apart by their type, and an item records only its immediate parent, so List Item Ancestors is how a workflow discovers which project and package a task belongs to. The other thing to understand is that writes here move the plan. Booking time also updates an item's remaining estimate, and blocking dates for everyone closes the workspace. Agents do that work continuously; the writes that reschedule other people wait for a person, which is what human-in-the-loop is for.

Without FlowRunner

Estimates as single numbers A plan built on one date per task hides how much uncertainty is really in it

Capacity known too late Absences reach the schedule after the commitments built on that capacity were made

Forecasts rebuilt by hand Someone reassembles the delivery picture in a spreadsheet whenever a client asks

With FlowRunner

Ranges that carry the risk Low and high effort stay current, so the finish dates reflect what the team actually knows

Capacity arrives with the absence Approved time off reaches the workspace as it is granted rather than after the fact

The forecast reports itself Items, ancestors and logged time are read on a schedule and summarized where the team reads it

Use Case Scenarios

Approved absence reaches the schedule the day it is approved

An absence approved in Personio or agreed in a thread in Slack reaches the agent. It resolves the person with List Workspace Users, checks List Time Off so the same days are not blocked twice, and calls Create Time Off for that account. The scheduling engine reflows the affected assignments, and the agent reads the changed finish dates back with List Items and posts the ones that moved past a commitment date. When the request is a company closure rather than one person's leave, the agent stops and asks, because that write reaches everybody.
Time booked where the work happened, estimates corrected as it goes

Engineers log their hours in the tool they already have open. On a schedule, the agent reads those entries, resolves each one to an item, and calls Create Logged Time Entry against it. That call is not a passive record in LiquidPlanner: it also updates the item's remaining estimate, which is how the plan learns. Where the remaining range no longer looks credible against the hours already spent, the agent flags the item rather than silently rewriting it, and the owner adjusts Low Remaining and High Remaining themselves.
The delivery report that assembles itself

Every Monday the agent reads List Items filtered to the projects in flight, walks List Item Ancestors to attach each task to its project and package, pulls List Logged Time Entries for the period and calls Export Timesheet for the range. It writes the result into Google Sheets and posts a short summary naming the projects whose finish dates moved, the assignments now waiting on a dependency, and the people whose upcoming capacity is already spoken for. Nobody exports anything.

Human-in-Loop Highlight

Create Time Off has two shapes, and only one of them is a personal record. Choosing Everyone blocks those dates for every person in the workspace, which closes the office in the eyes of the scheduling engine and pushes every commitment behind it. Editing one account afterwards does not undo it. So when an agent picks up a closure request, it prepares the write and stops: "The request reads as a company closure for December 24 to January 1. Recording that as Everyone time off blocks those dates for all 46 people in the workspace and moves 12 assignments past their committed finish dates, including two on the Northwind rollout. Confirm as a workspace closure, or record it as personal time off for the 9 named people instead?" The delivery lead answers in the channel and the agent writes exactly that. Individual absences flow through untouched. The write that reschedules everybody is a decision, so a person makes it.

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

43 actions

Account and People

Get Organization Returns the organization the token belongs to. The cheapest connection check, and it needs no workspace.
List Workspaces Returns the workspaces the token can reach. Every other operation is workspace scoped, so this is the first call in most flows.
List Organization Users Returns the people in the organization across every workspace.
Get User Returns one person in the organization. Used to resolve an owner or an assignee before a write.
Create User Adds a person to the organization. The type decides both cost and access: a member is licensed and can sign in, a resource is capacity without a login, and a placeholder is unnamed capacity for planning.
Update User Changes a person's details or type.
List Workspace Users Returns the people in one workspace, which is a narrower set than the organization's. The lookup behind every absence and assignment write.
Get Workspace User Returns one person's membership of a workspace with the settings that apply there.
List Groups Returns a workspace's groups, which gather people into teams for planning and permissions.
List Group Members Returns the people in one group. Used to resolve a team into individuals before capacity work.

Items

List Items Returns a workspace's items. Packages, projects, folders, tasks and assignments all live here, told apart by item type, so filtering by type is how a workflow asks for one kind.
Create Item Creates a package, project, folder, task or assignment. The parent decides where it lands, and the status vocabulary depends on the type.
Update Item Changes the properties supplied and leaves the rest alone. Where estimate ranges and statuses are corrected as work progresses.
Delete Item Deletes an item and everything under it. Worth reviewing before it runs against anything with children.
Duplicate Item Copies an item, optionally under a different parent and at a chosen place in the priority order. The fast path for a repeatable project shape.
List Item Ancestors Returns the chain of items above one item up to the workspace root. Because an item records only its immediate parent, this is how a task's project and package are found.
List Item Story Points Returns the story points recorded on an item.
Remove Item Custom Field Clears one custom field from an item, chosen by name. Leaving the name empty clears every custom field on the item, which is a different route and a deliberate act.

Dependencies

List Item Dependencies Returns what an item waits on and what waits on it.
Create Item Dependency Makes one item wait on another. A predecessor is what this item waits for and a successor is what waits on it, and reversing them reverses the schedule.
Delete Item Dependency Removes a dependency, freeing the item to be scheduled independently.

Files

List Item Files Returns the files attached to an item.
Download Item File Fetches a file attached to an item into FlowRunner file storage and returns a URL later steps can use.
Move Item File Moves a file from one item to another.
Delete Item File Removes a file from an item.

Time

List Logged Time Entries Returns booked time. The read behind utilization reporting and invoice preparation.
Get Logged Time Entry Returns one booked time entry.
Create Logged Time Entry Books time against an item, and updates that item's remaining estimate at the same time. Logging time here moves the schedule rather than just recording history.
Update Logged Time Entry Changes booked time, and updates the remaining estimate with it.
Delete Logged Time Entry Removes booked time, which also changes the remaining estimate and therefore the plan.
List Time Off Returns time off. Everyone entries close the whole workspace for those dates and personal entries cover one account, and they are separate records.
Create Time Off Records time off. Choosing Everyone blocks the dates for every person in the workspace, which is the operation this page's human gate exists for.
Update Time Off Changes a time off entry.
Delete Time Off Removes a time off entry, returning that capacity to the schedule.

Rates and Codes

List Rate Sheets Returns the rate sheets that decide what work is billed and paid at.
Create Rate Sheet Adds a rate sheet. A sheet is either a billing rate or a pay rate, and the two are not interchangeable.
Create Rate Rule Adds a rule to a rate sheet, setting the number that applies to a person or a role.
List Rate Rules Returns the rules on a rate sheet, which are what actually set the numbers.
Delete Rate Rule Removes a rule from a rate sheet. A change that reprices future work, so it belongs in a reviewed flow.
List Cost Codes Returns the cost codes an item's time can be booked to.
List Task Statuses Returns the statuses a task can be in. Read this before setting a status, since the identifiers are per workspace.

Exports

Export Timesheet Returns the timesheet as data. It defaults to the past month, so give an explicit date range when a workflow needs a different period.
Download Export Renders one of LiquidPlanner's spreadsheet exports into FlowRunner file storage and returns a URL later steps can use.

Frequently Asked Questions

What can FlowRunner do with LiquidPlanner?

FlowRunner agents can run Get Organization, List Workspaces, and List Organization Users in LiquidPlanner, plus 40 more actions.

Does connecting LiquidPlanner to FlowRunner require OAuth?

No. LiquidPlanner connects to FlowRunner with an API key, no OAuth flow required.

Can LiquidPlanner trigger a FlowRunner workflow automatically?

LiquidPlanner doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with LiquidPlanner

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us