Resources · Zapier integration

LiquidPlanner Classic Zapier integrationAutomate LiquidPlanner Classic with Zapier.

The LiquidPlanner Classic Zapier integration gives you 6 triggers, 32 actions and 0 searches. All six triggers are instant, and the actions cover projects, tasks, milestones, events, comments, timers and timesheets, so most of your planning chores can run from other tools.

See the 38 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the LiquidPlanner Classic Zapier integration does

LiquidPlanner Classic is online project management with predictive scheduling: the plan recalculates itself when things change. Zapier plugs it into your other apps. A change in a workspace can start work elsewhere, and your other tools can create, update, move or time items in LiquidPlanner Classic without anyone opening it.

Three results come up again and again.

A team that hears about task changes at once. New or Changed Task is instant, so a message can reach your team chat the moment a task is created or edited, on any plan.

Work that arrives already planned. A request collected in another tool becomes a task with Create a Task, then gets a range of effort with Create an Estimate for a Task and a place in line with Create Dependency.

Timesheets that move without chasing. Trigger Submit Timesheet and Trigger Accept Timesheet push a timesheet through its steps from another app, and the timer actions track hours against an item.

What Zapier does not do here: it cannot delete anything, and there is no search step, so a Zap cannot look up an item first. Most actions point at an item by its name, which must match what is in the workspace. Every trigger fires on creation and on change, so an update made by your own Zap can start it again. And nothing that happened before the Zap was switched on is picked up.

Still choosing a tool? The Make vs Zapier comparison is the next read.

Vocabulary

Zapier words, in plain English

Zapier has its own vocabulary. Here it is once, so the long lists further down read easily.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap, such as a new or changed task. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once started: the step that writes, sends or moves something for you, like creating a milestone.
Task
The unit Zapier bills: one action your Zap completes successfully. Not to be confused with a LiquidPlanner task.
Instant vs polling
An instant trigger is reported by the app the moment it happens; a polling one is checked by Zapier on a timer. All six here are instant.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A filter or a second action makes one, and it then needs a paid plan.
Connection
Your LiquidPlanner Classic account linked to Zapier once, then reused by every step and every Zap that uses it.
Cost

What a LiquidPlanner Classic Zap costs

LiquidPlanner Classic is not a premium app, so it works on the free plan. Triggers never cost anything; each action that goes through costs one task.

  • Premium appNo, works on the free plan
  • Tasks on the free plan100 per month
  • Steps per Zap on the free planTwo: one trigger, one action
  • Instant triggers6 of 6

A Zap that creates a task and then estimates it uses two tasks per run. An action that fails is not counted. The free plan gives 100 tasks a month and builds two-step Zaps only, one trigger and one action; a filter or a second action makes the Zap multi-step, which needs a paid plan. The grid below is how often Zapier checks polling triggers on each plan. It does not apply to this app: all six LiquidPlanner Classic triggers are instant and start the Zap right away, whatever your plan.

Connect

Connect LiquidPlanner Classic to Zapier

  1. 01

    Add the connection

    Open Apps in your Zapier account, click + Add connection, search for LiquidPlanner Classic and pick it. You need a LiquidPlanner Classic account with access to the workspace the Zap will use.

  2. 02

    Sign in

    Click Add connection. A tab opens on LiquidPlanner Classic: sign in with the account that owns the workspace you want to automate. Every Zap reuses this connection, so pick that account on purpose.

  3. 03

    Grant access

    Accept Zapier's access request in that tab. It closes and LiquidPlanner Classic shows up on your Apps page, ready to be used as a trigger or as an action.

First Zap

Your first Zap: task changes posted to your team

