Resources · Make integration

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 you can automate

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.

Connect

How do you connect LiquidPlanner to Make?

  1. 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.

  2. 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.

  3. 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.

First scenario

Your first scenario: a starter task for every new project

GoalWhen a project is created in LiquidPlanner, Make adds a kickoff task to it.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

Triggers

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.

LiquidPlanner1Watch Clients

Watch Clients

Instant trigger

In MakeTriggers 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.

How it fires
instant, LiquidPlanner calls Make through a webhook as soon as the client is created or changed.
When to use it
your billing tool or CRM must hold the same client list as your planning workspace.
Watch out
an edit to an existing client starts the scenario as well, so a downstream module that creates records can produce duplicates unless it searches first.
LiquidPlanner2Watch Comments

Watch Comments

Instant trigger

In MakeTriggers 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.

How it fires
instant, the app notifies Make through a webhook the moment the comment is posted or changed.
When to use it
stakeholders who never open LiquidPlanner still need to see the discussion on their tasks.
Watch out
fixing a typo in a comment fires the trigger again, so the same message can be forwarded twice.
LiquidPlanner3Watch Documents

Watch Documents

Instant trigger

In MakeTriggers 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.

How it fires
instant, LiquidPlanner pings Make through a webhook as soon as the document appears or changes.
When to use it
files attached to your projects should also be logged in a drive, a spreadsheet or a client portal.
Watch out
an update counts as much as a creation, so design the next module to overwrite rather than add a second copy.
LiquidPlanner4Watch Packages

Watch Packages

Instant trigger

In MakeTriggers when a package has been created or updated.

This trigger sends your scenario each package created or modified in LiquidPlanner.

How it fires
instant, the app calls Make through a webhook when the package is created or edited.
When to use it
a new package should alert the delivery team or open a matching entry in a reporting sheet.
Watch out
renaming a package counts as a change too, so expect more runs than new packages and plan the actions that follow for repeat visits.
LiquidPlanner5Watch Projects

Watch Projects

Instant trigger

In MakeTriggers 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.

How it fires
instant, LiquidPlanner calls Make through a webhook as soon as a project is created or updated.
When to use it
a fresh project needs its kickoff task, a shared folder elsewhere, or a message to the account manager.
Watch out
the same trigger fires on creations and edits, so a setup scenario can repeat itself when someone edits the project later.
LiquidPlanner6Watch Tasks

Watch Tasks

Instant trigger

In MakeTriggers 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.

How it fires
instant, LiquidPlanner notifies Make through a webhook the moment the task is created or updated.
When to use it
a support desk or a dev tracker should mirror the tasks your team plans in LiquidPlanner.
Watch out
a scenario that updates the same task with Update a Task will change it again, which can wake this trigger once more.
Modules

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.

LiquidPlanner1

Accept a Timesheet

Action

In MakeAccepts 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.

When to use it
approvals already happen in a form or a chat button, and LiquidPlanner should reflect the decision.
Watch out
the module acts on one specific timesheet, so an earlier module has to hand it the right one.
LiquidPlanner2

Add a Comment to an Item

Action

In MakeAdds 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.

When to use it
a client answers a support ticket and the reply belongs on the matching task.
Watch out
reach for Create a Note for an Item instead when the text is reference material rather than discussion, and avoid pairing this module with Watch Comments on the same item.
LiquidPlanner3

Clear a Timer

Action

In MakeClears 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.

When to use it
a team member started a timer on the wrong task from a shortcut and wants it wiped.
Watch out
clearing is not the same as stopping; pick Stop a Timer when the tracked time should be kept, and test with Run once on a dummy item first.
LiquidPlanner4

Create a Checklist Item for a Task

Action

In MakeCreates 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.

When to use it
every onboarding task needs the same list of checks, fed from a template sheet or a form answer.
Watch out
one run adds one checklist item, so a list of five steps needs five bundles, for example from an iterator in front of it.
LiquidPlanner5

Create a Client

Action

In MakeCreates a client in workspace.

Create a Client adds a new client record to your workspace, ready to be tied to projects.

When to use it
a deal is marked won in your CRM and the account should exist in LiquidPlanner before anyone plans the work.
Watch out
nothing stops a second client with the same name; run List Clients first when the same deal might be processed twice.
LiquidPlanner6

Create a Dependency

Action

In MakeCreates a Dependency between two items.

