Actions524
- AI Helper Actions
- Tool Actions
- API Threshold Actions
- Appointment Actions
- Billing Code Actions
- Billing Items Actions
- Change Request Link Actions
- Checklist Library Actions
- Checklist Library Item Actions
- Classification Icon Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Company Site Configuration Actions
- Configuration Item Actions
- Configuration Item Billing Product Association 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
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Contract Exclusion Billing Code 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 Rate Actions
- Contract Role Costs Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Department Actions
- Project Phase Actions
- Quote Item Actions
- Quote Location Actions
- Quote Template Actions
- Resource Actions
- Resource Role Actions
- Resource Role Queue Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Subscription Actions
- Subscription Period Actions
- Ticket Category Actions
- Ticket Category Field Default Actions
- Ticket History Actions
- Ticket Note Actions
Resource → Who Am I
AI-generatedOverview
The 'Resource' node with the 'Who Am I' operation in the Autotask integration allows users to retrieve information about the current authenticated user or context. This operation is useful for scenarios where you need to verify or display the identity details of the API user making the request, such as in user profile displays, audit logs, or conditional workflows based on user identity.
Use Case Examples
- A workflow that fetches the current user's details to personalize subsequent actions.
- An automation that logs the identity of the user performing certain operations for audit purposes.
Properties
| Name | Meaning |
|---|---|
| Cache Response | Whether to cache the API response for this operation to reduce repeated Autotask calls. |
| Cache TTL (seconds) | Maximum time to keep a cached API response for this operation (in seconds). If a valid cached response exists for the same parameters, it will be returned immediately and no new API request will be sent until the TTL expires. |
| Add Picklist Labels | Whether to automatically add '_label' fields for picklist fields with human-readable values (no labels will be added for empty values). |
| Add Reference Labels | Whether to automatically add '_label' fields for reference fields with human-readable values (no labels will be added for empty values). |
| Select Columns Names or IDs. | Choose which fields to include in the response. If no fields are selected, all fields will be returned. The ID field is always included regardless of selection. |
Output
JSON
id- The unique identifier of the authenticated user or resource.username- The username of the authenticated user.email- The email address associated with the authenticated user.roles- Roles assigned to the authenticated user.otherDetails- Additional details about the authenticated user or context returned by the API.
Dependencies
- Requires an API key credential for Autotask API authentication.
Troubleshooting
- If the node returns authentication errors, verify that the API credentials are correct and have the necessary permissions.
- If caching is enabled but stale data is returned, adjust the Cache TTL or disable caching to ensure fresh data.
- If expected fields are missing in the response, check the 'Select Columns' property to ensure the desired fields are selected.
Links
- Autotask REST API Documentation - Official documentation for Autotask REST API endpoints and usage.
- Autotask n8n Node GitHub Repository - Source code and additional information about the Autotask node for n8n.