Skip to main content
The Autotask integration opens a Datto Autotask PSA ticket for each security finding Telivy raises for a mapped client. When a technician completes the ticket, Telivy marks the finding as resolved. When you resolve or accept a finding in Telivy, Telivy can move its ticket to a status you choose. Setting it up needs someone with admin access to Autotask and access to Account → Integrations → PSA in Telivy.

Setup at a glance

  1. Activate Telivy in the Autotask Integration Center
  2. Create a security level for the API user
  3. Create the API user
  4. Connect Autotask in Telivy
  5. Choose which findings open tickets
  6. Map each company and turn on sync
The Prerequisites and each step are below. How the integration works, after the steps, explains what happens to tickets once sync is on.

Prerequisites

  • A Datto Autotask PSA subscription and an Autotask account with admin access.
  • A Telivy account with access to Account → Integrations → PSA.
  • No other PSA connected in Telivy. An agency connects one PSA at a time, see One PSA at a time.
Some terms below are Autotask defaults. If your instance uses different names, see Datto’s Local Terms and Symbols help page.

Step 1: Activate Telivy in the Autotask Integration Center

1

Open the Integration Center

In Autotask, go to Admin → Extensions & Integrations → Other Extensions & Tools → Integration Center.
2

Edit the Telivy entry

Search for Telivy - Security/Risk Monitoring, right-click it and choose Edit.
3

Turn it on

Under General, select Active. Under Integration Vendor Widgets, select Enable Integration Vendor Widgets. Under Vendor Insights, select both Enable Integration Vendor Ticket Insights and Enable Integration Vendor Configuration Item Insights. Save.

Step 2: Create a security level for the API user

1

Copy an API security level

Go to Admin → Company Settings & Users → Security Level. Right-click a security level with the API User licence type and choose Copy.
2

Name it and clear every permission

Name the copy, for example Telivy API Integration. Set every permission on every tab to No Permission.
3

Grant only what Telivy needs

Then turn on these permissions:Click Save and Close.

Step 3: Create the API user

1

Add a new API user

Go to Admin → Company Settings & Users → Resources/Users (HR), open the New dropdown and choose New API User.
2

Assign the security level and generate credentials

Fill in the required fields and select the security level from Step 2. Click Generate to create the Key (username) and Secret. Copy both now.
3

Set the tracking identifier

Under API Tracking Identifier, select Telivy - Security/Risk Monitoring as the vendor. Click Save & Close.

Step 4: Connect Autotask in Telivy

1

Pick Autotask as your platform

In Telivy, go to Account → Integrations → PSA and choose Autotask in the Platform picker, then turn on the Enable switch. The Autotask dialog opens on its 1. Connect tab.
2

Enter the API user credentials

Enter the API user’s key as Username and its Secret. Click Test Connection to check them without saving, then Connect & Enable. The 2. Settings tab stays unavailable until the connection succeeds.
Connect tab of the Autotask dialog in Telivy with Username and a masked Secret filled in, and the Test Connection and Connect & Enable buttons
3

Choose the ticket settings

On the 2. Settings tab, New tickets lists the ticket fields your Autotask instance marks as required, such as Queue or Status, read from your own picklists. Pick a default for each, and a Sub Issue Type if your instance requires one.Ticket Source defaults to telivy-task-manager. Add the same name under Admin → Features & Settings → Service Desk → Sources in Autotask if you want workflow rules to act on Telivy tickets.Under Finding decisions:
  • Resolved Status: used when a finding is accepted or resolved. Autotask applies the same status to both.
  • Complete Status: used only when no Resolved Status is set.
Leave both blank to keep tickets as they are. Click Save. To change these later, click Configure on the Autotask card.
Settings tab of the Autotask dialog in Telivy with Queue, Status and Priority under New tickets, Ticket Source set to telivy-task-manager, and Resolved Status and Complete Status under Finding decisions

Step 5: Choose which findings open tickets

Go to Alerts → Policies, click Edit on each policy whose findings should open tickets (or Add Policy), and on its Delivery step turn on the Autotask switch. The policy’s trigger condition, such as Severity Equals High, decides which findings in that category open tickets. These settings apply to whichever PSA is connected. See Alerts for the policy controls. To receive one ticket per scan instead of one per finding, see Grouped PSA tickets. Under Account → Integrations → PSA → Ticket settings, the Close tickets when a finding is accepted or resolved switch controls whether Telivy uses the statuses from Step 4. Without those statuses, tickets are left open.