GoalPost a message in your team chat each time a LiquidPlanner Classic task is created or changed and matches your condition.

  1. 01

    Set the trigger

    Create a Zap, pick LiquidPlanner Classic and New or Changed Task, then your connection and the space it should watch. The space must be one you own.

  2. 02

    Test on a real task

    Run the test. Zapier brings back the three most recent tasks of the space, so you map the next steps on a real one rather than a blank sample.

  3. 03

    Add the filter

    Use the plus icon to add Filter, then set the field, the rule and the value. Since the trigger fires on every change, the filter keeps only the updates you care about.

  4. 04

    Add the message

    Add your team chat as the action and choose the step that sends a message. Put the task name and the details you need in the text, then test the step and read what came back.

  5. 05

    Publish

    Publish the Zap. With the filter it is multi-step and needs a paid plan; without it, the Zap fits the free plan but posts on every single change.

Triggers

LiquidPlanner Classic triggers

6 events start a Zap when something happens in LiquidPlanner Classic, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New or Changed Client

Instant trigger

In Zapier“This trigger will fire when a task is created or updated in your workspace.”

The name promises a new or changed client, yet Zapier's own blurb for it talks about tasks, not clients. Before you build on it, run the test: the three most recent items it brings back show you what it really sends.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
once that test shows it returns what your Zap needs to handle.
Watch out
you pick the space by name, and only the owner of that space can build the Zap.
2

New or Changed Comment

Instant trigger

In Zapier“A comment has been created or updated in your workspace.”

Fires whenever someone writes or edits a comment in your workspace, and hands the comment on. Conversations that live inside LiquidPlanner Classic can then reach people who never open it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
comments on items should be copied to a chat channel or an inbox.
Watch out
an edit counts as a change, so fixing a typo sends the comment again; and a Zap that adds comments can start itself.
3

New or Changed Document

Instant trigger

In Zapier“A document has been created or updated in your workspace.”

Reacts when a document is added or updated in your workspace and carries it to the steps that follow. It lets files attached in LiquidPlanner Classic be announced or logged elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your team should be told when a document lands or changes, without checking each item.
Watch out
this trigger asks for the space by its ID, and you must own that space to set it up.
4

New or Changed Package

Instant trigger

In Zapier“Triggered when a package is created or updated in LP.”

Goes off each time a package is created or modified in LiquidPlanner Classic, and hands the package to the steps you placed after it. Other tools learn when a package appears or changes.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a new package should create matching tasks, or its changes should be logged in a sheet.
Watch out
a Zap that uses Create a Package in the same space can set this trigger off again.
5

New or Changed Project

Instant trigger

In Zapier“A project has been created or updated in your workspace.”

Launches your Zap as soon as a project is created or edited in your workspace, and passes the project along. It is the natural start for anything that should follow a new project.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
each project should get a folder, a milestone or a kickoff task without someone setting them up by hand.
Watch out
it fires on every edit too, so add a filter if only brand-new projects should go through.
6

New or Changed Task

Instant trigger

In Zapier“A new task has been created in your workspace!”

Runs your Zap whenever a task is created or updated in the space you chose, and sends the task to the rest of the Zap. Every edit to a task counts as a change.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
people outside LiquidPlanner Classic need to know when a task appears, is done or is put on hold.
Watch out
a Zap that runs Update a Task on the same space will trigger itself again and again.
Actions

LiquidPlanner Classic actions

LiquidPlanner Classic gives you 32 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Trigger Accept Timesheet

Action

In Zapier“Accept a specific timesheet.”

Approves the timesheet of a user for the period starting on the date you map.

When to use it
the approval happens in another app and LiquidPlanner Classic should record it.
Watch out
a wrong start date points at a different period, or at none.
2

Send Clear Timer

Action

In Zapier“Clear the timer for a specific item.”

Clears the timer on an item you point to by name.

When to use it
a timer was started by mistake from another tool and should be cleared.
Watch out
the space and the item name are both required; if the hours should be logged rather than cleared, use Send Track Time via a Timer.
3

Create Activity

Action

In Zapier“Create a new activity for the workspace.”

Adds a new activity, the label time is tracked under, to the whole workspace.

When to use it
a new kind of work appears in another tool and should be selectable when people log hours.
Watch out
the billable option only shows up in timesheet exports; the shared option decides whether every client and project can use the activity or only the ones it is set up for.
4

