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 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.
How do you connect your Float account to Make?
- 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.
- 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.
- 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.
Your first scenario with Float
GoalWhen a new client is created in Float, Make opens a first project for that client.
- 01
Create the scenario
From the Scenarios page, create a new scenario and click the + to place the first module on the canvas.
- 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.
- 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.
- 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.
- 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.
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.
Watch New Clients
Scheduled triggerIn Make“Triggers 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.
Watch New Departments
Scheduled triggerIn Make“Triggers 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.
Watch New Logged Times
Scheduled triggerIn Make“Triggers 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.
Watch New Persons
Scheduled triggerIn Make“Triggers 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.
Watch New Projects
Scheduled triggerIn Make“Triggers 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.
Watch New Tasks
Scheduled triggerIn Make“Triggers 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.
Watch New Time Offs
Scheduled triggerIn Make“Triggers 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.
Watch Updated Logged Times
Scheduled triggerIn Make“Triggers 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.
Watch Updated Tasks
Scheduled triggerIn Make“Triggers 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.
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.
Modules index
- Create a Client
- Create a Department
- Create a Logged Time
- Create a Milestone
- Create a Person
- Create a Project
- Create a Task
- Create a Time Off
- Delete a Client
- Delete a Department
- Delete a Logged Time
- Delete a Milestone
- Delete a Person
- Delete a Project
- Delete a Task
- Delete a Time Off
- Get a Client
- Get a Department
- Get a Logged Time
- Get a Milestone
- Get a Person
- Get a Project
- Get a Task
- Get a Time Off
- Make an API Call
- Update a Client
- Update a Department
- Update a Logged Time
- Update a Milestone
- Update a Person
- Update a Project
- Update a Task
- Update a Time Off
- List Clients
- List Departments
- List Logged Times
- List Milestones
- List Persons
- List Projects
- List Tasks
- List Time Offs
Create a Client
ActionIn Make“Creates 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.
Create a Department
ActionIn Make“Creates 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.
Create a Logged Time
ActionIn Make“Creates 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.
Create a Milestone
ActionIn Make“Creates 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.
Create a Person
ActionIn Make“Creates 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.
Create a Project
ActionIn Make“Creates 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.
Create a Task
ActionIn Make“Creates 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.
Create a Time Off
ActionIn Make“Creates 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.
Delete a Client
ActionIn Make“Deletes 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.
Delete a Department
ActionIn Make“Deletes 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.
Delete a Logged Time
ActionIn Make“Deletes 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.
Delete a Milestone
ActionIn Make“Deletes 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.
Delete a Person
ActionIn Make“Deletes 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.
Delete a Project
ActionIn Make“Deletes 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.
Delete a Task
ActionIn Make“Deletes 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.
Delete a Time Off
ActionIn Make“Deletes 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.
Get a Client
ActionIn Make“Retrieves 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.
Get a Department
ActionIn Make“Retrieves 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.
Get a Logged Time
ActionIn Make“Retrieves 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.
Get a Milestone
ActionIn Make“Retrieves 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.
Get a Person
ActionIn Make“Retrieves 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.
Get a Project
ActionIn Make“Retrieves 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.
Get a Task
ActionIn Make“Retrieves 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.
Get a Time Off
ActionIn Make“Retrieves 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.
Make an API Call
ActionIn Make“Performs 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.
Update a Client
ActionIn Make“Updates 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.
Update a Department
ActionIn Make“Updates 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.
Update a Logged Time
ActionIn Make“Updates 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.
Update a Milestone
ActionIn Make“Updates 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.
Update a Person
ActionIn Make“Updates 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.
Update a Project
ActionIn Make“Updates 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.
Update a Task
ActionIn Make“Updates 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.
Update a Time Off
ActionIn Make“Updates 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.
List Clients
SearchIn Make“Retrieves 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.
List Departments
SearchIn Make“Retrieves 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.
List Logged Times
SearchIn Make“Retrieves 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.
List Milestones
SearchIn Make“Retrieves 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.
List Persons
SearchIn Make“Retrieves 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.
List Projects
SearchIn Make“Retrieves 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.
List Tasks
SearchIn Make“Retrieves 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.
List Time Offs
SearchIn Make“Retrieves 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.
Need help automating Float with Make?
A person reads every message.