Setup at a glance
- Create an API member in ConnectWise
- Connect ConnectWise in Telivy
- Choose which findings open tickets
- Map each company and turn on sync
Prerequisites
- A ConnectWise PSA (Manage) instance and a ConnectWise account that can create API members and Security Roles.
- 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.
Step 1: Create an API member in ConnectWise
Give the API member a Security Role
Create the API member and its keys
Note your company ID and URL
mycompany.connectwiseapps.com.Step 2: Connect ConnectWise in Telivy
Pick ConnectWise as your platform

Enter the API member keys
https://), Public Key and Private Key. Click Test Connection to check the keys and permissions without saving, then click Connect & Enable. The 2. Settings tab stays unavailable until the connection succeeds.
Choose the ticket settings
- Resolved Status: used when a finding is resolved or a compensating control is recorded.
- Accepted Risk Status: used when someone accepts the risk on a finding.

Step 3: 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 ConnectWise 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.
Step 4: Map each company and turn on sync
Open the mapping dialog
Pick the ConnectWise company

Turn on PSA sync for the assessment

How the integration works
Tickets
Once ConnectWise is connected and a company is mapped, each finding in a category you chose to sync opens one service ticket. When a scan raises a finding in a category you chose to sync, Telivy creates a service ticket on the board you picked, against the ConnectWise company mapped to that client. The summary starts with[Telivy], the severity and the finding name, for example [Telivy][HIGH] <finding name>, and is cut to ConnectWise’s 100-character limit. The ticket body 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 reads your instance’s own priority list, so customized priority tables work. Critical and High findings get your highest priority, Low and Info get the lowest, and Medium gets your default priority.Resolutions read back from ConnectWise
Every hour Telivy checks the tickets it opened. A ticket that is closed, or that sits in a status the board marks as closed or as the Resolved escalation step, marks the finding Resolved in PSA in Telivy, with the ticket number and status in the reason. If the issue is still there, the next scan raises the finding again.Merged tickets
If a technician merges a Telivy ticket into another ticket, Telivy writes later updates to the ticket it was merged into instead of failing on the closed original.One PSA at a time
An agency connects one PSA. While Autotask or HaloPSA is enabled, the ConnectWise switch is disabled and Telivy shows Disable Autotask to connect ConnectWise (or HaloPSA). Disconnecting a PSA keeps its credentials, ticket settings and company mappings, so you can switch back later.
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 ConnectWise. Find unsynced in ConnectWise lists the assessment’s findings that should have a ticket but do not, and queues them. The ConnectWise card on the assessment’s Setup → 4. Integrations step has Check ConnectWise for updates, which runs the hourly read-back straight away for that assessment. The same card has Unmap, which stops new tickets for that company. Tickets already in ConnectWise stay as they are, and findings that were synced before do not sync again if you map the company somewhere else. Disconnect in the ConnectWise dialog stops Telivy opening and updating tickets for the whole agency. Credentials, ticket settings and mappings are kept. Deleting a company in Telivy releases its ConnectWise mapping, so the ConnectWise company can be mapped to another client.Check that it works
- Account → Integrations → PSA shows ConnectWise as Connected.
- The PSA column on Companies shows the ConnectWise company name.
- New tickets appear on your chosen board with summaries starting with
[Telivy]. - When a technician closes one of those tickets, the finding shows Resolved in PSA within the hour, or straight away after Check ConnectWise for updates.
Troubleshooting
Test Connection says a permission is missing
Test Connection says a permission is missing
Test Connection fails with an authentication error
Test Connection fails with an authentication error
https:// prefix, and that the public and private keys were copied without extra spaces from the same API key.The ConnectWise switch is greyed out
The ConnectWise switch is greyed out
Findings are not creating tickets
Findings are not creating tickets
Closed tickets are not resolving findings in Telivy
Closed tickets are not resolving findings in Telivy