Create a Dependency links two items so one waits for the other, without anyone setting the order by hand.

When to use it
a scenario builds a project from a template and design must finish before development starts.
Watch out
both items have to exist when the module runs, so place it after the modules that create them in the flow.
LiquidPlanner7

Create a Folder

Action

In MakeCreates 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.

When to use it
each new project should open with the same phases, such as discovery, delivery and support.
Watch out
a folder is empty when created; follow it with Create a Task to fill it.
LiquidPlanner9

Create a Milestone

Action

In MakeCreates a new milestone.

A milestone marks a checkpoint the whole plan works toward, and this module adds one without touching the LiquidPlanner interface.

When to use it
a contract signed in your e-signature tool carries a delivery date that should appear as a milestone in the project.
Watch out
an estimate on the milestone is a separate step; add Create an Estimate for a Milestone afterward if your team relies on it.
LiquidPlanner10

Create an Estimate for a Milestone

Action

In MakeCreates an estimate for a milestone.

This module puts an estimate on a milestone, so the plan reflects how much effort sits behind that checkpoint.

When to use it
milestones are generated by a scenario and the sizing comes from a quote or an intake form filled by the sales team.
Watch out
the milestone must already exist; chain this module right after Create a Milestone and map its output.
LiquidPlanner11

Create an Estimate for an Event

Action

In MakeCreates 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.

When to use it
training days booked in a calendar become LiquidPlanner events and the team wants their weight visible next to project work.
Watch out
for a meeting that only takes part of the day, pick the partial day estimate module instead.
LiquidPlanner12

Create an Estimate for a Partial Day Event

Action

In MakeCreates 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.

When to use it
recurring client calls are pushed into LiquidPlanner as partial day events from a booking tool.
Watch out
it only works on partial day events; a full day event takes Create an Estimate for an Event, and the two are easy to mix up in the module list.
LiquidPlanner13

Create an Estimate for a Task

Action

In MakeCreates 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.

When to use it
a quote line or a ticket already carries the expected effort and you want the schedule to use it right away.
Watch out
place it after Create a Task in the flow and map the task it just made, or the estimate lands elsewhere.
LiquidPlanner14

Create an Event

Action

In MakeCreates 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.

When to use it
approved leave in your HR tool should appear in the plan without someone retyping it.
Watch out
this module creates full day events only; half a day off calls for Create a Partial Day Event.
LiquidPlanner15

Create a Note for an Item

Action

In MakeAdds 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.

When to use it
the brief from an intake form or the summary of a kickoff call should live on the project for anyone who opens it.
Watch out
run it once per item; a second run adds another note, so use Update a Note for an Item to refresh existing text.
LiquidPlanner16

Create a Package

Action

In MakeCreates a new package.

Create a Package opens a new package in LiquidPlanner, ready to hold the tasks of a sprint or a release.

When to use it
each sprint or release planned in another tool should get a matching package so tasks can be ranked inside it.
Watch out
Watch Packages will fire on the package this module creates, so do not build both into one scenario loop.
LiquidPlanner17

Create a Partial Day Event

Action

In MakeCreates 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.

When to use it
appointments confirmed in a booking app should reduce the hours your plan assumes are free.
Watch out
for a whole day away, Create an Event is the right module; keep the two apart in your mapping.
LiquidPlanner18

Create a Project

Action

In MakeCreates 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.

When to use it
a won deal, a signed quote or an approved request form should become a project in the plan.
Watch out
if the same record can reach the scenario twice, check with List Projects first to avoid two identical projects.
LiquidPlanner19

Create a Task

Action

In MakeCreates a new task in Liquid Planner.

Create a Task puts a new task into LiquidPlanner, filled with what the previous module passed along.

When to use it
a support request, a form answer or a bug report needs to become planned work instead of staying in an inbox.
Watch out
a task created here also wakes Watch Tasks, so keep the two in separate scenarios.
LiquidPlanner20

Delete a Checklist Item for a Task

Action

In MakeDeletes 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.

When to use it
a service option is dropped from an order and its matching check should disappear from the delivery task.
Watch out
deletion cannot be undone from Make, so test on a copy of the task with Run once before switching the scenario on.
LiquidPlanner21

Delete a Client

Action

In MakeDeletes 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.

