Resources · Make integration

Float Make integrationAutomate Float with Make.

Can Make keep your Float schedule in sync with the rest of your tools? The Float Make integration gives you 50 modules: 9 triggers, 33 actions and 8 searches. This guide is for ops leads and project managers, and it walks you from the connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Float Make integration automate?

The Float Make integration links your Float account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Float then reacts to your other apps, and your other apps react to what changes in Float, without a line of code.

A project ready as soon as the client exists. Watch New Clients spots a client added in Float, and Create a Project opens its first project right away, so nobody retypes the name.

Hours that reach finance without copy and paste. Watch New Logged Times and Watch Updated Logged Times pick up each entry your team logs or corrects, and a module from your billing or spreadsheet app records it on the other side.

Leave that appears in the plan. When a request is approved in your HR tool, Create a Time Off books the absence in Float, and planners see it before they assign work to that person.

Know the limits before you start. All 9 triggers are scheduled, so Make checks Float on the scenario's schedule instead of hearing about changes the moment they happen. The Make documentation for Float also warns that it was generated with AI from Float's own docs, so check any detail that matters with Float. If a need falls outside the listed modules, Make an API Call reaches the rest of the Float API.

Float may also be available in n8n; the n8n vs Make comparison helps you choose a tool, and the Make review or Make training help you get started.

Connect

How do you connect your Float account to Make?

  1. 01

    Copy your API token in Float

    In Float, open your Account Settings, go to the Integrations page and find the API token section. Copy the token shown on screen. You need an active Float account for it to exist.

  2. 02

    Add a Float module in Make

    In your scenario, add any Float module and click Create a connection. A connection is your Float account linked to Make once; every Float module in your scenarios reuses it. You can give it a name in Connection name, which helps when you manage several accounts.

  3. 03

    Paste the token and save

    Paste the token you copied from Float into the credentials field, or follow the instructions Make shows on screen, then save. From then on, Make can list what it reads in Float when you fill a module's fields.

First scenario

Your first scenario with Float

GoalWhen a new client is created in Float, Make opens a first project for that client.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to place the first module on the canvas.

  2. 02

    Pick the Float trigger

    Search for Float, choose Watch New Clients and click Create a connection to link your account with the API token from Float.

  3. 03

    Add the project module

    Click the + on the right of the trigger, pick Create a Project and map the client coming from the first module into the fields Make offers.

  4. 04

    Test with Run once

    Add a test client in Float, then click Run once. Open each module to read the bundles it received: one bundle is one item, here one client and then one project.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; keep it or change it within your plan, then switch the scenario on.

Triggers

What can start a Float scenario?

9 modules start a scenario when something happens in Float. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Float as soon as it happens.

Float1Watch New Clients

Watch New Clients

Scheduled trigger

In MakeTriggers when a new client is created.

Watch New Clients starts your scenario each time someone adds a client in Float, and hands the next module that client as a bundle, ready to reuse in your CRM, your invoicing tool or a folder structure.

How it fires
it is a scheduled trigger, so Make checks Float on the scenario's schedule and collects the clients created since the last check.
When to use it
your sales team signs a new account and you want every other tool to know about it without retyping the name.
Watch out
it only sees new clients; a client renamed later does not start the scenario again.
Float2Watch New Departments

Watch New Departments

Scheduled trigger

In MakeTriggers when a new department is created.

Watch New Departments tells your scenario that a new department now exists in Float, so the teams you organize there can appear elsewhere too, such as a channel in your chat tool or a group in your directory.

How it fires
scheduled; Make asks Float for new departments at the pace you set on the scenario, not the instant one is added.
When to use it
the company opens a new team and you want the matching structure created in the other apps you use for staffing.
Float3Watch New Logged Times

Watch New Logged Times

Scheduled trigger

In MakeTriggers when a new logged time is created.

Watch New Logged Times picks up every fresh time entry your team records in Float, which turns Float into the starting point for timesheets, billing and project cost tracking in other apps.

How it fires
scheduled; on each run Make pulls the entries logged since the previous check, one bundle per entry.
When to use it
finance needs hours in a spreadsheet or an invoicing tool as people log them.
Watch out
a correction made afterwards is not a new entry; pair it with Watch Updated Logged Times if edits matter.
Float4Watch New Persons

Watch New Persons

Scheduled trigger

In MakeTriggers when a new person is created.

Watch New Persons reacts when a new person is added to Float, whether an employee or a contractor you schedule, and passes that profile along so onboarding steps can start in your other tools.