Create Checklist Item for a Task

Action

In Zapier“Create a checklist item for a specific task.”

Appends a line to the checklist of a task you name, optionally already ticked.

When to use it
a step agreed elsewhere should become a box to tick on the right task.
Watch out
the task is picked by its name, so check that name points to a task in the space.
5

Add a Comment to an Item

Action

In Zapier“Add a comment to an item.”

Posts a comment on any item you name, with the text you map in.

When to use it
a reply or an update arrives in another app and should be visible on the item itself.
Watch out
paired with New or Changed Comment on the same space, it can loop.
6

Create Dependency

Action

In Zapier“Create a Dependency between two items.”

Links two items so that one cannot start before the other is done. You give the dependent item and its prerequisite, both by name.

When to use it
work created by a Zap should land in the right order instead of floating free in the schedule.
Watch out
both names are required and must match existing items.
7

Create an Event

Action

In Zapier“Create a full day event.”

Adds a full-day event to the workspace, with a name and the usual done, on hold and shared options.

When to use it
a whole day blocked in another tool should be blocked in the plan too.
Watch out
for anything shorter than a day, use the partial day version instead.
8

Create a Folder

Action

In Zapier“Create a new folder.”

Adds a folder to your workspace, which you can use to group items inside the plan. Only the space and the folder name are required.

When to use it
every new project or package should come with the same folder structure.
10

Create a Milestone

Action

In Zapier“Create a new milestone.”

Sets a milestone in the workspace, a marker for a date or a deliverable that the schedule works toward.

When to use it
each new project should get the same checkpoint without anyone adding it by hand.
Watch out
the shared option can make it visible on a project portal, so check it before you switch it on.
11

Create a Note for an Item

Action

In Zapier“Add a note to the item.”

Attaches a note to an item you point to by name, which keeps background information next to the work.

When to use it
context gathered in another tool belongs with the item it concerns.
Watch out
only the space and the item name are required.
12

Create a Package

Action

In Zapier“Create a new package.”

Creates a package in the space you choose, with the name you map and, if you want, already done or on hold.

When to use it
a batch of work agreed elsewhere should appear as one package ready to receive tasks.
Watch out
on hold means the package is not scheduled.
13

Create a Partial Day Event

Action

In Zapier“Create a partial day event.”

Blocks part of a day in the plan, with a name, a start time and a finish time, both given in UTC.

When to use it
a block of hours booked in another tool should be taken out of the schedule.
Watch out
the finish can be no more than 24 hours after the start, and times in another zone must be converted first.
14

Create a Project

Action

In Zapier“Create a new project.”

Opens a new project in the workspace you name, with its own title. It can start already done or on hold.

When to use it
a new client registered in another tool should turn into a project.
Watch out
marking it on hold or done means none of its tasks get scheduled.
15

Create a Task

Action

In Zapier“Create a new task in Liquid Planner.”

Puts a new task into the plan from data collected in another app. Name and space are required; it can be shared on a project portal, marked done or put on hold.

When to use it
requests from a form or an inbox should become scheduled work.
Watch out
a Zap started by New or Changed Task should not create tasks in the same space.
16

Create an Estimate for a Task

Action

In Zapier“Estimate a specific task.”

Gives a task a fresh low and high estimate of remaining work, in hours or in a short form like 4h or 0.5d.

When to use it
a sizing done in another tool should feed the schedule straight away.
Watch out
both the low and the high value are required, along with the task name.
17

Send Item Move After Command

Action

In Zapier“Move an item after another.”

Places an item right after another one, pushing it down the priority order.

When to use it
work put on the back burner in another tool should wait behind a specific item.
Watch out
the reference item must already exist in the space.
18

Send Item Move Before Command

Action

In Zapier“Move an item before another.”

Moves one item so it sits before another in the plan, which changes its priority in the schedule.

When to use it
something flagged as urgent elsewhere should jump ahead of a named item.
Watch out
both items are given by name and both are required.
19

Send Start Timer