When to use it
a duplicate account is merged in your CRM and the leftover copy should vanish from the workspace.
Watch out
the module removes the client by ID with no confirmation, so double check the ID coming from the previous module during your Run once test.
LiquidPlanner22

Delete a Comment

Action

In MakeDeletes 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.

When to use it
a scenario posted a status comment and a later correction replaces it with a new one.
Watch out
removed text does not come back; prefer Update a Comment when a fix to the wording is enough.
LiquidPlanner23

Delete a Dependency

Action

In MakeDeletes 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.

When to use it
a blocker is resolved in your issue tracker and the LiquidPlanner items should stop waiting on each other.
Watch out
Get a Dependency lets you check which link you are about to remove before the delete runs.
LiquidPlanner24

Delete a Folder

Action

In MakeDeletes a specific folder.

Delete a Folder removes a folder from the workspace, handy when a scenario tidies up structures that were created by mistake.

When to use it
a test run created a set of phase folders you no longer need in the live plan.
Watch out
look at the tasks it holds before the delete runs, and never test on a real project since nothing comes back.
LiquidPlanner26

Delete a Milestone

Action

In MakeDeletes 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.

When to use it
a contract amendment removes a delivery step and the scenario keeps LiquidPlanner aligned with it.
Watch out
there is no undo, so pass the milestone through Get a Milestone first if the ID comes from outside.
LiquidPlanner27

Delete an Event

Action

In MakeDeletes 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.

When to use it
a leave request is withdrawn in your HR tool after it had already been synced.
Watch out
it handles full day events; a cancelled meeting booked as a partial day event needs Delete a Partial Day Event.
LiquidPlanner28

Delete a Note for an Item

Action

In MakeDeletes 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.

When to use it
a scenario writes a fresh summary and the previous note should go.
Watch out
in many flows Update a Note for an Item is simpler, since it changes the text in place and keeps a single note on the item.
LiquidPlanner29

Delete a Package

Action

In MakeDeletes a specific package.

This module removes a package from LiquidPlanner, the right move when a release or sprint is dropped altogether.

When to use it
a cancelled release in your product tool should no longer rank work in the plan.
Watch out
review the work it holds in the app before you let the scenario delete it, and test with Run once on a throwaway package.
LiquidPlanner30

Delete a Partial Day Event

Action

In MakeDeletes 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.

When to use it
a client cancels a call in your booking app and the slot in LiquidPlanner should disappear with it.
Watch out
map the ID of the partial day event itself; an ID of a full day event will not work here.
LiquidPlanner31

Delete a Project

Action

In MakeDeletes a specific project from workspace.

Delete a Project removes a whole project from the workspace, the heaviest cleanup module in the list.

When to use it
a deal is lost before any work starts and the placeholder project created for it should go away.
Watch out
this cannot be reversed from Make; keep it behind a clear condition and test it only on a project made for testing.
LiquidPlanner32

Delete a Task

Action

In MakeDeletes a specific task.

Delete a Task takes one task out of the plan, which keeps LiquidPlanner honest when the request behind it disappears.

When to use it
a ticket is closed as a duplicate in your help desk and the task created from it is no longer needed.
Watch out
the deleted task does not come back, so confirm the ID with Get a Task during your first Run once.
LiquidPlanner33

Delete a Treeitem

Action

In MakeDeletes 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.

When to use it
a cleanup scenario receives mixed items from List Treeitems and must remove them one by one.
Watch out
because it accepts any item, a wrong ID can hit a project instead of a task; test carefully.
LiquidPlanner34

Get a Checklist Item for a Task

Action

In MakeGets 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.

When to use it
a report or a client update should mention whether a given check on a delivery task is done.
Watch out
you need the ID of the checklist item, usually passed along by a module earlier in the scenario.
LiquidPlanner35

Get a Client

Action

In MakeGets 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.

When to use it
Watch Projects hands you a project and the scenario also needs the client behind it.
Watch out
it returns one client; to scan the whole list, List Clients is the better choice.
LiquidPlanner36

Get a Comment

Action

In MakeGets 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.

When to use it
a notification only carries a reference and the full wording is needed for a chat message.
Watch out
each call is one operation, the unit Make counts on your plan, so skip it when the trigger already delivered the text you need.
LiquidPlanner37

Get a Dependency

Action

In MakeGets 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.