How it fires
scheduled; Make queries Float on the scenario's clock and returns each person created since the last run.
When to use it
a new hire enters the resource plan and you want an account, a welcome message or an HR record created from the same data.
Float5Watch New Projects

Watch New Projects

Scheduled trigger

In MakeTriggers when a new project is created.

Watch New Projects fires when a project appears in Float and gives you its details, so the rest of the workflow around it, a shared folder, a board or a client update, starts from the plan itself.

How it fires
scheduled; Make looks for new projects on the rhythm you choose on the first module.
When to use it
a project manager sets up a job in Float and the delivery team needs its workspace ready in other apps.
Watch out
projects created between two checks all arrive in the same run, as separate bundles.
Float6Watch New Tasks

Watch New Tasks

Scheduled trigger

In MakeTriggers when a new task is created.

Watch New Tasks catches each task planned in Float, the unit that assigns work to someone on a project, and lets your scenario tell the person or the tool that needs to know about it.

How it fires
scheduled; Make checks Float for new tasks whenever the scenario runs, not the moment a planner saves one.
When to use it
you want each new assignment posted in the team chat or copied into the to-do app people actually open.
Float7Watch New Time Offs

Watch New Time Offs

Scheduled trigger

In MakeTriggers when a new time off is created.

Watch New Time Offs detects a new absence entered in Float and sends it downstream, so the calendars and HR tools around your team stay consistent with the resource plan.

How it fires
scheduled; Make reads the time off created since its last visit, on the schedule set for the scenario.
When to use it
leave is recorded in Float first, and you want it mirrored in a shared calendar or reported to payroll.
Watch out
if leave is also created from another tool into Float, filter those entries out or the scenario may send them back.
Float8Watch Updated Logged Times

Watch Updated Logged Times

Scheduled trigger

In MakeTriggers when an existing logged time is updated.

Watch Updated Logged Times follows changes to entries that already exist, so a corrected number of hours reaches the report or the invoice instead of staying stuck in Float.

How it fires
scheduled; at each run Make asks Float which logged times were edited since the previous check.
When to use it
someone fixes a timesheet after the fact and the copy in your spreadsheet or billing tool has to follow.
Watch out
your scenario needs a way to find the matching record on the other side, such as the Float ID stored there.
Float9Watch Updated Tasks

Watch Updated Tasks

Scheduled trigger

In MakeTriggers when an existing task is updated.

Watch Updated Tasks notices when a planned task changes in Float, for example when it moves or gets reassigned, and lets your scenario refresh whatever depends on it.

How it fires
scheduled; Make checks for edited tasks on the scenario's schedule, so a change shows up at the next run.
When to use it
a planner reshuffles the week and the people involved should hear about it without opening Float.
Watch out
new tasks are not covered here; use Watch New Tasks for those.
Modules

What can Make do in Float?

Float gives you 41 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Float1

Create a Client

Action

In MakeCreates a new client.

Create a Client adds a client to Float from data your scenario already has, so a deal won in your CRM or a signed quote becomes a client that planners can attach projects to.

When to use it
the moment an account is confirmed in your sales tool.
Watch out
search first with List Clients if the same client can arrive twice, or you end up with duplicates.
Float2

Create a Department

Action

In MakeCreates a new department.

Create a Department builds a new department in Float from another source, which keeps the way you group people in the plan aligned with the org chart kept elsewhere.

When to use it
your HR or directory tool is the reference for teams, and a new team there should exist in Float too, ready to receive people.
Float3

Create a Logged Time

Action

In MakeCreates a new logged time.

Create a Logged Time records hours in Float on behalf of your team, which spares people from entering the same time twice when they already track it in another app.

When to use it
a time tracker or a form collects hours, and Float must show them against the right person and project.
Watch out
map the person and the project carefully; a wrong match puts hours on the wrong budget.
Float4

Create a Milestone

Action

In MakeCreates a new milestone.

Create a Milestone places a key date on a Float project, such as a delivery or a review, so the whole team sees it on the schedule without a planner adding it by hand.

When to use it
a contract, a board card or a form sets a deadline and that date has to land on the project in Float.
Float5

Create a Person

Action

In MakeCreates a new person.

Create a Person adds someone to Float so they can be scheduled, using the details your HR tool or onboarding form already holds, which avoids a second manual entry on the first day.

When to use it
a hire or a contractor is confirmed and planners need them available in the resource plan.
Watch out
check with List Persons whether that person already exists before you create them.
Float6

Create a Project

Action

In MakeCreates a new project.

