Configure PSA - Datto AutoTask

Configure Datto (AutoTask) PSA to import organizations, automatically create tickets, and more



  1. Ensure you have all needed API Credentials
  2. Go to the Integrations tab on the nav menu (far left side of screendashboard-shot-png.png
  3. Input the API username and secret you saved in step 1
  4. Click Create Integration
  5. If there is a problem with your credentials, you will receive an error message as a popup.  If you have verified that all information is collected/entered correctly, submit a support ticket.
  6. Select a queue from the dropdown and click Update Autotask Integration.  New security tickets from RocketCyber will appear in the selected queue.
  7. If the update is successful, the status lists (New, Updated, Closed) will populate with a list of possible statuses for the selected board.  You must select a status to assign to tickets in each situation (new tickets, tickets to be closed, etc.) under the New and Closed dropdowns.  You may select a status for Updated if you wish.  Once you have made your selections, click Update Autotask Integration.
  8. Autotask cannot create a service ticket unless it is associated with a specific company.  Select the Autotask-RocketCyber Organization Map button
  9. You will have a list of company types from your AutoTask PSA.  Please select only the needed organization types and check Create Organizations then click Pull Companies. 
  10. This will import a list of companies to choose which organizations to pull into RocketCyber. Check which organizations to add then ">" to add to Selected Companies list, select all then click Create Companies. It is not necessary to select companies that were added manually into RocketCyber, this will create a duplicate. blobid0.png
  11. Once completed then click on the Autotask Mapping to see the list of organizations, for organizations entered manually in RocketCyber the mapping will be blank and will need to be selected in the drop down menu.  blobid1.png
  12. Once the organizations are mapped you can configure the 'Status for Closed Tickets' to enable two-way ticket sync. By default the field is set to "Complete", so any RocketCyber incident tickets marked as 'Complete' in AutoTask will automatically resolve the corresponding incident in RocketCyber. You can customize this field to use a different status if you'd like.

Default Due Date Settings

Autotask sets a default value for Due Date and Due Time for the "Standard" ticket category. RocketCyber relies on these default values for automated ticket creation. If your PSA tickets are not being generated please verify that the default offsets for Due Date and Due Time are configured properly. If the setting for this values indicate No Default (user entry required) the tickets will fail to be generated as this is a required field.

To verify and configure these settings perform the following steps.


  1. Logon to the Datto (AutoTask) PSA


2. From the main navigation menu click Admin/Features & Settings


3. Click on Service Desk/Ticket Categories


4. Click on the context menu bar to the left of the Standard category the, click Edit


5. Click on Details and scroll down to Section & Fields


6. On the context menu to the left of Due Date, click Edit Field


7. Click the Pencil icon to edit the values.


8. In the Configure Default Value dialog, set an expected Due Date and Due Time for the values. In this example, we set the default Due Date to 0 days from ticket creation and Due Time within 8 hours of ticket creation. Please adjust these values as needed for your organization. You must set a default value for both Due Date and Due Time.

When finished modifying the values click OK


9. Click OK in the highlighted row.


10. Very important to click Save & Close on the Edit Ticket Category view. Changes will be lost if this is not clicked.

You're done!  Any security tickets will automatically be populated in your Autotask PSA!  If you wish to also receive email notifications, follow these instructions.



Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section