When to use it
a status report explains why a task has not started by naming the item it depends on.
Watch out
it needs the dependency ID; to see every link at once, List Dependencies fits better.
LiquidPlanner38

Get a Folder

Action

In MakeGets a specific folder by ID.

Get a Folder reads one folder by its ID, handing its details to the next modules of the scenario.

When to use it
a task arrives from a trigger and the message you send should name the phase or folder it sits in.
Watch out
for a lookup by name, List Folders returns the candidates; this module only works when you already hold the ID.
LiquidPlanner40

Get a Milestone

Action

In MakeGets 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.

When to use it
a task tied to a checkpoint changes and the account manager should get a message naming that milestone.
Watch out
it covers one milestone at a time; to go through all of them, start from List Milestones.
LiquidPlanner41

Get an Event

Action

In MakeGets 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.

When to use it
your scenario holds an event ID from List Events and the next step, say a message to the team, needs the event details.
Watch out
no ID in hand means no result, so put List Events in front.
LiquidPlanner42

Get a Note for an Item

Action

In MakeGets 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.

When to use it
a task changed, Watch Tasks fired, and you want the note written on that task copied into a report or a client email.
Watch out
this module needs the note ID, not only the ID of the item that carries it.
LiquidPlanner43

Get a Package

Action

In MakeGets 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).

When to use it
before updating a package, check its current state so the scenario only acts when something actually needs to change.
Watch out
to browse packages rather than read a known one, List Packages is the right pick.
LiquidPlanner44

Get a Partial Day Event

Action

In MakeGets 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.

When to use it
a partial day event was created earlier in the scenario and a later module needs its stored values.
Watch out
full-day events live in a separate module, Get an Event, so keep the two apart when you map IDs.
LiquidPlanner45

Get a Project

Action

In MakeGets 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.

When to use it
Watch Tasks fired on a task and your notification should name the parent project, whose ID you already have.
Watch out
each call counts as an operation (one module run that Make bills on your plan), so avoid fetching the same project twice in one scenario.
LiquidPlanner46

Get a Task

Action

In MakeGets 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.

When to use it
a comment arrives through Watch Comments and you need the task it belongs to before posting an update to a support tool.
Watch out
for several tasks at once, List Tasks returns each one as its own bundle.
LiquidPlanner47

Get a Timer

Action

In MakeGets 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.

When to use it
a task has just been marked done and you want to check its timer before calling Stop a Timer or Clear a Timer.
Watch out
the module asks for the item, so map the task ID from an earlier step.
LiquidPlanner48

Get a Treeitem

Action

In MakeGets 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.

When to use it
a scenario receives an ID from a webhook of another app and must read it whatever its type.
Watch out
once you know the type, the dedicated Get module is easier to map.
LiquidPlanner49

Make an API Call

Action

In MakePerforms 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.

When to use it
you need an endpoint that none of the 86 modules covers and the LiquidPlanner API documentation describes it.
Watch out
you build the request yourself from the LiquidPlanner API documentation, so test with Run once (the editor button that runs the scenario a single time) before switching it on.
LiquidPlanner50

Move Item After

Action

In MakeMoves 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.

When to use it
a new task lands from a form and should sit just behind the current top item in its package.
Watch out
both IDs are required, the item you move and the one it follows.
LiquidPlanner51

Move Item Before

Action

In MakeMoves 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.

When to use it
an urgent client request arrives, the scenario creates the task and then moves it before the task your team is working on.
Watch out
the reference item must already exist in the plan, so check the new order in LiquidPlanner after your first Run once.
LiquidPlanner52

Start a Timer

Action

In MakeStarts 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.

When to use it
a ticket moves to In progress in your help desk and you want LiquidPlanner to start counting on the matching task at that moment.
Watch out
a started timer keeps running until something stops it, so plan the matching Stop a Timer in another scenario.
LiquidPlanner53

Stop a Timer

Action

In MakeStops 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.

When to use it
the linked ticket is resolved in another tool and the timer should stop at that moment, not whenever someone remembers.
Watch out
stopping is not clearing; when the timer should be reset rather than halted, the module you want is Clear a Timer.
LiquidPlanner54

Submit a Timesheet

Action

In MakeSubmits 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.

When to use it
a manager marks a period as closed in your HR tool and every timesheet tied to it should be submitted.
Watch out
you need the ID of that timesheet; if the wrong one goes out, Un-Submit a Timesheet brings it back.
LiquidPlanner55