Create a Project opens a project in Float from an event elsewhere, so the schedule is ready as soon as the work is sold and planners can start assigning people.

When to use it
a deal closes, a client is created or a form is submitted, and a project should follow.
Watch out
if the project belongs to a client, get or create that client first so you can link them.
Float7

Create a Task

Action

In MakeCreates a new task.

Create a Task assigns work in Float from another tool, which means a request logged in your ticketing or project app can show up on someone's schedule without anyone planning it twice.

When to use it
requests arrive in one place and planning lives in Float.
Watch out
the task needs the right person and project, so fetch them before this module.
Float8

Create a Time Off

Action

In MakeCreates a new time off.

Create a Time Off books an absence in Float so nobody gets scheduled on days they are away, using the approval that already happened in your HR or leave tool.

When to use it
a leave request is approved outside Float and the plan should reflect it at the next run.
Watch out
run it only on approved requests, not on drafts, to keep the plan honest.
Float9

Delete a Client

Action

In MakeDeletes an existing client.

Delete a Client removes a client from Float when it is removed at the source, which keeps your client list free of accounts that no longer exist.

When to use it
an account is deleted in your CRM and Float should not keep it around.
Watch out
a deletion cannot be undone from Make, so test it on a dummy client with Run once before you switch the scenario on.
Float10

Delete a Department

Action

In MakeDeletes an existing department.

Delete a Department takes a department out of Float, useful when a team is dissolved and should stop appearing as a group in the resource plan.

When to use it
a reorganization is recorded in your HR tool and Float must match it.
Watch out
move people to their new department first, then delete the old one, since the removal cannot be reversed from Make.
Float11

Delete a Logged Time

Action

In MakeDeletes an existing logged time.

Delete a Logged Time erases a time entry in Float, which lets a cancellation in your time tracker cancel the copy too, so reports do not count the same hours by mistake.

When to use it
an entry is removed at the source and the Float copy must go as well.
Watch out
you need the exact Float ID of that entry; without it, the wrong line could disappear.
Float12

Delete a Milestone

Action

In MakeDeletes an existing milestone.

Delete a Milestone removes a key date from a Float project, so a deadline that was dropped in your project tool stops cluttering the schedule people read every day.

When to use it
a phase is cancelled and its milestone no longer means anything.
Watch out
if the date only moved, Update a Milestone is the safer choice.
Float13

Delete a Person

Action

In MakeDeletes an existing person.

Delete a Person removes someone from Float, which fits the offboarding part of a scenario when a departure is recorded in your HR tool and the person must disappear from the plan.

When to use it
a contract ends and the person should no longer be scheduled.
Watch out
removal is final from Make; check what your team expects to keep about past work before you automate it.
Float14

Delete a Project

Action

In MakeDeletes an existing project.

Delete a Project removes a project from Float when the deal that created it falls through, so planners stop seeing work that will never happen.

When to use it
an opportunity is lost in your CRM after a project was opened too early.
Watch out
use a filter so only projects created by the scenario get deleted, never one that people have already planned by hand.
Float15

Delete a Task

Action

In MakeDeletes an existing task.

Delete a Task clears an assignment from Float, freeing the person's time on the schedule when the request behind it is closed or cancelled in another tool.

When to use it
a ticket is withdrawn and the planned hours should be released.
Watch out
map the Float task ID stored on the ticket, not the ticket number, or Make will not find the right task.
Float16

Delete a Time Off

Action

In MakeDeletes an existing time off.

Delete a Time Off removes an absence from Float, so a person who cancels their leave becomes available again in the plan without a planner stepping in.

When to use it
a leave request is withdrawn or rejected in your HR tool after it was already booked.
Watch out
keep the Float ID of each time off you create, so the right one can be removed later.
Float17

Get a Client

Action

In MakeRetrieves an existing client.

Get a Client fetches one client from Float by its ID, giving later modules its full record when the trigger only passed along a reference.

When to use it
a project or task arrives with a client ID and you want the client's details in your message or report.
Watch out
it needs an ID; to find a client by another value, use List Clients instead.
Float18

Get a Department

Action

In MakeRetrieves an existing department.

Get a Department reads a single department from Float, which helps when a person record carries a department ID and your scenario needs a readable team name instead.

When to use it
you route a notification or a report by team and must know which team a person belongs to.
Float19

Get a Logged Time

Action

In MakeRetrieves an existing logged time.

Get a Logged Time pulls one time entry from Float with its details, handy for checking what a line contains before you copy, bill or correct it somewhere else.

