Skip to main content
The Float integration makes the resource schedule available in your client work. Ask who is free for three days next week, how heavily a consultant is booked in November, or whether a project has the people it needs before the readout, and Hebno answers from Float with each person, project and allocation cited. When a request implies a change, such as booking Sarah Chen on the Contoso pricing review, Hebno shows a confirmation card and writes to Float only after you confirm.

At a glance

Before you start

You need:
  • An owner or admin role in Hebno.
  • The Float account owner, or a person with the account owner’s access, to copy the API key.
  • Float time tracking turned on in your account if you want logged time in answers.
The account owner finds the API key in Float under Team settings → Integrations, in the Float API section. Float issues one key per account. It has no scopes and gives access to the whole schedule, which is why Hebno narrows what members see with teams and data areas.
Regenerating the API key in Float ends the Hebno connection straight away. If you rotate the key, paste the new one on the Float card under Admin → Connectors at the same time.

Connect Float

1

Allow the integration

Open Admin → Connectors → Catalogue, find Float under PSA, time and resourcing, and set it to Allow.
2

Connect the organisation

Select Connect, paste the Float API key, then select Test connection. Hebno checks that it can read people, projects and allocations, and shows the Float account name.
3

Choose teams and data areas

Under Who can use it, choose All teams or pick teams. Under Data areas, choose what members can see. See Data areas.
4

Set access

Leave Access on Read and write to let members propose new and changed allocations, or choose Read only.
The card shows Connected with the Float account name. Members in the selected teams can use Float in chat straight away. Float has one key per account, so members do not link their own Float accounts. Every write goes through the organisation connection, and Hebno records which member confirmed it.

Data areas

Data areas control what members of the allowed teams can see through the organisation connection.
Admin connector panel showing who can use it, access and data areas

An organisation connection with team access and data areas. Financial figures default to owners and admins.

To share budgets with resource managers, open the Float card in Admin → Connectors, select Financials and add the teams that should see them.
Hebno reads who is away and when. It does not read time off notes.

What Hebno reads

Capacity is worked out from each person’s work days and hours, minus time off and holidays, at the time of the request, so it matches the Float schedule. Reads are live. Hebno queries Float when a request needs it. Only what a reply used is stored with the conversation as its sources.

What Hebno writes

Every write appears first as a confirmation card. You can change any field before you select Confirm.
Confirmation card for Float with editable fields

A Float change pending confirmation. Nothing is written until you confirm.

The card shows a warning when an allocation would put the person into overtime or overlap their time off. Hebno never deletes allocations, adds or removes people, changes rates or budgets, or approves time off in Float. Writes are made with the account’s API key, so Float shows the API as the creator. Hebno adds your name to the allocation notes and records the write against you in Admin → Logs → Integrations. Linking marks which Float projects belong to a Hebno project, so you can ask “who is on this next week?” without naming them.
  1. Open the project and select Brain.
  2. Under Linked records, select Link record, then Float.
  3. Search by project name or client, and select the project. Repeat for each Float project in the engagement.
In chats tagged to the project, Hebno starts with the linked projects for any staffing or capacity question, and allocation cards default to them. See Linked records.

Use Float in chat

  • Attach: open the + menu, choose Sources → Float, and pick a person, a project or a schedule period. Or type / and choose Float.
  • Ask: name the person, project or week in your request. For example:
    Who in the pricing team has at least three free days in the week of 16 November?
    Show everyone allocated to the Contoso pricing review until the readout, and flag anyone in overtime.
    Move Priya’s Contoso allocation to start on 18 November at 6 hours a day.
  • Research runs show a Checking Float step, with a chip for each person, project and allocation it read.
  • Agents can read Float on a schedule, for example a Monday list of people under 50 per cent scheduled for the next fortnight. Writes an agent proposes appear in agent approvals for review.

Troubleshooting