IMPORTANT: After updating this node to a new version, a restart of your n8n instance is highly recommended to ensure all changes are properly applied.
This is an n8n community node for integrating with Autotask PSA. It provides a comprehensive set of operations to interact with Autotask entities through their REST API.
n8n is a fair-code licensed workflow automation platform.
Installation
Authentication
Features
Usage
Configuration
Limitations
Troubleshooting
Resources
Support
License
Follow these steps to install this node:
# Install with npm
npm install n8n-nodes-autotask
# Install with pnpm
pnpm install n8n-nodes-autotaskRequirements:
- n8n version 1.0.0 or later
- Node.js version 18.10 or later
- pnpm version 9.1 or later (if using pnpm)
To use this node, you need to have API access to your Autotask instance. Follow these steps to set up authentication:
- In Autotask, go to Admin > API User Security
- Create or select an API user
- Note the API Integration Code, Username, and Secret
- In n8n, create a new credential of type Autotask API
- Enter your API Integration Code, Username, and Secret
- Select your Autotask zone
- Select your timezone (affects how dates and times are displayed and entered)
- Configure caching options as needed (this will cache dynamically fetched field picklists)
The node supports the following Autotask resources:
| Resource | Description |
|---|---|
| API Threshold | Check Autotask API usage limits and current usage levels |
| Billing Code | Manage billing codes for time entries and charges |
| Company | Manage organisations in Autotask |
| Company Alert | Manage alerts associated with companies |
| Company Location | Manage locations for companies |
| Company Note | Manage notes attached to companies |
| Company Webhook | Manage webhooks for company events |
| Configuration Item | Manage configuration items (CIs) for companies |
| Configuration Item Billing Product Association | Manage product associations for configuration items |
| Configuration Item Category | Manage categories for configuration items |
| Configuration Item Category UDF Association | Manage UDF associations for CI categories |
| Configuration Item DNS Record | Manage DNS records for configuration items |
| Configuration Item Note | Manage notes for configuration items |
| Configuration Item Related Item | Manage related items for configuration items |
| Configuration Item SSL Subject Alternative Name | Manage SSL alternative names for configuration items |
| Configuration Item Type | Manage types for configuration items |
| Configuration Item Webhook | Manage webhooks for configuration item events |
| Contact | Manage contacts associated with companies |
| Contact Groups | Manage contact groups |
| Contact Group Contacts | Manage contacts within contact groups |
| Contact Webhook | Manage webhooks for contact events |
| Contract | Manage contracts for companies |
| Contract Billing Rules | Manage billing rules for contracts |
| Contract Block | Manage block hour contracts |
| Contract Block Hour Factor | Manage hour factors for block hour contracts |
| Contract Charge | Manage charges associated with contracts |
| Contract Exclusion Billing Codes | Manage excluded billing codes for contracts |
| Contract Exclusion Roles | Manage excluded roles for contracts |
| Contract Exclusion Set Excluded Roles | Manage excluded roles within exclusion sets |
| Contract Exclusion Set Excluded Work Types | Manage excluded work types within exclusion sets |
| Contract Exclusion Sets | Manage exclusion sets for contracts |
| Contract Milestone | Manage milestones for contracts |
| Contract Note | Manage notes attached to contracts |
| Contract Rate | Manage rates for contract services |
| Contract Retainers | Manage retainers for contracts |
| Contract Role Costs | Manage role costs for contracts |
| Contract Service | Manage services within contracts |
| Contract Service Adjustments | Manage adjustments for contract services |
| Contract Service Bundle Adjustments | Manage adjustments for service bundles |
| Contract Service Bundles | Manage service bundles within contracts |
| Contract Service Bundle Units | Manage service bundle units |
| Contract Service Unit | Manage service units for contracts |
| Contract Ticket Purchases | Manage ticket purchases for contracts |
| Domain Registrars | Manage domain registrars |
| Holiday | Manage holiday dates |
| Holiday Set | Manage holiday sets for resources |
| Invoices | Manage invoices |
| Notification History | View notification history |
| Opportunity | Manage sales opportunities |
| Product | Manage products in the catalogue |
| Product Vendors | Manage vendor associations for products |
| Project | Manage projects |
| Project Charge | Manage charges associated with projects |
| Project Note | Manage notes attached to projects |
| Project Phase | Manage phases within projects |
| Project Task | Manage tasks within projects |
| Resource | Manage staff resources |
| Resource Role | Manage department/role relationships, service desk queues, and service desk roles |
| Roles | Manage roles in the system |
| Search Filter | Build advanced search filters |
| Service | Manage services offered to clients |
| Service Call | Manage service calls |
| Survey | Manage customer surveys |
| Survey Results | Manage results from customer surveys |
| Ticket | Manage service tickets |
| Ticket History | View historical changes to tickets |
| Ticket Note | Manage notes attached to tickets |
| Ticket Note Webhook | Manage webhooks for ticket note events |
| Ticket Webhook | Manage webhooks for ticket events |
| Time Entry | Manage time entries for billing |
For most resources, the following operations are available:
- Create: Add new records
- Read: Retrieve a single record by ID
- Update: Modify existing records
- Delete: Remove records
-
Get Many: Retrieve multiple records with basic filtering options. This operation allows you to:
- Filter records using simple field conditions (equals)
- Filtering on User Defined Fields (UDFs)
- Automatically paginate through large result sets
- Choose to get all results or limit to a specific number (1-500)
- Set a maximum number of records to return when not retrieving all records
- Select specific columns to return in the response
- Add human-readable labels for picklist and reference fields
- Flatten User-Defined Fields for easier access in workflows
-
Get Many Advanced: Build complex queries with multiple filter conditions and logical operators. This operation provides:
- Support for complex AND/OR logic in filters
- Nested condition groups for sophisticated queries
- Filtering on User Defined Fields (UDFs)
- Advanced operators like contains, beginsWith, endsWith, exists, notExists
- Support for IN and NOT IN operators with multiple values
- Choose to get all results or limit to a specific number (1-500)
- Set a maximum number of records to return when not retrieving all records
- Select specific columns to return in the response
- Add human-readable labels for picklist and reference fields
- Flatten User-Defined Fields for easier access in workflows
- Date-based filtering with automatic timezone handling
- Count: Get the number of matching records
- Get Entity Info: Retrieve metadata about the entity
- Get Field Info: Retrieve field definitions for the selected entity
For webhook resources (Company Webhook, Contact Webhook, Configuration Item Webhook, Ticket Webhook, Ticket Note Webhook), the following operations are available:
- Get: Retrieve a single webhook by ID
- Get Many: Retrieve multiple webhooks with basic filtering
- Delete: Remove a webhook
The node includes an Autotask Trigger node that can receive webhook events from Autotask. The trigger supports:
- Events for multiple entity types (Companies, Contacts, Tickets, Configuration Items, Ticket Notes)
- Create, Update, and Delete events
- Field selection for webhook payloads (specify which fields to include)
- Resource exclusion (exclude specific resources from triggering the workflow)
- Email notifications for webhook delivery failures
- Threshold notifications for monitoring webhook performance
- Automatic webhook registration and cleanup
- Secure payload verification with HMAC signatures
- Resource Mapping: Dynamically map fields based on entity definitions
- Advanced Filtering: Build complex queries with multiple conditions
- Column Selection: Choose specific fields to return in get operations
- Picklist Label Enrichment: Automatically add human-readable labels for picklist fields
- Reference Label Enrichment: Add human-readable labels for reference fields
- UDF Flattening: Bring user-defined fields up to the top level of response objects for easier access
- File-based Caching: Improved performance with persistent caching that can be shared between workflows and runs
- Timezone Handling: Automatic conversion between local time and UTC
- API Usage Monitoring: Check current API usage thresholds and limits using the API Threshold resource to help prevent hitting rate limits and ensure smooth operations
The API Threshold resource provides a simple way to monitor your Autotask API usage limits and current consumption. This helps users:
- Track how many API requests have been made in the current timeframe
- See the maximum allowed requests (threshold limit)
- View the usage as a percentage and categorized level (Normal, Moderate, High, Critical)
- Calculate remaining available requests
- Monitor timeframe duration for rate limits
This is particularly useful for workflows that make many API calls, allowing you to implement conditional logic based on current usage levels to avoid hitting rate limits and ensure continuous operation.
This node can be used as a tool by AI agents in n8n workflows. This allows AI agents to interact with Autotask PSA, performing operations like retrieving company information, creating tickets, or updating contacts.
Currently, n8n only allows core nodes to be used as tools by default. To use this community node as a tool, you need to:
- Set the environment variable
N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGEtotruewhen running n8n. - Add the Autotask node as a tool in your AI agent workflow.
For the node to be usable as an AI tool, you must set the following environment variable:
N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=trueThis can be done by:
- Adding it to your .env file
- Setting it in your system environment variables
- Including it in your Docker or container configuration
- Adding it to your startup command (e.g.,
N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true n8n start)
Without this environment variable set to true, n8n will not allow AI agents to use this community node as a tool.
An AI agent might use the Autotask node to:
- Retrieve information about a company or contact
- Create a new ticket based on user input
- Update the status of an existing ticket
- Add notes to a ticket or company record
- Search for tickets matching specific criteria
- Add an Autotask node to your workflow
- Select Ticket as the resource
- Select Create as the operation
- Configure the required fields (Title, Status, etc.)
- Connect to a trigger or previous node
- Execute the workflow
- Add an Autotask node to your workflow
- Select Project as the resource
- Select Get Many as the operation
- Add filter conditions (e.g., Status equals "Active")
- Choose whether to retrieve all results or limit the number:
- Toggle "Get All" to true to retrieve all matching records
- Toggle "Get All" to false and set "Max Records" (1-500) to limit the results
- Connect to a trigger or previous node
- Execute the workflow
- Add an Autotask node to your workflow
- Select Ticket as the resource
- Select Get Many as the operation
- Add filter conditions as needed
- Enable Select Columns to choose specific fields to return
- Select only the fields you need in the response (improves performance)
- Enable Add Picklist Labels to get human-readable values for picklist fields
- Enable Add Reference Labels to get human-readable values for reference fields
- Enable Flatten User-Defined Fields to bring UDFs to the top level of response objects
- Execute the workflow to get tickets with only the selected fields and human-readable labels
- Add an Autotask node to your workflow
- Select Ticket as the resource
- Select Get Many Advanced as the operation
- Build a complex filter, for example:
Valid filter operators and filter documentation can be found here
{ "filter": [ { "op": "and", "items": [ { "field": "status", "op": "noteq", "value": 5 }, { "op": "or", "items": [ { "field": "priority", "op": "eq", "value": 6 }, { "field": "dueDateTime", "op": "lt", "value": "{{ $now.plus(3, 'days').toLocal()}}" } ] } ] } ] } - Choose whether to retrieve all results or limit the number:
- Toggle "Get All" to true to retrieve all matching records
- Toggle "Get All" to false and set "Max Records" (1-500) to limit the results
- Enable Select Columns to choose specific fields to return
- Enable Add Reference Labels and Add Picklist Labels for human-readable values
- Execute the workflow to retrieve tickets that are not complete AND either have priority 6 OR are due within the next 3 days
- Add an Autotask node to your workflow
- Select API Threshold as the resource
- The operation Get API Usage will be automatically selected (it's the only available operation)
- Execute the node to receive current API usage information including:
- Current usage count
- Maximum threshold (limit)
- Usage percentage
- Usage level (Normal, Moderate, High, Critical)
- Remaining requests
- Timeframe duration
- You can use this information with IF nodes to implement conditional logic:
- Pause workflows when usage is too high
- Throttle requests during peak usage periods
- Log warnings when approaching limits
- Only execute non-critical operations when usage is below certain thresholds
Many Autotask entities have parent-child relationships (e.g., Companies and Contacts). To work with these:
- First, retrieve or create the parent entity
- Use the parent entity's ID in the child entity operations
- For example, to create a Contact for a Company:
- First node: Get or create the Company
- Second node: Create a Contact with the Company ID
- Add an Autotask Trigger node to your workflow
- Select the entity type to monitor (Companies, Contacts, Tickets, etc.)
- Select the events to subscribe to (Create, Update, Delete)
- Configure the webhook URL (n8n will handle this automatically)
- Optionally specify fields to include in the webhook payload
- Optionally exclude specific resources from triggering the workflow
- Configure email notifications for webhook delivery failures if needed
- Save and activate the workflow
- The node will automatically register the webhook with Autotask
- When events occur in Autotask, they will trigger your workflow
- When the workflow is deactivated, the webhook will be automatically removed
The node includes an enhanced file-based caching system to improve performance by reducing API calls:
- Enable Field Caching: Toggle caching on/off
- Cache TTL: How long to cache field values (in seconds)
- Cache Entity Info: Whether to cache entity information and field definitions
- Entity Info TTL: How long to cache entity information
- Cache Reference Fields: Whether to cache reference field values
- Reference Fields TTL: How long to cache reference field values
- Cache Picklists: Whether to cache picklist values
- Picklists TTL: How long to cache picklist values
- File-based Cache: Cache is stored in files that can be shared between workflows and runs
- Cache Directory: Optional path to a directory where cache files will be stored
IMPORTANT: This node uses dynamic picklists and field enrichers to convert numerical values into human-readable labels through dynamic lookups. It's strongly recommended to keep caching enabled to avoid excessive API calls. Without caching, each picklist and reference field lookup requires separate API calls, which can quickly consume your API rate limits, especially in workflows with many operations or large data sets.
The node provides options to enrich entities with human-readable labels and simplify field access:
- Add Picklist Labels: Adds "_label" fields for picklist values (e.g., Status_label: "In Progress")
- Add Reference Labels: Adds "_label" fields for reference values (e.g., Company_label: "Acme Corporation")
- Flatten User-Defined Fields: When enabled, brings UDFs up to the top level of each response object for easier access instead of being nested in the userDefinedFields array (maintains the original array for backward compatibility)
To improve performance and reduce payload size, you can select specific columns to return:
- Select Columns: Choose which fields to include in the response
- Works with all get operations (get, getMany, getManyAdvanced)
- Compatible with label enrichment features
All dates and times in the Autotask API are in UTC. The node automatically converts between your selected timezone and UTC:
- When creating or updating records, local times are converted to UTC
- When retrieving records, UTC times are converted to your local timezone
- The timezone is configured in the credentials
- Maximum 500 records per page in query results
- Maximum 50 pages per query operation
- Maximum 500 OR conditions in filters
- Maximum 1 User Defined Field per query
- Some entities may not support all operations (e.g., Project Phases cannot be deleted)
- Parent-child relationships require specific handling
- Some fields may be read-only or have specific validation rules
- Large queries may be slow and should be optimised with filters
- Column selection can significantly improve performance by reducing payload size
- Complex workflows with many API calls may hit rate limits
- Disabling caching when using picklist or reference label enrichment can lead to a high volume of API calls, potentially triggering rate limits. Each field being enriched requires a separate API call when cache is not available.
- Authentication Errors: Verify your API credentials and ensure the API user has appropriate permissions
- Field Validation Errors: Check field requirements in the Autotask API documentation
- Rate Limiting: If you encounter rate limiting, reduce the frequency of API calls or implement retry logic
If you encounter any bugs or issues with this integration:
- Check the GitHub Issues to see if the problem has already been reported
- If not, please submit a new issue with:
- A clear description of the problem
- Steps to reproduce the issue
- Expected vs actual behaviour
- Your environment details (n8n version, Node.js version)
- Any relevant error messages or screenshots
Bug reports should be submitted via GitHub at: https://github.com/msoukhomlinov/n8n-nodes-autotask/issues
If you find this node helpful and want to support its ongoing development, you can buy me a coffee:
Your support helps maintain this project and develop new features.
Below are the 5 most recent changes. For a complete changelog, see CHANGELOG.md.
- Fixed issue with custom URL not being used for pagination requests:
- Modified request handling to use custom URL consistently for all API calls
- Fixed pagination URLs to work properly with proxy/custom URL configurations
- Ensures all requests in a paginated sequence use the same base URL
- Updated documentation in README:
- Corrected Advanced Example for Complex Filtering with Get Many Advanced operation
- Updated "Other (Use Zone Information API)" option in credentials to "Other (Custom URL)":
- Modified the credential option to better reflect its actual functionality
- The custom URL is now used directly without any zone lookup
- Improved error handling to display specific API error messages in n8n UI:
- Enhanced error extraction from API responses for all status codes
- Enhanced Search Filter resource with new "Dynamic Build" operation:
- Added entity-driven field selection workflow distinct from standard "Build" operation
- Implemented dynamic field loading based on entity selection
- Added UDF field support with clear type indicators