Action

In Zapier“Start a timer for a specific item.”

Starts the timer on an item you name, so time begins to count against it.

When to use it
work starts in another tool and the hours should be logged on the right item.
Watch out
pair it with Send Stop Timer, or the timer keeps running.
20

Send Stop Timer

Action

In Zapier“Stop a timer for a specific item.”

Halts the timer running on an item you name.

When to use it
the same event that ends work elsewhere should stop the clock in the plan.
Watch out
to turn a timer's hours into logged time, Send Track Time via a Timer is the action for that.
21

Trigger Submit Timesheet

Action

In Zapier“Submit a specific timesheet.”

Despite its name, this is an action: it submits the timesheet of a given user that starts on a given date.

When to use it
a sign-off in another tool should hand the timesheet to its approver.
Watch out
user name and start date are both required and must match an existing timesheet.
22

Send Track Time

Action

In Zapier“Update your estimate, track hours worked, and add a comment and/or note.”

Records hours worked on an item and can update its estimate, add a comment or add a note in the same step.

When to use it
time is logged in another tool and should land in LiquidPlanner Classic without retyping.
Watch out
if you mark the task done, the low and high estimates must be left out or set to zero.
23

Send Track Time via a Timer

Action

In Zapier“Enter hours worked from a timer, update your estimate, add a comment, and restart the timer.”

Turns the hours on a task's timer into tracked time, updates the estimate, adds a comment and can restart the timer at zero.

When to use it
you run timers and want the logging done the moment work stops.
Watch out
marking done has the same rule as Send Track Time: estimates omitted or zero.
24

Trigger Un-Accept Timesheet

Action

In Zapier“Un-accept a specific timesheet.”

Reverses an approval, sending a user's accepted timesheet back to its previous state.

When to use it
an approval was given by mistake or needs to be revisited.
Watch out
like its siblings, it needs the user name and the timesheet start date.
25

Trigger Un-Submit Timesheet

Action

In Zapier“Un-submit a specific timesheet.”

Pulls a submitted timesheet back, for the user and start date you give.

When to use it
a correction is requested elsewhere and the timesheet must be editable again.
Watch out
it only works on a timesheet that was submitted.
26

Update a Checklist Item

Action

In Zapier“Update a checklist item.”

Ticks or unticks a checklist item, found by its name.

When to use it
a step is confirmed in another app and the box on the task should follow.
Watch out
the item is picked by its name, so give your checklist lines clear ones.
27

Update a Comment

Action

In Zapier“Change a comment.”

Rewrites an existing comment: you give the text it currently holds and the new text that should replace it.

When to use it
a comment posted by an earlier Zap needs its content corrected or refreshed.
Watch out
the old text is how the comment is identified, so it must match.
28

Update an Event

Action

In Zapier“Update an event.”

Modifies a full-day event identified by its name, with the done, on hold and shared options.

When to use it
a day blocked elsewhere changes and the plan should follow.
Watch out
the event name must match the one in the workspace.
30

Update a Milestone

Action

In Zapier“Update a specific milestone.”

Changes an existing milestone you name, for instance to mark it done or put it on hold.

When to use it
a deliverable is approved elsewhere and the milestone should reflect it.
Watch out
done means it no longer holds anything back, since its dependencies count as satisfied.
31

Update a Partial Day Event

Action

In Zapier“Update a partial day event.”

Edits a partial day event you name, so the schedule keeps up with a block of hours that changed.

When to use it
a block of hours booked in another tool changes.
Watch out
once on hold, it is no longer scheduled.
32

Update a Task

Action

In Zapier“Update an existing task item.”

Edits an existing task, found by its name, and can mark it done, put it on hold or share it on a project portal.

When to use it
work closed in another tool should close in the plan too.
Watch out
inside a Zap started by New or Changed Task, this action restarts the Zap with every edit it makes.
When it breaks

When a LiquidPlanner Classic Zap breaks

