Float

Keep resource plans current in Float. Agents manage people, projects, tasks, and clients, and read time-off records so scheduling decisions reflect real capacity.

10 actions API key available

Float website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A deal closes won in the CRM and a kickoff date lands on the calendar

Create Project provisions the engagement in Float, tied to the client resolved through List Clients, marked billable

List Time Off reads upcoming vacations and leave for the candidate team members over the delivery window

List Tasks pulls current allocations for the same window, so the plan starts from real availability rather than assumed availability

The agent drafts a staffing plan: which people, how many hours per day, across which date ranges

Create Task books each allocation with status Tentative

The resource manager reviews the tentative bookings, reshuffles where judgment says so, and confirms the plan

The confirmed schedule posts to the project channel with people, hours, and dates named

What This Integration Enables

Float is the schedule for teams that sell hours, and for those teams the schedule is not an admin artifact, it is the inventory ledger. An unbooked hour expires worthless at the end of the week; an overbooked person pays for the error in burnout and blown deadlines. FlowRunner agents treat that ledger the way it deserves: reads happen constantly, writes happen deliberately, and commitments get a human signature. - Provision people and projects the moment onboarding or a closed deal creates them, so the schedule never lags the business - Book capacity with allocations that assign a person to a project for specific dates and daily hours - Read the live schedule and time off together to compute genuine availability before proposing anything - Feed utilization reporting and downstream planning tools from the schedule itself, not an export of it - Keep the commitment step, confirming an allocation, behind a [human-in-the-loop](/concepts/human-in-the-loop) gate

Without FlowRunner

Staffing by memory Who is free next month lives in the resource manager's head and a spreadsheet that was accurate two Fridays ago

Kickoff scramble The deal closes, then a week disappears into finding out who can actually start

Vacation surprises An allocation gets confirmed, then someone notices the lead is in Portugal for half of it

With FlowRunner

Availability as a query Agents read allocations and time off together, so every plan starts from what the schedule actually says

Projects staffed at close The engagement, the project record, and a tentative staffing plan exist the same day the deal does

Conflicts surfaced before commitment Overlaps and time-off collisions arrive flagged in the draft, while the plan is still tentative

Use Case Scenarios

The new hire who starts scheduled

A new team member appears in [BambooHR](/integrations/bamboohr). The agent calls Create Person with their name, email, job title, and department, sets the employee type, then reads the project list with List Projects to find the onboarding engagement. Create Task books their first two weeks: half days on onboarding, half days shadowing the team's active project, both entered as Tentative for the manager to confirm. The new hire's first Monday exists on the schedule before their laptop ships.

The utilization report nobody compiles

Every Friday, the agent calls List Tasks for the coming four weeks and List People for the active roster, then joins the two into a per-person picture of booked hours against working days, with List Time Off subtracted so vacations do not read as idle capacity. The result lands in [Google Sheets](/integrations/google-sheets) as a rolling utilization sheet and a summary posts to [Slack](/integrations/slack) naming the people under 50 percent booked and the people over 100. The Monday resourcing call starts from the same numbers for everyone.

Planned versus actual, without the archaeology

At month end, the agent reads the month's allocations with List Tasks and the hours actually logged in [Harvest](/integrations/harvest) for the same people and projects. It resolves each project's client and budget context with Get Project, then writes a variance summary: where actuals ran hot against plan, where booked time went unlogged, which clients absorbed the drift. The delivery lead reads a one-page discrepancy report instead of reconstructing the month from two systems.

Human-in-Loop Highlight

Create Task is where Float stops being a report and starts being a commitment. A confirmed allocation books a person's actual days against an actual project, and on billable work it commits client budget at the same stroke; booking the wrong person, or the right person twice, is an error the week absorbs whether or not anyone catches it. So FlowRunner agents write allocations as Tentative and stop. The staffing draft arrives with the evidence attached: "Proposed: Priya on Meridian rebuild, 6 hours per day, March 2 to March 27. Conflict check: she is confirmed 4 hours per day on Atlas support through March 13, and List Time Off shows approved leave March 20 to 24." The resource manager resolves the conflict and confirms. The agent did the reading; the person made the commitment.

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

10 actions

People

List People Lists team members in the Float account with pagination, including name, email, job title, department, and active status. The roster read behind availability and utilization work.
Get Person Retrieves one person's full details by ID, including employee type, hourly rate, and active status. Used to check rate and type context before proposing billable allocations.
Create Person Adds a new team member to Float with name, optional email and job title, department, and employee type. The onboarding step that makes someone schedulable.

Projects

List Projects Lists projects with pagination, including client association, color, budget type, and active status. Combined with List Clients to resolve which engagement is which.
Get Project Retrieves one project's full details by ID, including client, notes, budget, and active status. The context read before reporting on or booking against an engagement.
Create Project Creates a project, optionally tied to a client, with schedule color, notes, and billable or non-billable status. The step that turns a closed deal into a schedulable engagement.

Scheduling

List Tasks Lists scheduled allocations, filterable by person and date window. The ground truth for who is booked on what, and the input every honest staffing draft starts from.
Create Task Creates an allocation assigning a person to a project over a date range for a set number of hours per day, with optional notes and tentative, confirmed, or complete status. The core scheduling operation, and the one this page's human gate governs.

Clients

List Clients Lists clients with their IDs and names. Used to attach projects to the right client and filter reporting by relationship.

Time Off

List Time Off Lists time off entries with type, date range, and approval status. The subtraction that turns booked-versus-bench math into real availability.

Frequently Asked Questions

What can FlowRunner do with Float?

FlowRunner agents can run List People, Get Person, and Create Person in Float, plus 7 more actions.

Does connecting Float to FlowRunner require OAuth?

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

Can Float trigger a FlowRunner workflow automatically?

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

Start building with Float

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us