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
Tool → Execute
AI-generatedOverview
The node provides a flexible interface to execute various operations on different resources within the Autotask PSA system using a generic 'tool' resource. It allows users to specify the exact resource and operation to perform in a single string format (e.g., 'ticket.create', 'company.getMany'). This node is beneficial for scenarios where users want to perform custom or less common operations that may not have dedicated nodes or when they want to dynamically specify operations at runtime. For example, creating a new ticket, updating a company record, or retrieving multiple contacts can all be done through this node by specifying the appropriate operation and providing the necessary data.
Use Case Examples
- Create a new ticket by setting targetOperation to 'ticket.create' and providing ticket details in requestData.
- Retrieve multiple companies by setting targetOperation to 'company.getMany' and optionally specifying filters in requestData.
- Update a contact by setting targetOperation to 'contact.update', specifying the entityId, and providing updated fields in requestData.
Properties
| Name | Meaning |
|---|---|
| Target Operation | Specifies the resource and operation to execute in the format 'resource.operation' (e.g., 'ticket.create'). This determines what action the node will perform. |
| Entity ID | The ID of the specific entity to target for operations like get, update, or delete. Not required for create or getMany operations. |
| Request Data (JSON) | JSON object containing the data for the operation. For create/update operations, this includes field values. For read operations, this can include filters. |
| Select Columns (JSON) | An array of field names to return for read operations. An empty array returns all fields. |
| Dry Run | If enabled, the node validates the request and shows what would be sent to the API without actually executing the operation. Useful for testing and validation. |
| Allow Write Operations | Determines whether write operations (create, update, delete) are permitted. Disabled by default for safety to prevent unintended data changes. |
| Allow Dry Run for Writes | Allows dry-run previews for write operations even when write operations are disabled, enabling validation without execution. |
| Allowed Resources (JSON) | An array of resource names that are permitted for operations. An empty array means all resources are allowed. This is used to restrict operations for security purposes. |
Output
JSON
json- The JSON response from the executed operation, containing the result data or error information.
Dependencies
- Requires an API key credential for Autotask PSA REST API authentication.
Troubleshooting
- If the node throws an error about unsupported resources, verify that the resource name in the targetOperation is correct and allowed by the allowedResources setting.
- If write operations fail or are blocked, check that 'Allow Write Operations' is enabled if you intend to perform create, update, or delete actions.
- For dry run mode, ensure that the requestData JSON is correctly formatted to avoid validation errors.
- Authentication errors indicate issues with the provided API credentials; verify the API key and integration code are correct and have necessary permissions.
Links
- Autotask n8n Node GitHub Repository - Source code and documentation for the Autotask node in n8n.
- Autotask PSA REST API Documentation - Official API documentation for Autotask PSA REST API endpoints and usage.