AutoTask

Overview

Pre-built tooling

✅ Authorization
ToolsStatus
Pre-built authorization (API Key)✅
Pre-built authorization UI✅
Custom authorization UI✅
End-user authorization guide✅
Expired credentials detection✅
✅ Read & write data
ToolsStatus
Pre-built integrations🚫 (time to contribute: <48h)
API unification✅
2-way sync✅
Webhooks from Tenklo on data modifications✅
Real-time webhooks from 3rd-party API✅
Proxy requests✅
✅ Observability & data quality
ToolsStatus
HTTP request logging✅
End-to-end type safety✅
Data runtime validation✅
OpenTelemetry export✅
Slack alerts on errors✅
Integration status API✅
✅ Customization
ToolsStatus
Create or customize use-cases✅
Pre-configured pagination🚫 (time to contribute: <48h)
Pre-configured rate-limit handling🚫 (time to contribute: <48h)
Per-customer configurations✅

No pre-built syncs or actions available yet.

Not seeing the integration you need? Build your own independently.

Access requirements

Pre-RequisitesStatusComment
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:

  1. API Integration Code: A 27-character tracking identifier for your API-only user
  2. API Username: The email address of your API-only user account
  3. API Secret: The secret for your API-only user account
  4. API Zone: Your AutoTask instance subdomain (e.g., webservices3, webservices1)

Steps:

  1. Log into your AutoTask instance as an administrator
  2. Create an API-only user account with appropriate permissions
  3. Generate an API Integration Code for tracking
  4. Note your API zone subdomain from your AutoTask URL

📚 AutoTask Integration Guides

Need help getting started? Get help in the community.
Contribute improvements to the setup guide by editing this page
Contribute useful links by editing this page

Connection configuration in Tenklo

  • 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 Tenklo Connect.

On this page