Autotask PSA
Connect NetLock RMM to Autotask PSA: alerts become tickets of the mapped company, the all-clear adds a note and sets the closing status, devices can be kept as configuration items, device counts go to contract services.
Autotask PSA
Requirements
- An API user with the security level
API User (API-only)and an API tracking identifier. The valueCustomdoes not require a partner contract. - For contract quantities, the user needs access to contracts. A security level with limited contract visibility cannot read the units.
Setup
- In
Settings → Integrations, open the Autotask PSA tile and chooseConnect. - Enter the
API user name, theSecretand theAPI tracking identifier. NetLock finds the zone of your database through the user name. - Under options, choose the
Status of new tickets, theDefault priority, theClosing status(usually Complete), theNote typeand theVisibility of the note. Choose the value for internal notes there. The lists come from your Autotask database. - If the ticket category of the API user requires a queue, choose a
Queue. Autotask also requires a due date unless the category sets one, so every ticket gets a due date based onDue after (hours). - Map each tenant to a company, or import companies and locations. Tenants without a mapping are not included.
- Optionally map locations and severities.
- Activate the connection.
Autotask allows 10,000 requests per hour per database across all integrations and limits parallel calls per endpoint. A job that hits a limit waits and then continues.
What goes to the vendor
For every alert that passes the filter of the connection: a title, the severity, tenant, location and device name, the source, first and last time seen, the alert text, and a link to the web console if the public console URL is set. Check that this matches your data processing agreements before you activate the connection.
With the asset sync on, also: device name, operating system, manufacturer, model, serial number, IP address and MAC address.
With contract items mapped, also: the device count of the mapped tenant per period.
What happens to a ticket
- An alert becomes a ticket of the mapped company. The reference
NetLock-Alert-<id>is stored in theExternal IDof the ticket and at the end of its title. Autotask limits the title to 255 and the description to 8,000 characters. - When the alert ends, the ticket gets a note with the type and visibility of the options, and it is set to the closing status if nobody is working on it.
- A ticket with a primary resource counts as assigned.
- If Autotask refuses the status, for example because of a required field, the ticket stays open with its note, and the history says
close_refused.
The behaviour is set in the Settings tab, see A.14.4. NetLock never deletes anything at the vendor.
Asset sync
The sync is off by default. Switch on Sync devices as assets, and choose a Product of configuration items, which Autotask requires, and a default type or a mapping of the device classes.
- A device is a configuration item with
NetLock-Device-<id>as reference number. NetLock reuses an existing item only on an exact match within the company. - The company of an item cannot change in Autotask, so a device that moved gets a new item at its new company. The old one stays.
- An alert of a synced device names its configuration item in the ticket.
Contract quantities
The Billing tab of the connection writes device counts to the services of recurring contracts, see A.14.10.
- The list holds the services of the recurring contracts of the company that run in the period.
- Contracts with
ContractServiceBundlesdo not appear in the list, only single services. - Autotask stores units in rows per period and accepts only changes. NetLock reads the units at the effective date and writes the difference as an adjustment, so a second transfer of a period adds nothing.
- A period with 0 units has no row in Autotask. A date inside the contract without a row therefore counts as 0.
- If the units cannot be determined, nothing is written and the history says so: for a date before all rows of the service, at the very end of a row, or after the end of the contract.
- A change applies from the day after the period, which has not been billed yet. With
Quantities apply from the start of the periodit applies from the first day of the period; Autotask can refuse that for a period already posted. - An adjustment holds for all later periods. Only the latest closed month can be transferred; the preview offers no other month, and
Send againon an older job ends without a write. - If a write gets no answer, NetLock does not repeat the difference by itself. If Autotask shows the old quantity, the row waits for your check.
Known limits
- Tickets in NetLock show the ticket number, no link.
Related
HaloPSA
Connect NetLock RMM to HaloPSA: alerts become tickets of the mapped client, the all-clear adds a hidden note and sets the closing status, devices can be synced as assets, clients and sites can be imported.
IT Glue
Connect NetLock RMM to IT Glue: devices become configurations of the mapped organization, organizations can be imported as tenants.