Step 6: Map each company and turn on sync

1

Open the mapping dialog

In Companies, open the actions menu on a company and choose Map to Autotask. You can also map from the Autotask card on an assessment’s Setup → 4. Integrations step, which is the only place that offers to start syncing right away.
2

Pick the Autotask account

In the Map to an Autotask account dialog, type at least two characters, pick the account, and click Map account. An Autotask account can belong to one Telivy company at a time. Mapping it again moves it to the new company, and the previous company shows Not mapped.
Map to an Autotask account dialog in Telivy with search results for Acme Dentistry and the Start syncing findings to Autotask after mapping box ticked
3

Turn on PSA sync for the assessment

Tick Start syncing findings to Autotask after mapping in the dialog, or turn on Sync findings to PSA on the assessment’s PSA card later. Telivy then opens tickets for the assessment’s existing findings that match your sync policy, and tells you how many it queued.
Autotask card on the assessment Setup Integrations step showing the mapped Autotask account, the Sync findings to PSA switch turned on, Change mapping and Unmap

How the integration works

Tickets

Once Autotask is connected and a company is mapped, each finding in a category you chose to sync opens one ticket. When a scan raises a finding in a category you chose to sync, Telivy creates a ticket against the Autotask account mapped to that client. The title starts with [Telivy], the severity and the finding name. The description covers the finding, the detected value, the risk, the recommended fix and references, and a View in Telivy link that opens the finding directly on the assessment’s Risk tab.

Priority

Telivy matches the finding’s severity to your Autotask priority labels (for example Critical, High, Medium, Low), so a customized priority list works too.

Resolutions read back from Autotask

Every hour Telivy checks the tickets it opened. A ticket that Autotask records as completed, or that sits in a status whose name means closed (such as Complete, Closed or Resolved, but not a waiting or on-hold status), marks the finding Resolved in PSA in Telivy. If the issue is still there, the next scan raises the finding again.

Decisions made in Telivy

When you resolve or accept a finding in Telivy, Telivy moves its ticket to the status you choose in the ticket settings.

One PSA at a time

An agency connects one PSA. While ConnectWise or HaloPSA is enabled, the Autotask switch is disabled and Telivy shows Disable ConnectWise to connect Autotask (or HaloPSA). Disconnecting a PSA keeps its credentials, ticket settings and company mappings, so you can switch back later.
PSA settings in Telivy with Autotask selected, the Enable switch turned off and the note Disable HaloPSA to connect Autotask

Work with tickets from Telivy

Finding tables on the Risk tab have a PSA column. Each dot shows whether the finding is synced, synced but not yet resolved or accepted in Telivy, failed, or not synced. Click a dot to open the existing ticket, or to create one for a finding that has none. To open tickets for many findings at once, select them and click Sync to Autotask. Find unsynced in Autotask lists the assessment’s findings that should have a ticket but do not, and queues them. Unmap on the Autotask card on the assessment’s Setup → 4. Integrations step stops new tickets for that company. Tickets already in Autotask stay as they are, and findings that were synced before do not sync again if you map the company somewhere else. Disconnect in the Autotask dialog stops Telivy opening and updating tickets for the whole agency. Credentials, ticket settings and mappings are kept. Completed tickets are read back on the hourly schedule only. Unlike ConnectWise and HaloPSA, the assessment’s PSA card has no button to run the check on demand for Autotask. Deleting a company in Telivy releases its Autotask mapping, so the Autotask account can be mapped to another client.

Check that it works

  • Account → Integrations → PSA shows Autotask as Connected.
  • The PSA column on Companies shows the Autotask account name.
  • New tickets appear in your chosen queue with titles starting with [Telivy].
  • Within an hour of a technician completing one of those tickets, the finding shows Resolved in PSA in Telivy.

Troubleshooting

Check that the key and secret were copied without extra spaces, that the API user is active, and that its security level includes Can login to Web Services API.
Another PSA is connected. Disable it under Account → Integrations → PSA first. Its settings and mappings are kept.
Check that the company is mapped, that Sync findings to PSA is on for the assessment, and that the finding’s category has PSA sync turned on in Alerts → Policies. If Autotask rejects a ticket, hover the finding’s dot in the PSA column to see the reason, then check the queue, status and other defaults on the 2. Settings tab.
Telivy checks once an hour. A ticket counts as resolved when Autotask records a completed date for it, or when its status name means closed. Statuses named as waiting, pending or on hold are not read back, even if they also contain a word like Complete.