Skip to main content
This guide walks you through connecting your Autotask PSA instance to MSPortal.ai using our streamlined setup wizard.

​
Prerequisites

  • Admin access to Autotask, or API credentials (username and secret)
  • Admin access to MSPortal.ai with integration management permissions

​
Part 1: Configure Autotask PSA

Before connecting to MSPortal.ai, you need to create an API user and security role in Autotask.

​
Create Security Role

1

Access Security Settings

  1. Navigate to Autotask
  2. Go to the Admin area
  3. Click Account Settings & Users
  4. Click Security Levels
2

Create MSPortal Security Role

  1. Copy the default API User (system) role
  2. Rename it to MSPortal
  3. Scroll down to Other and enable:
    • Can create webhooks: Yes
    • Set webhook limit to 25
We recommend setting unused areas to “No permissions” or “Read only” to follow the principle of least privilege. However, this may cause synchronization issues if you later enable those features.
3

Save the Role

Click Save & Close to finalize the security role settings.

​
Create API User

1

Navigate to Users

  1. Go back to Account Settings & Users
  2. Select Resources/Users
  3. Click to add a new API user
2

Configure API User

Fill in the following details:
3

Generate API Credentials

  1. Under Credentials, click Generate Key
  2. Click Generate Secret
  3. Important: Save the API username and secret immediately - the secret cannot be retrieved later
Make sure to copy and save your API credentials before closing this dialog. The secret cannot be viewed again after creation.
4

Associate Lines of Business

Associate the appropriate lines of business with the API user, then click Save & Close.

​
Part 2: MSPortal Setup Wizard

MSPortal.ai provides a guided setup wizard that walks you through connecting and configuring your Autotask integration in 5 easy steps.

​
Starting the Wizard

1

Navigate to Integrations

In MSPortal.ai, go to Settings > Integrations.
2

Start Setup

Find the Autotask PSA integration card and click Setup (or Configure if previously connected) to launch the setup wizard.

​
Step 1: Connect

Enter your Autotask API credentials to establish the connection.
1

Enter API Credentials

Fill in the following fields:
2

Test Connection

Click Test Connection to verify your credentials. You’ll see a green “Connected” status when successful.
If the connection fails, verify your API username and secret are correct and that the API user has the MSPortal security role assigned.
3

Proceed

Once connected, click Next to continue to the permission check.

​
Step 2: Permissions

MSPortal checks what your Autotask API user is allowed to read, and shows the result for each area of data.
1

Review the results

The check runs automatically when you reach this step. Each area of data is listed as either granted or unavailable.Areas marked Required must be granted before you can continue: Companies, Contacts and staff, Tickets, and Boards and statuses (the ticket picklists). Without these the integration cannot function.Optional areas cover Configurations, Opportunities, Product catalog, Invoices, Contracts, Projects, Time entries, Service calls, and Company notes.
2

Grant anything missing

Any area that is not permitted shows the exact security level setting to change, for example Security Level -> Contracts -> Products & Services: View.Update the security level assigned to your API user in Admin > Resources/Users > Security Levels, then come back and click Re-check.
3

Continue

You can continue with optional areas ungranted. Those syncs stay switched off and their toggles are locked on the next step until you grant the permission and re-check.
If a permission is removed later, MSPortal switches off the affected sync and notifies your integration admins rather than retrying against an entity it can no longer read.

​
Step 3: Sync

Configure what data to sync from Autotask and set up automatic contact import.
1

Configure Data Sync Options

Enable or disable the following sync options:
2

Configure Contact Auto-Import

If you want contacts to be automatically imported when companies are added:
  1. Enable Auto-Import to automatically create user accounts for active contacts
  2. Select a Default Role for Imported Contacts (e.g., Viewer)
We recommend choosing a role with minimal permissions (basic ticket creation only) if you plan to import all contacts.
3

Configure Ticket Sync Scope

Define which tickets to sync:
When you proceed to the next step, data sync will begin in the background. This may take a few minutes depending on the amount of data in your Autotask account.Syncs are automatically deduplicated - if you navigate back and forth between steps, the same sync will not run multiple times within a 2-minute window.
4

Proceed

Click Next to continue to ticket and opportunity configuration.

​
Step 4: Configure

Set up ticket status mapping and opportunity defaults.

​
Ticket Settings

1

Configure Status Settings

2

Configure Resolution Status Stepper

The Resolution Status Stepper provides a visual indicator of ticket progress. Map your Autotask statuses to each stage:
You can map multiple Autotask statuses to each stage. The stepper will show the appropriate stage based on the ticket’s current status.
3

Sync Actions

Use these buttons to manage ticket sync:

​
Opportunity Settings

1

Configure Opportunity Defaults

Set default values for opportunities created from MSPortal:
Opportunity sync can be enabled or disabled in the Sync step. These settings only apply when opportunity sync is enabled.
2

Proceed

Click Next to continue to the import step.

​
Step 5: Import (Optional)

Import users and companies from Autotask. This step is optional - you can skip it and import later from the respective settings pages. The step is organized into Users, Companies, and Configuration Items tabs.
Import resources (your MSP staff) from Autotask to create user accounts.
  1. Select users from the list to create accounts for
  2. Choose a role for imported users
Client contacts are not imported here. They can be managed via Company settings after companies are imported.

​
Complete Setup

Click Complete Setup to finish the wizard. Your Autotask integration is now configured!
You can return to the setup wizard at any time by clicking Configure on the Autotask integration card. The wizard will resume with your current settings.

​
Managing Your Integration

After setup, you can manage your integration from Settings > Integrations:
  • Configure: Re-open the setup wizard to modify settings
  • Resync: Trigger a manual sync of data
  • Sync PSA Data: Refresh configuration data (boards, statuses, types) from Autotask

​
Webhook Management

MSPortal automatically provisions webhooks in Autotask when the integration connects, so ticket and company changes sync instantly. No manual webhook setup is required. If webhooks stop working, verify that your API user’s security role still allows creating webhooks, then re-run the Connect step of the setup wizard.

​
Additional Configuration

After completing the wizard, you may want to configure additional settings:

​
Configure Ticket Settings

Navigate to Settings > Tickets to:
  1. Set the Delivery Method to PSA
  2. Ensure Autotask is selected as your PSA provider
  3. Configure ticket categories and map them to Autotask ticket types
  4. Set Ticket Defaults for tickets created from compliance tasks or automation
Ticket defaults are also used as the starting point for new ticket templates, making template creation faster.

​
Configure Display Groups

Display groups control which ticket fields users can see based on their role.
  1. Navigate to Settings > Tickets
  2. Scroll to Display Groups and click Create Group
  3. Configure:
    • Name for the display group
    • Select Autotask as the PSA provider
    • Assign roles that should use this display group
    • Select which fields are visible
Only grant access to information users need for their role. Follow the principle of least privilege.

​
Configure Allowed Statuses

Set which ticket statuses users can select when updating tickets:
  1. Navigate to Settings > Tickets
  2. Configure status permissions for each display group
We recommend preventing users from closing tickets directly. Instead, use a “Ready for Review” status to ensure tickets are reviewed before closure.

​
Troubleshooting