Fill in the id or name of the job's status (the entity must already exists in your company) when changed to which the trigger will be triggered. For example - 123 or Completed are both valid values. If you leave this field blank, the trigger will be triggered when changing to any status.

Fill in a start date of the calendar task (allowed format - Y-m-d). For example - 2019-09-06. [API field name - start_date]

Fill in a start time of the calendar task (allowed format - H:i). For example - 20:30. [API field name - start_time]

Fill in an end date of the calendar task (allowed format - Y-m-d). For example - 2019-09-06. [API field name - end_date]

Fill in an end time of the calendar task (allowed format - H:i). For example - 20:30. [API field name - end_time]

Fill in an id of the user that will be attached (the entity must already exists in your company). For example - 123 are valid value. [API field name - users_id]

Fill in an id of the customer that will be attached (the entity must already exists in your company). For example - 123 are valid value. [API field name - customers_id]

Fill in an id of the job that will be attached (the entity must already exists in your company). For example - 123 are valid value. [API field name - jobs_id]

Fill in an id of the estimate that will be attached (the entity must already exists in your company). For example - 123 are valid value. [API field name - estimates_id]

Fill in the field to true to set recurrence options for the calendar task. WARNING: if the recurrence options are set incorrectly, which will not allow creating at least 1 additional recurrence, your calendar task will not be created, instead, an error message with code 422 will be returned.

Fill in only one of the values from your Office Payment Terms Settings.

Fill in the discount of the customer (must be a numerical value).

Fill in the rate of the customer (must be a numerical value).

Fill in the date of last service of the customer (allowed format - Y-m-d). For example - 2019-09-06.

Fill in the name of the customer that will be attached (the entity must already exists). For example - John Smith.

Fill in the short name of the source that will be attached (the entity must already exists). For example - Yelp.

Fill in the first name and last name of the agent that will be attached separated by space (the entity must already exists). For example - John Smith.

Fill in the title of the contract that will be attached (the entity must already exists). For example - Cancellation Policy.

Fill in the name of the payment type that will be attached (the entity must already exists). For example - Cash.

Fill in the short name of the tax item that will be attached (the entity must already exists). For example - Sales Tax.

Fill in the name of the industry that will be attached (the entity must already exists). For example - Apparel Stores.

Fill in the first name of the contact (which is required for each line-item and can not be blank but you can skip this field if the line-item was skipped).

Fill in the last name of the contact (which is required for each line-item and can not be blank but you can skip this field if the line-item was skipped).

Fill in the date of dob of the contact of the customer (allowed format - F j). For example - September 7.

Fill in the date of anniversary of the contact of the customer (allowed format - F j). For example - September 7.

Fill in the is primary flag of the contact of the customer (which is required for each line-item and can not be blank but you can skip this field if the line-item was skipped). If any count of contacts were passed - at least one must be a primary.

Fill in the email of the contact of the customer (must be a valid email address).

Fill in types of the email of the contact of the customer (which allows any count of the following values separated by comma: CONF, STATUS, PMT, INV). For example: PMT,STATUS.

Fill in the phone of the contact of the customer (must match the format 000-000-0000).

Fill in the phone extension of the contact of the customer (max length is 5).

Fill in the street 1 of the location of the customer (which is required for each line-item and can not be blank but you can skip this field if the line-item was skipped).

Fill in the latitude of the location of the customer (must be a numerical value).

Fill in the longitude of the location of the customer (must be a numerical value).

Fill in the first name and last name of the contact that will be attached separated by space (the entity must exist in your entities contacts of the request). For example - John Smith.

Fill in the custom fields of the customer. Please check your Office Custom Fields Settings - all required items under Customer Custom Fields are required and can not be blank.