Actions389
- Contract Actions
- Ticket History Actions
- Ticket Note Webhook Actions
- Ticket Note Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Role Actions
- Resource Role Actions
- Search Filter Actions
- Service Actions
- Skill Actions
- Service Call Actions
- Survey Results Actions
- Survey Actions
- Ticket Actions
- Opportunity Actions
- Notification History Actions
- Invoice Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Phase Actions
- Project Task Actions
- Project Note Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Service Bundle Adjustment Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code Actions
- Contract Rate Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Role Costs Actions
- Contact Groups Actions
- Contact Actions
- Contact Webhook Actions
- Contact Group Contacts Actions
- Contract Block Hour Factor Actions
- Contract Block Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Company Alert Actions
- Company Actions
- Billing Code Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Overview
This node operation retrieves multiple time entry records from the Autotask system using an advanced filtering mechanism. It is useful for users who need to query time entries with complex criteria beyond simple filters, such as date ranges, specific user IDs, or custom conditions. For example, a project manager might use this to extract all time entries logged by a particular team within a certain period for reporting or billing purposes.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching time entry records or limit the number of results. |
| Max Records | Specifies the maximum number of time entry records to return when 'Get All' is false. The value must be between 1 and 500. |
| Advanced Filter | A required JSON string containing a 'filter' array that defines the Autotask API query criteria for selecting time entries. This allows complex queries using Autotask's REST API filtering syntax. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix to the output for picklist fields, providing human-readable labels instead of raw values. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix to the output for reference fields, providing human-readable labels. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are moved to the top level of each returned object instead of being nested inside a 'userDefinedFields' array. |
Output
JSON
id- Unique identifier of the time entry record.fieldName- Various fields of the time entry as specified by the selected columns or all fields if none selected.fieldName_label- Human-readable label for picklist or reference fields if label addition is enabled.userDefinedFields- Array of user-defined fields associated with the time entry, unless flattened to top-level properties.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in the 'Advanced Filter' property will cause query errors. Ensure the JSON string is well-formed and follows Autotask API filter syntax.
- Requesting too many records without pagination or limits may cause timeouts or API rate limiting.
- Selecting fields that do not exist or are misspelled in 'Select Columns' may result in incomplete or error responses.
- If labels are not appearing as expected, verify that 'Add Picklist Labels' and 'Add Reference Labels' are enabled and that the fields support labels.
- Ensure the API credentials have sufficient permissions to read time entry data.
Links
- Autotask API Basic Query Calls - Official documentation for constructing advanced filter queries for Autotask REST API.