busybusy Integrations

Triggers when a post is created.

Triggers when a cost code is archived within busybusy.

Triggers when a cost code group is edited in busybusy.

Triggers when a custom daily sign-off question is flagged in busybusy.

Triggers when an employee submits an answer to a custom daily sign-off question in busybusy.

Triggers when a Daily Project Report is deleted.

Triggers when a document gets uploaded to busybusy.

Triggers when the details of an existing document are updated in busybusy.

Triggers when a new employee group is created in busybusy.

Triggers when an employee group is edited in busybusy.

Triggers when an existing piece of equipment is deleted in busybusy.

Triggers when an existing piece of equipment is updated in busybusy.

Triggers when a reported safety incident is deleted in busybusy.

Triggers when a reported safety incident is marked as completed in busybusy.

Triggers when an employee reports an injury when submitting their Daily Sign-Off answers.

Triggers when a safety inspection is submitted in busybusy.

Triggers when a note (sometimes referred to as a "media collection") is created in busybusy. There is a separate trigger for adding photos to an existing note, "Photos & Notes: Photo Uploaded".

Triggers when a new comment is added to a photo in busybusy.

Triggers when an employee is archived within busybusy.

Triggers when an employee is updated in busybusy. This includes edits to the employee's settings, and their wage history. It will also be activated if an employee is unarchived. Note that updates can also occur for internal reasons. When using this trigger, it should be understood that some update triggers won't have meaningful data changes. This trigger is intended to assist in keeping datasets in sync.

Triggers when a photo is annotated in busybusy.

Triggers when a new safety observation is submitted in busybusy.

Triggers when a photo verification fails with an accuracy rating lower than 90%.

Triggers when a progress entry has been deleted.

Triggers when a project, or subproject, is archived within busybusy.

Triggers when a new project group is created in busybusy.

Triggers when a project group is edited in busybusy.

Triggers when a recurring schedule item is created in busybusy.

Triggers when a safety training is marked as complete in busybusy.

Triggers when the details of an existing safety training are edited in busybusy.

Triggers when a schedule item is deleted in busybusy.

Triggers when a schedule item is edited in busybusy.

Triggers when a time entry is deleted.

Triggers when an employee reports inaccurate time when submitting their Daily Sign-Off answers.

Triggers when a time-off request is approved. The "Time Off Created" trigger will also be activated.

Triggers when a time-off entry is deleted.

Triggers when a time-off request is denied.

Triggers when a post is deleted.

Triggers when a cost code is created in busybusy.

Triggers when a cost code is updated in busybusy. This includes edits to the cost code's settings. Note that updates can also occur for internal reasons, including if a cost code is unarchived. When using this trigger, it should be understood that some update triggers won't have meaningful data changes. This trigger is intended to assist in keeping datasets in sync.

Triggers when a flagged custom daily sign off question is reviewed and marked as processed in busybusy.

Triggers when a Daily Project Report is submitted.

Triggers when an employee is flagged when submitting their Daily Sign-In answers.

Triggers when a document is deleted in busybusy.

Triggers when the details of a processed observation are edited in busybusy.

Triggers when an employee group is deleted in busybusy.

Triggers when a new piece of equipment is created in busybusy.

Triggers when an equipment hour meter is changed. This includes employee-submitted hour meter changes, as well as any automated updates to the machine's hour meter.

Triggers when an employee disables their required GPS in busybusy.

Triggers when a new safety incident is reported in busybusy.

Triggers when a safety incident has been reviewed and submitted in busybusy.

Triggers when a Daily Sign-Off reported injury is marked as processed.

Triggers when an employee clocks time outside of a project geofence and their location is flagged for review.

Triggers when a note is updated. This includes adding or modifying the description, changing the project, or if the entire note and all of its photos are deleted.

Triggers when a photo is added to an existing note in busybusy. There is a separate trigger for creating the note ("Photos & Notes: Note Created").

Triggers when an employee is created in busybusy.

Triggers when a new safety inspection is created and assigned in busybusy.

Triggers when a safety observation is processed in busybusy.

Triggers when an employee submits a new per diem request in busybusy.

Triggers when a new progress entry is submitted.

Triggers when a progress entry has been updated. Updates can include changing the progress quantity, changing either the project or the cost code, modifying or adding a note, or changing the progress entry's date. This trigger is intended to assist in keeping datasets in sync.

Triggers when a project or subproject is created in busybusy.

Triggers when a project group is deleted in busybusy.

Triggers when a project, or subproject, is updated in busybusy. This includes edits to the project's settings. This trigger will also be activated if a project is unarchived. When using this trigger, it should be understood that some update triggers won't have meaningful data changes. This trigger is intended to assist in keeping datasets in sync.

Triggers when an Observation, either open or processed, is deleted in busybusy.

Triggers when a safety training is deleted in busybusy.

Triggers when a new safety training is scheduled in busybusy.

Triggers when a schedule item is created in busybusy.

Triggers when a time entry is created, either from a clock in, or if manually created.

Triggers when a time entry is edited.

Triggers when a Daily Sign-Off time accuracy issue is marked as resolved.

Triggers when time off is created. This will also get triggered if a time-off request is approved.

Triggers when a time-off entry is edited.

Triggers when time off is requested by an employee.