- Home
- Resources
- Integrations
- LiquidPlanner
LiquidPlanner Make integrationAutomate LiquidPlanner with Make.
What if new clients, tasks and timesheets moved through LiquidPlanner without anyone retyping them? The LiquidPlanner Make integration gives you 86 modules, including 6 instant triggers. This guide shows project leads how to connect the account, build a first scenario and pick the right module.
Verified Trustpilot reviews · AI, automation & growth agency
What does the LiquidPlanner Make integration do?
The LiquidPlanner Make integration links your LiquidPlanner workspace to Make, a no-code tool where you chain apps into a scenario (the automation you build, made of modules). LiquidPlanner can start a scenario when a client, task or project changes, and Make can then create, update, read or delete the items of your plan.
Every signed deal becomes a ready-made project. When a deal closes in your CRM, Create a Client and Create a Project set up the account and its plan, then Create a Task drops in the kickoff work so nobody starts from a blank tree.
Timesheets stop waiting in an inbox. Submit a Timesheet and Accept a Timesheet let an approval made elsewhere, in a form or a chat message, land in LiquidPlanner directly. Un-Accept a Timesheet covers the case where the manager changes their mind.
Comments reach the people who need them. Watch Comments fires as soon as someone writes on an item, so the text can be forwarded to a chat channel or a client report without copy and paste.
The limits are worth knowing before you start. All 6 triggers are instant and fire on creations and updates alike, so a scenario sees every edit, not only new records. The official doc gives no numeric limit for this app. When a listed module does not cover your need, Make an API Call reaches any endpoint of the LiquidPlanner API with the same connection.
If you are still weighing tools, the n8n vs Make comparison sets the two side by side, and the Make pricing page explains what each plan counts. To go further with scenarios, see the Make training.
How do you connect LiquidPlanner to Make?
- 01
Open the connection dialog
Add any LiquidPlanner module to your scenario and click Create a connection. A connection is your LiquidPlanner account linked to Make once, then reused by every LiquidPlanner module you add later.
- 02
Enter your login and a clear name
Type a label in Connection name, for example the workspace it points to. Then fill Email and Password with the credentials you use to sign in to LiquidPlanner.
- 03
Add the workspace and confirm
Paste your Workspace ID, found in LiquidPlanner under Your Profile Icon > Settings > Workspace Summary. Click Continue and Make lists your data in the module fields.
Your first scenario: a starter task for every new project
GoalWhen a project is created in LiquidPlanner, Make adds a kickoff task to it.
- 01
Create the scenario
On the Scenarios page, create a new scenario and click the big +. Search for LiquidPlanner and pick Watch Projects as the first module.
- 02
Link your account
Click Create a connection and follow the three steps above. Watch Projects is instant: LiquidPlanner calls Make through a webhook the moment a project is created or updated.
- 03
Add the task module
Click the + on the right of Watch Projects and choose Create a Task. Map the project data from the first module so the task lands in the project that just appeared.
- 04
Test with Run once
Click Run once, then create a test project in LiquidPlanner. Each module shows the bundle it received (one item passed along), so you can check the task went where you expected.
- 05
Switch it on
Turn the scenario on. The trigger also fires when a project is edited, so each edit could add another kickoff task: test an edit too before you rely on it.
What can start a LiquidPlanner scenario?
6 modules start a scenario when something happens in LiquidPlanner. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by LiquidPlanner as soon as it happens.
Watch Clients
Instant triggerIn Make“Triggers when a client has been created or updated.”
Watch Clients hands your scenario every client record that someone adds or edits in LiquidPlanner, so the rest of your stack learns about it without a manual export.
Watch Comments
Instant triggerIn Make“Triggers when a comment has been created or updated.”
With Watch Comments, each comment written or edited on a LiquidPlanner item becomes a bundle your scenario can route anywhere, from a chat channel to a client update email.
Watch Documents
Instant triggerIn Make“Triggers when a document has been created or updated.”
Watch Documents lets a scenario react when a document is added to LiquidPlanner or updated there, which is handy for keeping a shared archive in step with the plan.
Watch Packages
Instant triggerIn Make“Triggers when a package has been created or updated.”
This trigger sends your scenario each package created or modified in LiquidPlanner.
Watch Projects
Instant triggerIn Make“Triggers when a project has been created or updated.”
Watch Projects is the trigger to start from when your automation begins with a project: it passes along every project that appears or changes in your workspace.
Watch Tasks
Instant triggerIn Make“Triggers when a task has been created or updated.”
Every task that is added to LiquidPlanner or edited there reaches your scenario through Watch Tasks, which makes it the trigger to pick for task-level follow-up.
What can Make do in LiquidPlanner?
LiquidPlanner gives you 80 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Modules index
- Accept a Timesheet
- Add a Comment to an Item
- Clear a Timer
- Create a Checklist Item for a Task
- Create a Client
- Create a Dependency
- Create a Folder
- Create a Link
- Create a Milestone
- Create an Estimate for a Milestone
- Create an Estimate for an Event
- Create an Estimate for a Partial Day Event
- Create an Estimate for a Task
- Create an Event
- Create a Note for an Item
- Create a Package
- Create a Partial Day Event
- Create a Project
- Create a Task
- Delete a Checklist Item for a Task
- Delete a Client
- Delete a Comment
- Delete a Dependency
- Delete a Folder
- Delete a Link
- Delete a Milestone
- Delete an Event
- Delete a Note for an Item
- Delete a Package
- Delete a Partial Day Event
- Delete a Project
- Delete a Task
- Delete a Treeitem
- Get a Checklist Item for a Task
- Get a Client
- Get a Comment
- Get a Dependency
- Get a Folder
- Get a Link
- Get a Milestone
- Get an Event
- Get a Note for an Item
- Get a Package
- Get a Partial Day Event
- Get a Project
- Get a Task
- Get a Timer
- Get a Treeitem
- Make an API Call
- Move Item After
- Move Item Before
- Start a Timer
- Stop a Timer
- Submit a Timesheet
- Un-Accept a Timesheet
- Un-Submit a Timesheet
- Update a Client
- Update a Comment
- Update a Folder
- Update a Link
- Update a Milestone
- Update an Event
- Update a Note for an Item
- Update a Package
- Update a Partial Day Event
- Update a Project
- Update a Task
- Update a Treeitem
- Update Checklist a Item for a Task
- List Clients
- List Dependencies
- List Events
- List Folders
- List Links
- List Milestones
- List Packages
- List Partial Day Events
- List Projects
- List Tasks
- List Treeitems
Accept a Timesheet
ActionIn Make“Accepts a specific timesheet.”
Accept a Timesheet records the approval of one timesheet in LiquidPlanner, so hours move forward without the manager opening the app to click through them.
Add a Comment to an Item
ActionIn Make“Adds a comment to an item.”
Add a Comment to an Item posts a comment on a LiquidPlanner item from outside the app, which keeps the conversation attached to the work it concerns.
Clear a Timer
ActionIn Make“Clears the timer for a specific item.”
Clear a Timer resets the timer attached to one item, which gives a clean slate when tracking went wrong.
Create a Checklist Item for a Task
ActionIn Make“Creates a checklist item for a specific task.”
This module adds a checklist line to a given task, turning a vague piece of work into small steps people can tick off.
Create a Client
ActionIn Make“Creates a client in workspace.”
Create a Client adds a new client record to your workspace, ready to be tied to projects.
Create a Dependency
ActionIn Make“Creates a Dependency between two items.”
Create a Dependency links two items so one waits for the other, without anyone setting the order by hand.
Create a Folder
ActionIn Make“Creates a new folder in workspace.”
Need a tidy place for a batch of related work? Create a Folder adds a new folder to the workspace so tasks can be grouped the way your team reads the plan.
Create a Link
ActionIn Make“Creates a specific link for an item.”
Create a Link attaches a link to an item, so the spec, the ticket or the shared drive is one click away from the task itself.
Create a Milestone
ActionIn Make“Creates a new milestone.”
A milestone marks a checkpoint the whole plan works toward, and this module adds one without touching the LiquidPlanner interface.
Create an Estimate for a Milestone
ActionIn Make“Creates an estimate for a milestone.”
This module puts an estimate on a milestone, so the plan reflects how much effort sits behind that checkpoint.
Create an Estimate for an Event
ActionIn Make“Creates an estimate for an event.”
Create an Estimate for an Event gives a full day event its own estimate, so time blocked for workshops or trips counts in the plan.
Create an Estimate for a Partial Day Event
ActionIn Make“Creates an estimate for a partial day event.”
Short blocks of time add up, and this module records an estimate on a partial day event so those hours show in capacity planning.
Create an Estimate for a Task
ActionIn Make“Creates an estimate for a task.”
Create an Estimate for a Task sizes one task from outside LiquidPlanner, so a new task arrives with its effort instead of an empty field.
Create an Event
ActionIn Make“Creates a full day event.”
Create an Event blocks a full day in LiquidPlanner, which keeps holidays, offsites or conference days out of the time available for tasks.
Create a Note for an Item
ActionIn Make“Adds a note to the item.”
Where a comment starts a conversation, a note keeps context on the item itself, and this module writes one for you.
Create a Package
ActionIn Make“Creates a new package.”
Create a Package opens a new package in LiquidPlanner, ready to hold the tasks of a sprint or a release.
Create a Partial Day Event
ActionIn Make“Creates a partial day event.”
This module books a slice of a day in LiquidPlanner, for a meeting, a doctor visit or a client call, so the schedule knows that time is taken.
Create a Project
ActionIn Make“Creates a new project.”
Create a Project adds a fresh project to your workspace from data another app already holds, so nobody rebuilds it by hand.
Create a Task
ActionIn Make“Creates a new task in Liquid Planner.”
Create a Task puts a new task into LiquidPlanner, filled with what the previous module passed along.
Delete a Checklist Item for a Task
ActionIn Make“Deletes a checklist item for a specific task.”
Delete a Checklist Item for a Task removes one checklist line from a task, keeping lists clean when a step no longer applies.
Delete a Client
ActionIn Make“Deletes specific client by ID.”
Delete a Client takes a client record out of LiquidPlanner, which helps when your client list must match a cleaned CRM.
Delete a Comment
ActionIn Make“Deletes a comment from specific item.”
With Delete a Comment, a comment disappears from its item, which is useful for moderation or for cleaning up automated messages.
Delete a Dependency
ActionIn Make“Deletes a dependency for a specific item.”
Delete a Dependency breaks the link that made one item wait for another, which frees the schedule when the order no longer matters.
Delete a Folder
ActionIn Make“Deletes a specific folder.”
Delete a Folder removes a folder from the workspace, handy when a scenario tidies up structures that were created by mistake.
Delete a Link
ActionIn Make“Deletes a link from specific item.”
This module strips a link from an item, so a task stops pointing to a document or page that no longer exists.
Delete a Milestone
ActionIn Make“Deletes a specific milestone.”
Delete a Milestone takes a checkpoint out of the plan, which matters when a phase is cancelled and the date should stop driving the schedule.
Delete an Event
ActionIn Make“Deletes a specific event.”
When a full day off is cancelled, Delete an Event gives that day back to the plan by removing the event from LiquidPlanner.
Delete a Note for an Item
ActionIn Make“Deletes a note for a specific item.”
Delete a Note for an Item erases a note from an item, which keeps outdated context from misleading whoever opens the task next.
Delete a Package
ActionIn Make“Deletes a specific package.”
This module removes a package from LiquidPlanner, the right move when a release or sprint is dropped altogether.
Delete a Partial Day Event
ActionIn Make“Deletes a specific partial day event.”
Delete a Partial Day Event frees a slice of time that had been booked, so the plan counts those hours as available again.
Delete a Project
ActionIn Make“Deletes a specific project from workspace.”
Delete a Project removes a whole project from the workspace, the heaviest cleanup module in the list.
Delete a Task
ActionIn Make“Deletes a specific task.”
Delete a Task takes one task out of the plan, which keeps LiquidPlanner honest when the request behind it disappears.
Delete a Treeitem
ActionIn Make“Deletes a specific treeitem from workspace.”
Delete a Treeitem removes any item from the workspace tree, whatever its kind, which makes it the generic delete when you do not know the item type in advance.
Get a Checklist Item for a Task
ActionIn Make“Gets a checklist item for a specific task by ID.”
Get a Checklist Item for a Task reads one checklist line by its ID, so the scenario knows its current wording and state before acting.
Get a Client
ActionIn Make“Gets info about specific client.”
Get a Client fetches the full record of one client, giving later modules the details they need to fill an invoice, a report or a message.
Get a Comment
ActionIn Make“Gets a comment by ID.”
Get a Comment pulls one comment by its ID, so a scenario can read the exact text before forwarding or quoting it.
Get a Dependency
ActionIn Make“Gets a specific dependency by ID.”
Get a Dependency returns the details of one link between two items, which tells the scenario what is waiting on what.
Get a Folder
ActionIn Make“Gets a specific folder by ID.”
Get a Folder reads one folder by its ID, handing its details to the next modules of the scenario.
Get a Link
ActionIn Make“Gets a specific link by ID.”
Get a Link returns one link stored on an item, so a scenario can reuse the address in an email or a report.
Get a Milestone
ActionIn Make“Gets detail about a specific milestone.”
Get a Milestone reads the details of one checkpoint, so a scenario can quote its name and state in updates to clients or managers.
Get an Event
ActionIn Make“Gets a specific event by ID.”
Get an Event returns the full record of one LiquidPlanner event, fetched by its ID, ready for the next module to read. It fills the gap when an earlier step only passed along the event ID.
Get a Note for an Item
ActionIn Make“Gets a specific note by ID.”
Get a Note for an Item reads back one note attached to a LiquidPlanner item, found by its ID, so its text can travel to another app. Think of it as opening the note without leaving your scenario.
Get a Package
ActionIn Make“Gets a specific package by ID.”
Get a Package hands your scenario the details of a single package, the LiquidPlanner container for a batch of work, looked up by ID. Every field you map afterwards comes from this one bundle (the item passed between modules).
Get a Partial Day Event
ActionIn Make“Gets a specific partial day event by ID.”
Get a Partial Day Event brings back one partial day event, such as a half-day absence blocked in LiquidPlanner, identified by its ID. The scenario can then copy its details into a calendar or a staffing sheet.
Get a Project
ActionIn Make“Gets a specific project by ID.”
Get a Project returns one LiquidPlanner project by its ID, with the details a later module can map into a CRM, a spreadsheet or a chat message. One project in, one bundle out.
Get a Task
ActionIn Make“Gets a specific task by ID.”
Get a Task fetches a single task from LiquidPlanner by ID so your scenario works from its stored data rather than guesses. The task itself stays untouched: this module reads, it never edits.
Get a Timer
ActionIn Make“Gets timer for a specific item.”
Get a Timer tells your scenario where the timer stands on a given item, so you know its state before deciding what happens next. It reads only, nothing gets started or stopped.
Get a Treeitem
ActionIn Make“Gets info about specific treeitem by ID.”
Get a Treeitem gives you the information behind one treeitem, the generic entry of the LiquidPlanner hierarchy, whatever kind of item it turns out to be. Useful when the type is not known in advance.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
Make an API Call opens the whole LiquidPlanner API to your scenario, with the connection you already set up, for everything the listed modules leave out. No extra login, no separate app to configure.
Move Item After
ActionIn Make“Moves an item after another item.”
Move Item After reorders your plan by placing one LiquidPlanner item right after another. A scenario can then fix the order of the plan without anyone dragging rows by hand.
Move Item Before
ActionIn Make“Moves an item before another item.”
Move Item Before pushes an item up the list by placing it directly in front of another one. It works the other way round from Move Item After.
Start a Timer
ActionIn Make“Starts a timer for a specific item.”
Start a Timer starts tracking time on a LiquidPlanner item without anyone opening the app. The clock runs on the task the scenario points to.
Stop a Timer
ActionIn Make“Stops a timer for a specific item.”
Stop a Timer halts the timer running on an item, on the task the scenario points to. It closes what Start a Timer opened.
Submit a Timesheet
ActionIn Make“Submits a specific timesheet.”
Submit a Timesheet sends a timesheet into review on the team member's behalf, the step that normally waits for someone to click the button in LiquidPlanner. Handy for closing a reporting period cleanly.
Un-Accept a Timesheet
ActionIn Make“Unaccepts a specific timesheet.”
Un-Accept a Timesheet reverses an approval, putting an accepted timesheet back into an open state where it can be corrected. It undoes Accept a Timesheet.
Un-Submit a Timesheet
ActionIn Make“Unsubmits a specific timesheet.”
Un-Submit a Timesheet pulls a submitted timesheet back to its owner, so hours can still be edited before anyone reviews them. It cancels Submit a Timesheet.
Update a Client
ActionIn Make“Updates information about client.”
Update a Client keeps a LiquidPlanner client record in line with the source you trust, by rewriting its information on the spot. Your project tool then shows the same client data as your CRM.
Update a Comment
ActionIn Make“Updates a specific comment.”
Update a Comment rewrites a comment already posted on an item, which keeps a status message current instead of piling up new ones. Readers see one comment that stays accurate.
Update a Folder
ActionIn Make“Updates a specific folder.”
Update a Folder changes a folder in your LiquidPlanner workspace, so the structure mirrors how your team organizes clients or departments elsewhere.
Update a Link
ActionIn Make“Updates a specific link for an item.”
Update a Link edits a link already attached to a LiquidPlanner item, so the URL your team clicks always leads to the right document or ticket.
Update a Milestone
ActionIn Make“Updates a specific milestone.”
Update a Milestone adjusts a milestone that already exists, so the key date in LiquidPlanner matches what was agreed with the client. Everyone reading the plan sees the change at once.
Update an Event
ActionIn Make“Updates a specific event.”
Update an Event brings a full-day event in LiquidPlanner up to date, so availability in the plan reflects the latest decision rather than the first request.
Update a Note for an Item
ActionIn Make“Updates a note for a specific item.”
Update a Note for an Item replaces the content of a note on an item, which suits living notes such as a client brief or a list of access details that change over time.
Update a Package
ActionIn Make“Updates a specific package.”
Update a Package modifies a package, so its details follow decisions taken elsewhere.
Update a Partial Day Event
ActionIn Make“Updates a specific partial day event.”
Update a Partial Day Event corrects a partial day event, such as a morning off or an afternoon training, so the hours blocked in LiquidPlanner stay accurate.
Update a Project
ActionIn Make“Updates a specific project.”
Update a Project rewrites a project's details in LiquidPlanner, so the plan tells the same story as the deal or contract behind it.
Update a Task
ActionIn Make“Updates a specific task.”
Update a Task changes a task in place, so the work in LiquidPlanner follows what happens in the tools your team actually uses.
Update a Treeitem
ActionIn Make“Updates a specific treeitem.”
Update a Treeitem edits any entry of the LiquidPlanner tree through a single module, whatever its type. That saves branching the scenario when the incoming item could be of any kind.
Update Checklist a Item for a Task
ActionIn Make“Updates checklist item for a specific task.”
This module edits one line of a task's checklist, so progress shows inside LiquidPlanner without anyone updating it by hand.
List Clients
SearchIn Make“Gets list of all clients.”
List Clients returns every client of your workspace, one bundle per client, which later modules process one at a time. It is the starting point for any sync or cleanup of your client list.
List Dependencies
SearchIn Make“Gets a list of dependencies.”
List Dependencies pulls out the dependencies of your plan, the links saying one item must wait for another, as separate bundles you can inspect or export.
List Events
SearchIn Make“Gets a list of events.”
List Events gathers the full-day events of LiquidPlanner, such as holidays or closures, so another tool can show the same availability.
List Folders
SearchIn Make“Gets a list of all folders.”
List Folders returns all the folders of your workspace, giving the scenario a map of how projects are organized before it files anything.
List Links
SearchIn Make“Gets a list of links.”
List Links collects the links stored on your LiquidPlanner items, handy to audit which documents, tickets or pages a project points to.
List Milestones
SearchIn Make“Gets a list of milestones.”
List Milestones brings every milestone into the scenario, so key dates can be shared with people who never open LiquidPlanner.
List Packages
SearchIn Make“Gets a list of packages.”
List Packages outputs the packages of your workspace one by one, which lets a scenario review priorities or copy them elsewhere.
List Partial Day Events
SearchIn Make“Gets a list of all partial day events.”
List Partial Day Events retrieves all partial day events, the half-day or few-hour blocks set in LiquidPlanner, so capacity reports include them.
List Projects
SearchIn Make“Gets a list of all projects.”
List Projects delivers every project of the workspace as a separate bundle, the basis for a portfolio view in a spreadsheet or a dashboard tool.
List Tasks
SearchIn Make“Gets a list of tasks.”
List Tasks returns the tasks of LiquidPlanner, one bundle each, so a scenario can act on many at once instead of one known ID.
List Treeitems
SearchIn Make“Gets a list of all treeitems.”
List Treeitems walks the whole LiquidPlanner tree and returns each treeitem, whatever its type, as a bundle. It is the broadest search of the app.
Need help automating LiquidPlanner with Make?
A person reads every message.