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
The node's 'Get Many' operation for the 'Time Entry' resource retrieves multiple time entry records from the Autotask system. It is useful for scenarios where users need to fetch a list of time entries for reporting, analysis, or integration purposes. For example, a user might want to extract all time entries logged within a specific period or by certain users to generate timesheet reports or to synchronize time tracking data with other systems.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the time entry records to retrieve and map in the output. This allows users to specify exactly which data points they want to include, optimizing data handling and performance. |
| Get All | Determines whether to return all available time entry records or limit the number of records returned. |
| Max Records | Specifies the maximum number of time entry records to return when 'Get All' is set to false. The value can range from 1 to 500. |
| Add Picklist Labels | Indicates whether to add additional fields with human-readable labels for picklist fields in the time entry data. This helps in making the output more understandable. |
| Add Reference Labels | Indicates whether to add additional fields with human-readable labels for reference fields in the time entry data. |
| Select Columns Names or IDs. | Allows users to select specific columns (fields) by name or ID to include in the response. If no fields are selected, all fields are returned by default. The ID field is always included. |
| Flatten User-Defined Fields | Determines whether user-defined fields (UDFs) should be brought up to the top level of each time entry object instead of being nested inside a userDefinedFields array, simplifying access to these fields. |
Output
JSON
id- Unique identifier of the time entry record.fieldName_label- Human-readable label for picklist or reference fields if 'Add Picklist Labels' or 'Add Reference Labels' is enabled.
userDefinedFieldsudfName- User-defined fields nested or flattened depending on 'Flatten User-Defined Fields' setting.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the query parameters and field selections are correct and that the Autotask account has time entries matching the criteria.
- If the node fails with authentication errors, ensure the API key credential is valid and has sufficient permissions.
- When selecting fields, if some expected fields are missing, check that the field names or IDs are correct and supported by the Autotask API for time entries.