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 integrates with the Autotask REST API to create a new Time Entry record. It allows users to map various fields of a time entry resource dynamically, enabling automation of time tracking and billing processes within Autotask. Typical use cases include logging work hours for projects, tasks, or tickets automatically from other systems or workflows, facilitating accurate time management and invoicing.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the fields and their values to be mapped to the new Time Entry record. This property supports dynamic mapping of multiple fields, allowing users to specify exactly which data to send when creating the time entry. |
Output
JSON
id- The unique identifier of the created Time Entry.fields- An object containing the details of the created Time Entry, reflecting the mapped fields and their values.createdAt- Timestamp indicating when the Time Entry was created.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the node throws an error about missing or invalid fields, verify that the 'Fields' property is correctly mapped with all required Time Entry fields as per Autotask API documentation.
- Authentication errors indicate issues with the provided API credentials; ensure the API key is valid and has sufficient permissions.
- Network or API errors may occur if the Autotask service is unreachable or if rate limits are exceeded; retry after some time or check network connectivity.