You must be the owner of a space to create a zap for that space.

You must be the owner of a space to create a zap.

The LiquidPlanner workspace you are targeting with this zap.

Name of the user to look up a timsheet for.

Date the timesheet starts that should be accepted.

Name of the item where the timer should be cleared.

Boolean flag; does not affect application behavior, but its value is reflected in a timesheet export.

Boolean flag; if true, then the activity is selectable for time tracked for items contained by any and all clients and projects; if false, then the activity is selectable only for those clients and projects for which it is specifically configured.

Name of the task to add the checklist item to.

(true|false) has this checklist item been completed ?

Name of the member who this comment should show as having made.

The name of the the prerequisite item that must be done before this dependent item can start.

The date on which this event starts. Format like 2014-01-24.

The date on which this event ends. Format like 2014-01-24.

Name of the parent project/folder/package that the event should go in to.

Name of the package the event belongs to, if any.

Name of the activity most recently used for tracking time against this item, suggested for use as a default.

Limit on the number of hours of work; triggers a flag if exceeded.

Arbitrary string; use e.g. to store a reference ID from an external system.

Editable, arbitrary string; if nonblank, generates an alert on this item.

If true, then the item is done; it has 0 effort, no schedule dates, and any dependencies on it are satisfied.

If true, then the event is on hold, and will not be scheduled.

If true, then the event may be visible on a project portal.

Name of the package the folder belongs to, if any.

A date before which no item in this container will start. Format 2014-01-24.

Date the folder contents are complete. Format 2014-01-24.

If the expected_finish of the item falls after this date, an alert is generated. Format 2014-01-24.

Arbitrary string; if nonblank, generates an alert on this item.

If true, then the item is on hold, and will not be scheduled.

Date of the milestone. Format 2014-01-24.

Populate the first comment in the milestone.

Name of the parent project/folder/package that the milestone should go in to.

Name of the package the milestone belongs to, if any.

Name of the package the package belongs to, if any.

Name of the parent project/folder/package that the package should go in to.

The plaintext description of the package.

The date on which this item was completed, defaulted to today if the item is marked done today. Format 2014-01-24.

The UTC date and time of the beginning of the partial day event. Format like 2015-04-03T010:30:00+00:00.

The UTC date and time of the end of the partial day event. Must be no more than 24 hours after start_time. Format like 2015-04-03T010:30:00+00:00.

Populate the first comment in the partial day event.

Plaintext summary of this partial day event.

Populate the notes field of a partial day event.

Name of the parent project/folder/package that the partial day event should go in to.

Name of the package the partial day event belongs to, if any.

If true, then the partial day event is on hold, and will not be scheduled.

If true, then the partial day event may be visible on a project portal.

Name of the parent project/folder/package that the project should go in to.

Name of the client associated with this project, if any; modifying this value changes the client_id of all items contained by this project.

A date before which no item in this project will start. Format 2014-01-24.

Boolean, if set to true, all tasks in the project are done and therefore not scheduled.

Boolean, if set to true, all tasks in the project are not scheduled.

Name of the package the project belongs to, if any.

Low estimate for remaining work, hours (or a string such as “4h”, “0.5d”).

High estimate for remaining work, hours (or a string such as “4h”, “0.5d”).

Name of the activity most recently used for tracking time against this workitem, suggested for use as a default.

ID of the parent project/folder/package that the task should go in to.

Name of the package the task belongs to, if any.

A date before which this task cannot start. Format 2014-01-24.

The date on which this item was started. Format 2014-01-24.

If true, then the task may be visible on a project portal.

The name of the other item, after which to move this item.

The name of the other item, before or after which to move this item.

Name of the item that has the timer to stop.

Name of the user to submit the timesheet for.

Item name to register the time against and update.

Low estimate for remaining work, hours (or a string such as “4h”, “0.5d”); usually optional, must be provided if you provide high, and omitted or set to ‘0’ when setting is_done.

High estimate for remaining work, hours (or a string such as “4h”, “0.5d”); usually optional, must be provided if you provide low, and omitted or set to ‘0’ when setting is_done.

Name of the activity for the work; required if you are using timesheets and provide a value for work.

Name of the member to track work against and comment as; optional, defaults to you (the current user)
NOTE: you can not track time for virtual members via the Zap.

If true, marks task as done; low and high must each be omitted or explicitly zero.

Datetime on which the task was done; valid only when is_done=true, defaults to now. Format 2014-01-24.

Date on which the work was performed, default today. Format 2014-01-24.

Note to add to the timesheet entry, optional.

If true, the timer restarts at zero for the task, optional.

Name of the user whose timesheet you wish to un-accept.

Start date of the timesheet to un-accept.

Name of the user whose timesheet you wish to un-submit.

Start date of the timesheet to un-submit.

Name of member who this comment should show as having made.

The date on which this event starts. Format 2014-01-24.

The date on which this event ends. Format 2014-01-24.

Name of the parent project/folder/package that the item should go in to.

Name of the package the item belongs to, if any.

A date before which this item cannot start. Format 2014-01-24.

LiquidPlanner Classic, online project management with predictive scheduling that updates automatically when things change.

LiquidPlanner Classic

Pivotal Tracker is a collaborative, project management tool for developers and agile product management teams.

Pivotal Tracker

Jira is a bug and issue tracking tool that allows software developers to manage product development and build better software. This integration connects to self-hosted instances of Jira.

Jira Software Server

Redmine is a flexible project management web application built with Ruby on Rails.

Zapier Automation Platform

PRODUCTS

CAPABILITIES

By use case

By app

By team

By company size

How Zapier Zaps

How Zapier Uses AI

By team

Learn more

Get help

Zapier quick-start guide

Developer resources

LiquidPlanner Classic Integrations

LiquidPlanner Classic Help & Support

About LiquidPlanner Classic

Related categories

Similar apps

Pivotal Tracker

Jira Software Server

Redmine