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 interacts with the Autotask REST API to perform various operations on different resources within Autotask. Specifically, for the Resource 'resource' and Operation 'whoAmI', it retrieves information about the currently authenticated user or resource context. This is useful for workflows that need to confirm or utilize the identity details of the API user or resource executing the workflow, such as logging, conditional logic based on user identity, or auditing.
Properties
| Name | Meaning |
|---|---|
| Add Picklist Labels | Determines whether to automatically add '_label' fields for picklist fields to provide human-readable values. Labels are not added for empty values. |
| Add Reference Labels | Determines whether to automatically add '_label' fields for reference fields to provide human-readable values. Labels are not added for empty values. |
| Select Columns Names or IDs. | Specifies which fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included regardless of selection. |
Output
JSON
id- Unique identifier of the resource or username- Name of the resource or useremail- Email address of the resource or userrole- Role or position of the resource or useradditionalProperties- Other relevant properties returned by the 'whoAmI' operation, such as department, status, or custom fields
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If the node returns an authentication error, verify that the API key credential is correctly configured and has sufficient permissions.
- If no data is returned, ensure that the 'whoAmI' operation is supported for the selected resource and that the API user has access rights.
- Errors related to missing fields may occur if 'Select Columns' are specified incorrectly; try leaving it empty to retrieve all fields.