Un-Accept a Timesheet

Action

In MakeUnaccepts 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.

When to use it
finance flags an error on hours already approved, and the scenario reopens the timesheet so its owner can fix it.
Watch out
this changes a record people rely on for billing, so add a filter in front to reopen only the timesheets that were flagged.
LiquidPlanner56

Un-Submit a Timesheet

Action

In MakeUnsubmits 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.

When to use it
a scenario submitted timesheets and one person reports missing hours; this module reopens only theirs.
Watch out
for a timesheet that was already approved, the module to reach for is Un-Accept a Timesheet.
LiquidPlanner57

Update a Client

Action

In MakeUpdates 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.

When to use it
an account is renamed or edited in your CRM and the matching client in LiquidPlanner should follow.
Watch out
you need the client ID; store it in the CRM when Create a Client runs, or look it up with List Clients.
LiquidPlanner58

Update a Comment

Action

In MakeUpdates 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.

When to use it
a scenario posts a build or delivery status as a comment, then edits that same comment when the status changes.
Watch out
keep the comment ID from Add a Comment to an Item; without it the scenario cannot find which comment to edit.
LiquidPlanner59

Update a Folder

Action

In MakeUpdates 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.

When to use it
a department or client is renamed in your directory, and the folder grouping their projects should carry the new name too.
Watch out
the module key in Make is spelled uptadeFolder, a typo on Make's side; search the module by its displayed name, Update a Folder.
LiquidPlanner61

Update a Milestone

Action

In MakeUpdates 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.

When to use it
a contract amendment is signed in your e-signature tool and the delivery milestone should move with it.
Watch out
a milestone ID is required, and a wrong mapping edits the wrong date; check the plan after the first Run once.
LiquidPlanner62

Update an Event

Action

In MakeUpdates 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.

When to use it
a leave request is changed in your HR tool and the event that blocks that day in LiquidPlanner must follow.
Watch out
half-day blocks are partial day events, which need Update a Partial Day Event instead of this module.
LiquidPlanner63

Update a Note for an Item

Action

In MakeUpdates 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.

When to use it
the brief is edited in your document tool and the note on the project should show the new version rather than a second copy.
Watch out
map the note ID kept from Create a Note for an Item, or the scenario edits nothing.
LiquidPlanner64

Update a Package

Action

In MakeUpdates a specific package.

Update a Package modifies a package, so its details follow decisions taken elsewhere.

When to use it
a sprint or release is renamed in your development tool, and the package that holds its tasks should carry the same label.
Watch out
you need the package ID; List Packages returns them if the scenario did not create the package itself.
LiquidPlanner65

Update a Partial Day Event

Action

In MakeUpdates 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.

When to use it
someone moves a medical appointment in the shared calendar and the partial day event created for it must shift the same way.
Watch out
keep the event ID from Create a Partial Day Event, or find it with List Partial Day Events.
LiquidPlanner66

Update a Project

Action

In MakeUpdates 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.

When to use it
a deal changes stage in your CRM and the project created for it should reflect the new status or owner.
Watch out
pairing this module with Watch Projects on the same project can make the scenario fire itself again; add a filter to break that loop.
LiquidPlanner67

Update a Task

Action

In MakeUpdates 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.

When to use it
a bug ticket is reassigned in your tracker and the linked task should switch owner at the same time.
Watch out
the same loop risk as Watch Tasks: if both sit in one scenario, filter out the changes the scenario made.
LiquidPlanner68

Update a Treeitem

Action

In MakeUpdates 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.

When to use it
a generic sync where the ID arrives from another app without saying which kind of item it points to.
Watch out
for a known type, the dedicated update module offers clearer fields to map.
LiquidPlanner69

Update Checklist a Item for a Task

Action

In MakeUpdates 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.

When to use it
a client signs the approval form, and the checklist item that tracked this approval should be marked as done on the task.
Watch out
the displayed name really reads Update Checklist a Item for a Task; search for checklist to find it.
LiquidPlanner70

List Clients

Search

In MakeGets 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.

When to use it
you want to match LiquidPlanner clients against CRM accounts and create only the ones missing.
Watch out
each bundle then runs the modules that follow, and every run counts as an operation on your plan.
LiquidPlanner71

List Dependencies

Search

In MakeGets 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.