When to use it
another app stores the ID of an entry and you need its current values at that moment.
Watch out
to gather several entries at once, List Logged Times fits better.
Float20

Get a Milestone

Action

In MakeRetrieves an existing milestone.

Get a Milestone returns one milestone from Float, so a scenario can read the key date it is about to announce, compare or copy into a client update.

When to use it
you keep milestone IDs in a board or sheet and want to confirm the date in Float before sending a reminder to anyone.
Float21

Get a Person

Action

In MakeRetrieves an existing person.

Get a Person loads one person's record from Float, which turns a bare person ID coming from a task or a logged time into a name you can put in a message.

When to use it
you notify someone about a new task and need to know who they are.
Watch out
each call costs one operation, the unit Make counts on your plan, so avoid calling it when the data is already there.
Float22

Get a Project

Action

In MakeRetrieves an existing project.

Get a Project reads one project from Float, giving your scenario the context around a task, a milestone or a logged time that only points to it.

When to use it
a timesheet line must be labeled with its project name before it reaches finance.
Watch out
when you need to find projects by name or status, List Projects is the search to use.
Float23

Get a Task

Action

In MakeRetrieves an existing task.

Get a Task fetches one planned task from Float so you can check its current state before acting on it, for instance before notifying the person or updating a ticket.

When to use it
a ticket stores the Float task ID and you want the latest version of that task.
Watch out
it reads a single task by ID; to find tasks by project or person, List Tasks is the right module.
Float24

Get a Time Off

Action

In MakeRetrieves an existing time off.

Get a Time Off returns one absence from Float, which lets a scenario confirm the details of a leave entry before it announces it or copies it into a calendar.

When to use it
another tool keeps the time off ID and you want to read what Float holds now, after possible edits by a planner.
Float25

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call lets you call any endpoint of the Float API with the connection you already set up, which covers whatever the ready-made modules on this page do not.

When to use it
you need an object or an option from Float that has no dedicated module.
Watch out
you write the request yourself, so keep Float's API documentation open and test with Run once before you rely on it.
Float26

Update a Client

Action

In MakeUpdates an existing client.

Update a Client changes an existing client in Float so its record follows your CRM, for example after a rename, instead of drifting apart over time.

When to use it
an account is edited at the source and planners should see the same information.
Watch out
you need the Float client ID; store it in your CRM when the client is first created.
Float27

Update a Department

Action

In MakeUpdates an existing department.

Update a Department edits a department in Float, which keeps team names in the plan identical to those in your directory after a rename or a merge.

When to use it
the HR tool renames a team and you do not want two spellings of the same group across your apps and reports.
Float28

Update a Logged Time

Action

In MakeUpdates an existing logged time.

Update a Logged Time corrects an existing entry in Float, so an edit made in your time tracker changes the Float copy rather than adding a second line with the new hours.

When to use it
hours are adjusted after a review and Float must reflect the final figure.
Watch out
without the stored Float ID, Make cannot tell which entry to change.
Float29

Update a Milestone

Action

In MakeUpdates an existing milestone.

Update a Milestone moves or renames a key date on a Float project, so a deadline pushed in your project tool also shifts in the plan everyone reads.

When to use it
a client agrees to a new delivery date and the schedule should follow.
Watch out
store the Float ID of each milestone your scenarios create, or Make has no way to point at the right one later.
Float30

Update a Person

Action

In MakeUpdates an existing person.

Update a Person edits someone's profile in Float, so a change of role or team recorded in HR also reaches the resource plan that schedules them.

When to use it
an employee changes department and planners should see it without being told.
Watch out
match people on the Float ID rather than on names, which two colleagues can share.
Float31

Update a Project

Action

In MakeUpdates an existing project.

Update a Project changes an existing Float project from another source, so that what changed in your CRM or board, a rename for example, also reaches the plan.

When to use it
a deal is amended after signature and the project in Float should not tell a different story.
Watch out
two tools editing the same project can overwrite each other; decide which one is the reference.
Float32

Update a Task

Action

In MakeUpdates an existing task.

Update a Task edits a planned task in Float so that a change in the request behind it lands on the schedule without a planner redoing it.

When to use it
a ticket is reassigned in your helpdesk.
Watch out
if Watch Updated Tasks runs in another scenario, this edit can be picked up there as well, so make sure the two do not feed each other.
Float33

Update a Time Off

Action

In MakeUpdates an existing time off.

Update a Time Off changes an absence already booked in Float, so a person who shortens or extends their leave keeps an accurate place in the plan.