Zapier attaches no help article of its own to LiquidPlanner Classic. What goes wrong comes from how Zapier works, and from two habits of this app: triggers that fire on every change, and actions that find items by name.

Most of these are not bugs but surprises. If a run really fails, the Zapier troubleshooting page is where to look next.

  • The Zap triggers itself

    A Zap started by New or Changed Task that runs Update a Task on the same space sets itself off again with each edit, and burns your tasks fast.

  • You cannot pick the space

    Every trigger needs a space, and only its owner can create a Zap for it. A member's connection will not do; the owner has to connect.

  • The item is not found

    Most actions point at an item by its name. If the name passed along matches no item in the space, the action has nothing to work on.

  • Old items never show up

    A Zap only reacts to what happens after it is switched on. Projects or tasks created earlier are never picked up; moving them is a separate job.

  • A bulk change stalls

    When a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back.

  • Too many runs for one change

    Each edit is a change, so one task edited several times starts the Zap several times. A filter keeps only the changes that matter.
Need help

Need help automating LiquidPlanner Classic with Zapier?

A person reads every message.

FAQ

LiquidPlanner Classic Zapier integration: questions

01Is the LiquidPlanner Classic Zapier integration free?
Yes, as long as each Zap stays at two steps. LiquidPlanner Classic is not a premium app, so it works on the free plan, which gives you 100 tasks a month and unlimited Zaps. Each free Zap is one trigger and one action. A filter or a second action makes it multi-step, and that needs a paid plan. Since all six triggers are instant, the free plan does not slow them down; only the step count and the task allowance hold you back.
02How many tasks does a LiquidPlanner Classic Zap use?
One per action that succeeds, per run. Triggers cost nothing. A Zap that posts a message for each task change uses one task per change, and because the triggers fire on edits as well as creations, that can add up. A Zap that creates a task, estimates it and links it to a prerequisite uses three tasks per run. Actions that fail are not counted. A filter in front of the actions is the simplest way to avoid paying for changes you do not care about.
03Do LiquidPlanner Classic triggers fire instantly?
Yes. All six triggers are instant: LiquidPlanner Classic tells Zapier the moment a client, comment, document, package, project or task is created or changed, and the Zap starts right away. The plan does not matter here, so the free plan's 15-minute polling interval never applies to this app. A Zap built on an instant trigger shows a lightning bolt in the editor, which is a quick way to confirm you picked the right event.
04What does it take to connect LiquidPlanner Classic to Zapier?
A LiquidPlanner Classic account, a Zapier account, and ownership of the space you want to automate. In Zapier, open Apps, click + Add connection, search for LiquidPlanner Classic, sign in in the tab that opens and grant access. Then, when you set up a trigger, you choose the space: only the owner of a space can create a Zap for it. Actions also ask for the workspace name, and most of them for the name of the item they act on.
05Why does a LiquidPlanner Classic Zap run over and over?
Because every trigger fires on changes as well as on creations. If a Zap starts on New or Changed Task and then runs Update a Task in the same space, its own edit counts as a change and starts it again. The same goes for comments, packages and projects. Use a filter to let through only the changes you mean, or have the Zap write to a different space from the one it watches.
06What if the LiquidPlanner Classic operation you want is missing?
Then the Zap cannot do it directly. The integration offers six triggers and 32 actions, but no search and no deletion, and no trigger for timesheets or timers. Timers are a good example: nothing tells Zapier when one stops, so a Zap can start, stop or clear a timer from another tool but cannot react to it. If none of the 32 actions fits, that part of the process stays inside LiquidPlanner Classic for now.
07Zapier, Make or n8n for LiquidPlanner Classic?
It depends on your criteria rather than a ranking. Zapier gives you 38 ready-made LiquidPlanner Classic operations and instant triggers on every plan, in a guided editor. The trade-offs are the two-step limit of the free plan and the task count, which climbs because triggers fire on every change. Make and n8n bill and build differently, so compare them on your volume of changes, the number of steps per automation, and who will maintain it.
Same platform

Other docs you might need on this stack.

Browse all integrations