Autotask setup checklist
Use this when wiring concorbit to a brand-new Autotask org. Tick off each item before you start a sync. For the longer narrative form, see Connecting.
In Autotask
Create an API user: Admin → Resources → New Resource → Resource Type API User
Set its Security Level to one that can read Tickets, Contacts, Companies, Resources, Contracts, ContractServices, TimeEntries
(Push later) the same Security Level needs Edit on Tickets, TicketNotes, TimeEntries
Set its email, which must be unique in your Autotask org. concorbit uses it for zone discovery
Set its Password (you won't paste this anywhere; Autotask uses it internally)
Set its Secret. This is what concorbit will use. Save it now; Autotask won't show it again
Generate an API Tracking Identifier under Admin → Integrations → API Tracking Identifiers. Give it a recognisable name like "concorbit". Save the integration code
In concorbit
Open Settings → Autotask
Paste the API user email, the secret, and the integration code
Click Connect, wait 2-3 seconds
Verify the connection card shows "healthy" and the recent activity log has a
createdevent(Session 2 onwards) configure mappings, then run your first picklist/resource sync
Sanity checks
Open
/admin/platform/api-health(super-admin only) and confirm the autotask provider card is rendering, with at least 2 calls in the last hour (zone discovery + validation)Try a deliberate disconnect/reconnect to make sure both sides handle it cleanly
What goes wrong, and where
| Symptom | Most-likely cause |
|---|---|
| "Could not find an Autotask zone for this email" | Typo in email, OR the API user was deleted in Autotask |
| "Autotask rejected the credentials" | Wrong secret OR wrong integration code |
| Connection healthy but no data flowing | Picklist sync hasn't run yet (Session 2 surface), or no mappings configured |
| Many 429 hits | Other tools also calling Autotask from the same account; reduce concurrent integrations |
Common Autotask Security Level templates that work
System Administrator: overkill, but works
Custom, concorbit Sync: read on every entity concorbit touches; edit on Tickets/TicketNotes/TimeEntries (when push lands). Recommended; minimum surface
Talk to your Autotask administrator if you're unsure which Security Level your API user has.