When to use it
the dates of an approved request are changed in your HR tool.
Watch out
a cancelled leave calls for Delete a Time Off, not an update to empty dates.
Float34

List Clients

Search

In MakeRetrieves a list of clients.

List Clients searches your Float clients and returns zero, one or many of them, each as its own bundle, which is how a scenario finds out whether a client already exists.

When to use it
just before Create a Client, to avoid duplicates.
Watch out
modules placed after it run once per client found, so add a filter when you expect a single match.
Float35

List Departments

Search

In MakeRetrieves a list of departments.

List Departments returns the departments defined in Float, a quick way to build a lookup between team names and their IDs inside a scenario that routes work by team.

When to use it
you sync departments with another tool and need to compare both lists.
Watch out
the search can also return nothing at all, for instance before the first department exists, so check the bundles with Run once.
Float36

List Logged Times

Search

In MakeRetrieves a list of logged times.

List Logged Times gathers several time entries from Float in one search, the natural input for a report, a client invoice or a sheet that totals hours by project.

When to use it
a request for a report arrives and you want the matching entries in one go.
Watch out
each entry is a separate bundle, so pair it with an aggregator in Make to build one total.
Float37

List Milestones

Search

In MakeRetrieves a list of milestones.

List Milestones returns the milestones stored in Float, which lets a scenario review upcoming key dates and share them with clients or with the team in one message.

When to use it
a project status request comes in and you want to answer with every milestone on record.
Watch out
several results mean several bundles downstream.
Float38

List Persons

Search

In MakeRetrieves a list of persons.

List Persons searches the people in Float, useful to check whether someone is already scheduled there before a scenario creates or updates their profile from HR data.

When to use it
ahead of Create a Person, or to match an email address with a Float ID.
Watch out
a broad search can return many bundles, each one counted as operations further down.
Float39

List Projects

Search

In MakeRetrieves a list of projects.

List Projects retrieves Float projects so your scenario can pick the right one by name, loop through them for a status report, or check that a project exists before adding tasks.

When to use it
an incoming request names a project and you need its Float ID.
Watch out
add a filter to keep only the project you expect.
Float40

List Tasks

Search

In MakeRetrieves a list of tasks.

List Tasks pulls the tasks planned in Float, a starting point for a workload summary, a digest sent to each person, or a comparison with tickets in another tool.

When to use it
you want to see every assignment tied to a project or a person in one step.
Watch out
many tasks means many bundles, and each module after it runs for every one.
Float41

List Time Offs

Search

In MakeRetrieves a list of time offs.

List Time Offs hands your scenario the time off already recorded in Float, so the next modules can work on every absence instead of one. Each time off arrives as its own bundle.

When to use it
pick it over Get a Time Off when you need the whole set, for example to copy absences into a staffing sheet.
Watch out
a search can return zero, one or many bundles, and every module placed after it runs once per bundle, so each run costs more operations.
Need help

Need help automating Float with Make?

A person reads every message.

FAQ

Float Make integration: common questions

01Is the Float Make integration free?
Yes, on the Make side. Float is a standard app, available from the Free plan like the 3,000+ standard apps. The Free plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need an active Float account, which Float bills separately.
02What do you need to connect Float to Make?
An active Float account and its API token. In Float, open Account Settings, go to the Integrations page and copy the token from the API token section. In Make, add any Float module, click Create a connection, optionally name it, then paste the token. The connection is created once and every Float module in your scenarios reuses it, so you do not repeat the step for each module. Make an API Call also relies on that same connection.
03Does the Float trigger in Make fire in real time?
No. All 9 Float triggers in Make are scheduled: Make checks Float on the scenario's schedule and picks up what changed since the previous check. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute. Float has no instant trigger in Make, so changes reach your scenario at the next run rather than the second they happen.
04What if a Float module is missing in Make?
Use Make an API Call. It calls any endpoint of the Float API with the connection you already created, so you can reach objects or options that the 50 listed modules do not cover. You write the request yourself, so keep Float's API documentation at hand and test with Run once. Also note that the Make documentation for Float was generated with AI from Float's docs, so verify any detail that matters directly with Float.
05Should you use Make or n8n for Float?
It depends on where your other automations already live. Make covers Float with 50 modules, including 9 scheduled triggers and a Make an API Call module for the rest of the API, all built in a visual editor without code. Float may also be available as a node in n8n. If your team already runs its workflows in one of the two tools, keeping Float there is usually the simpler choice, since connections and habits are already in place.