How it works
Step 1: Input Data
The action receives a list of PSA time entry objects, typically from a “Find Entities” action or a trigger. It also takes a list of fields to update, usually from an AI analysis action such as “Time Entry QA”.Step 2: Field Update Preparation
The action prepares the list of changes:- It combines suggested updates with any specified additional updates.
- If “Allow Clearing Fields” is set to False (default), it filters out updates that would set a field to an empty value.
Step 3: PSA Interaction
For each time entry:- The action constructs the payload for your PSA.
- It makes an API call to apply the changes.
- For ConnectWise, it temporarily disables email notifications to prevent spam. The flag is restored after all time entries for that ticket are processed.
Step 4: Output Generation
The action generates a message for each updated time entry that details the fields changed.Configuration options
Default Data
The list of PSA time entry objects that this action processes and updates. This input is typically provided by a “Find Entities” action or directly from a workflow trigger.Default Fields to Update
A list of field update instructions, usually generated by a preceding AI action such as “Time Entry QA”. Each instruction specifies the time entry ID, the field to change, and its new value.Allow Clearing Fields
Default: False - Determines whether the action can set fields to an empty or null value.- If False (default), updates that clear a field are ignored.
- If True, the action proceeds with updates that set fields to empty or null.
Update Additional Fields
Default: False - Set this to True to configure specific, static field updates.Additional Fields to Update
This section is enabled when “Update Additional Fields” is True. It lets you define updates to apply to all time entries processed by this action. Use additional fields for a single static change, such as always marking filtered time entries as non-billable. For changes that depend on the content of each time entry, use the output of an AI action such as “Time Entry QA” or “Time Entries Triage”.Is Non-Billable (Autotask only)
Set whether the time entry is non-billable. Choose “True”, “False”, or “Do not update”. ConnectWise typically handles non-billable status through Work Type or other specific fields.What you’ll get
- Executions: Messages confirming the update of each time entry and detailing the changes made
- Internal Messages: Messages for internal MSP use that can be used in subsequent actions such as “Add Ticket Note”
- Zero Credits: Updating time entry fields does not consume any credits
Use cases
Correct Time Entry after Automated QA
Correct Time Entry after Automated QA
Trigger: Time Entry Created
Action 1: Time Entry QA - Analyzes the new time entry based on defined criteria
Action 2: Update Time Entry Fields - Takes the suggestions from “Time Entry QA” and applies corrections like changing work type or billable flag
Standardize Non-Billable Time Entries
Standardize Non-Billable Time Entries
Trigger: Time Entry Created
Filter: Time entry’s associated ticket has title containing “Internal Meeting” OR time entry notes contain “Internal Training”
Action: Update Time Entry Fields - Set “Is Non-Billable” to “True” for Autotask, or update Work Type for ConnectWise
Best practices
ConnectWise Notifications
For ConnectWise users, this action temporarily modifies the email notification flag on the parent ticket to prevent excessive notifications. This flag is restored after all time entries for that ticket are processed.Example workflows
Billing Compliance Check
Billing Compliance Check
- Trigger: Time Entry Created
- Time Entries Triage - Check billing compliance and work type accuracy
- Update Time Entry Fields - Apply triage suggestions for compliance
Available field updates
You can update various time entry fields including:- Work type - Change the service category or work classification
- Billable status - Set whether the time is billable or non-billable
- Notes/description - Update or append to the time entry details
- Hours logged - Modify the time amount (use with caution)
- Custom fields - Update any custom fields specific to your PSA setup
Safety features
Data Protection
- Default behavior prevents accidental field clearing
- Individual time entry failures don’t stop the entire batch
- Detailed logging of all changes made
Notification Management
- ConnectWise: Temporarily disables automatic email notifications during updates
- Autotask: Respects existing notification settings
Validation
- Ensures time entries exist before attempting updates
- Validates field names match PSA configuration
- Confirms new values are appropriate for field types