When to use it
before rescheduling a task, see which items depend on it and warn their owners in your chat tool.
Watch out
a search can return zero bundles; add a filter so the rest of the scenario does not run on an empty result.
LiquidPlanner72

List Events

Search

In MakeGets 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.

When to use it
you publish team availability in a shared calendar and want the events from LiquidPlanner copied there.
Watch out
partial day events are not included; List Partial Day Events covers those.
LiquidPlanner73

List Folders

Search

In MakeGets 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.

When to use it
a new project must go into the folder of the right client, and the scenario first needs the folder IDs to pick from.
Watch out
match on the folder name with a filter, and plan what happens when no folder fits.
LiquidPlanner75

List Milestones

Search

In MakeGets a list of milestones.

List Milestones brings every milestone into the scenario, so key dates can be shared with people who never open LiquidPlanner.

When to use it
a client portal or a shared sheet should display upcoming milestones, fed from the plan rather than typed twice.
Watch out
to write the milestones into one table or one message, add an aggregator after this module to combine the bundles.
LiquidPlanner76

List Packages

Search

In MakeGets 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.

When to use it
your release notes tool should receive the list of packages and their names without anyone exporting them.
Watch out
the scenario receives one bundle per package; count the operations this creates before switching it on.
LiquidPlanner77

List Partial Day Events

Search

In MakeGets 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.

When to use it
a staffing sheet should show who is partly away, not only who is off for the whole day.
Watch out
combine it with List Events if the report must show both kinds of absence.
LiquidPlanner78

List Projects

Search

In MakeGets 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.

When to use it
management wants all active projects listed in a sheet that updates each time the scenario runs.
Watch out
the module lists all projects; filter afterwards on the values you care about to keep the sheet readable.
LiquidPlanner79

List Tasks

Search

In MakeGets 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.

When to use it
a client project closes in your CRM and every open task linked to it should be updated or reported.
Watch out
with many tasks, the modules placed after this search run many times; filter early to save operations.
LiquidPlanner80

List Treeitems

Search

In MakeGets 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.

When to use it
a full export of the workspace structure to a backup sheet, every kind of item in one pass.
Watch out
this module returns everything, so expect a large number of bundles and operations; for one type only, prefer its dedicated List module.
Need help

Need help automating LiquidPlanner with Make?

A person reads every message.

FAQ

LiquidPlanner and Make: frequent questions

01Is the LiquidPlanner Make integration free?
Yes, LiquidPlanner is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a scheduled run no more often than every 15 minutes, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Each module run on one bundle is an operation, which is what Make counts on your plan. Your LiquidPlanner subscription is a separate matter.
02What do you need to connect LiquidPlanner to Make?
Three things: the email and password you use to sign in to LiquidPlanner, a name for the connection, and your Workspace ID. The official documentation lists no other prerequisite. You find the Workspace ID in LiquidPlanner under Your Profile Icon, then Settings, then Workspace Summary. In Make, open Create a connection from any LiquidPlanner module, fill in the fields and click Continue. The connection is then reused by every LiquidPlanner module in your scenarios, so you only set it up once per workspace.
03Do LiquidPlanner triggers in Make react instantly?
Yes. All 6 LiquidPlanner triggers are instant: LiquidPlanner calls Make through a webhook as soon as a client, comment, document, package, project or task is created or updated, and the scenario runs at once instead of waiting for a schedule. Keep in mind that each trigger fires on edits as well as on creations. A scenario meant to handle only new records has to cope with repeated runs, for instance by searching before it creates anything, so it does not produce duplicates.
04What if the LiquidPlanner module you need is missing in Make?
Use Make an API Call. This module sends any request to the LiquidPlanner API with the connection you already set up, so it covers endpoints that the 86 listed modules do not. You will need the LiquidPlanner API documentation to build the request. The official Make documentation for this app gives no numeric limit, so there is no documented cap to plan around. If a scenario fails, open the bundles from a Run once test to see which module returned the error.
05Should you use Make or n8n for LiquidPlanner?
It depends on the criteria you care about. On Make, LiquidPlanner comes with 86 ready modules, 6 of them instant triggers, plus Make an API Call for anything else, and it runs from the Free plan. The same app often has an n8n node too, so check the node list there before deciding. Compare what each tool offers for your exact modules, the way usage is counted and which editor your team finds easier to maintain. The comparison page on this site lays out both tools side by side.