Overview
Pre-built tooling
✅ Authorization
✅ Authorization
✅ Read & write data
✅ Read & write data
Tools | Status |
---|---|
Pre-built integrations | 🚫 (time to contribute: <48h) |
API unification | ✅ |
2-way sync | ✅ |
Webhooks from Nango on data modifications | ✅ |
Real-time webhooks from 3rd-party API | 🚫 (time to contribute: <48h) |
Proxy requests | ✅ |
✅ Observability & data quality
✅ Observability & data quality
Tools | Status |
---|---|
HTTP request logging | ✅ |
End-to-type type safety | ✅ |
Data runtime validation | ✅ |
OpenTelemetry export | ✅ |
Slack alerts on errors | ✅ |
Integration status API | ✅ |
✅ Customization
✅ Customization
Tools | Status |
---|---|
Create or customize use-cases | ✅ |
Pre-configured pagination | 🚫 (time to contribute: <48h) |
Pre-configured rate-limit handling | 🚫 (time to contribute: <48h) |
Per-customer configurations | ✅ |
Pre-built integrations
No pre-built integration yet (time to contribute: <48h)Not seeing the integration you need? Build your own independently.
Access requirements
Pre-Requisites | Status | Comment |
---|---|---|
Paid dev account | ✅ | AutoTask API requires a paid account |
Paid test account | ✅ | Same as dev account |
Partnership | ❌ | Not required |
App review | ❌ | Not required |
Security audit | ❌ | Not required |
Setup guide
To connect to AutoTask, you’ll need:- API Integration Code: A 27-character tracking identifier for your API-only user
- API Username: The email address of your API-only user account
- API Secret: The secret for your API-only user account
- API Zone: Your AutoTask instance subdomain (e.g., webservices3, webservices1)
Steps:
- Log into your AutoTask instance as an administrator
- Create an API-only user account with appropriate permissions
- Generate an API Integration Code for tracking
- Note your API zone subdomain from your AutoTask URL
Need help getting started? Get help in the community.
Contribute improvements to the setup guide by editing this page
Useful links
Contribute useful links by editing this page
Connection configuration in Nango
- AutoTask requires a zone-specific subdomain for API access
- The API Integration Code is used for tracking and must be included in headers
- Authentication uses API_KEY auth with username/password credentials
API gotchas
- AutoTask requires the API Integration Code to be passed in the
APIIntegrationCode
header for all requests - The API zone (subdomain) varies by account and must be determined for each customer
- API rate limits apply and vary by account type
Contribute API gotchas by editing this page
Going further
Connect to AutoTask
Guide to connect to AutoTask using Nango Connect.