On this page
MSPortal PSA integrations at a glance
| ConnectWise Manage | HaloPSA | Autotask | Syncro | |
|---|---|---|---|---|
| Create tickets, add notes, change status | Yes | Yes | Yes | Yes |
| Ticket attachments | Yes | Yes | Yes | No |
| How ticket changes arrive | Webhook, plus a scheduled sync | Webhooks once set up, or scheduled sync | Webhooks once set up, or scheduled sync | Scheduled sync |
| Projects and project tickets | Yes | Yes | Yes | No |
| Invoices | Yes | Yes | Yes | No |
| Agreements or contracts | Yes | Yes | Yes | No |
| Products and opportunities | Yes | Yes | Yes | No |
| Devices or configurations | Configurations | Assets | Configuration items | Devices and assets |
ConnectWise Manage is supported in both cloud and on-premises editions. HaloPSA can also bring in native CSAT results, and Autotask its satisfaction survey results, when those datasets are turned on. Each integration has its own page with setup details: ConnectWise Manage, HaloPSA and Autotask. The full catalog is on the integrations page.
What MSPortal writes back to the PSA
MSPortal keeps your PSA as the system of record. These actions are written to it:
- New tickets. A ticket created in the portal is created in the PSA. Ticket templates set the PSA defaults, such as board or queue, type, status and priority, so routing follows your rules.
- Notes and status. Ticket notes and status changes made in the portal go to the PSA. Private notes written by MSP staff in MSPortal stay in MSPortal and are never sent to the PSA.
- Project changes. For ConnectWise, HaloPSA and Autotask projects, status, schedule dates and assignees write back. Milestones, updates, decisions and deliverables stay in MSPortal.
- Warranty dates. Optional warranty writeback can update ConnectWise configurations, HaloPSA assets or Autotask configuration items when MSPortal resolves a device's warranty.
MSPortal's MCP server uses the same path, so a note or status change made by a connected AI client, after you confirm it, also lands in the PSA. Write actions need write permissions on the PSA's API account. The permission check in MSPortal tests read access only, so test a write on a sample ticket before rollout.
How often PSA data updates in MSPortal
PSA data is automatically updated rather than live, unless webhooks deliver it. ConnectWise ticket updates arrive by webhook, and Autotask and HaloPSA can use webhooks once they are set up. Otherwise, these are the published target intervals for tickets:
| PSA | Ticket sync interval |
|---|---|
| Syncro | Every 5 minutes |
| Autotask | Every 10 minutes |
| ConnectWise Manage | Every 15 minutes |
| HaloPSA | Every 15 minutes |
Other data refreshes less often. For example, ConnectWise invoices and projects sync every two hours, and statuses, priorities and boards sync daily. The sync schedule documentation lists every dataset. Intervals are how often work is scheduled, not a guaranteed maximum delay, and staff can request a manual sync from the integration's page.
What clients see from the PSA
Clients never log in to the PSA. Through MSPortal they see the tickets their role allows, with status, the assigned technician and public notes, and they can reply if their role permits. Internal notes stay hidden. Where invoice and project sync are on, clients can also see the invoices and projects you choose to share. See how clients see the status of their IT tickets and the ticketing feature page.
Setting up a PSA connection
Setup follows the same steps for each PSA:
- Create a dedicated API account in the PSA with the permissions listed in the guide.
- Connect it in Settings > Integrations and run the permission check.
- Choose which data to sync, such as tickets, projects or invoices, and the ticket scope.
- Import or match client companies and users, then verify what clients can see.
MSPortal asks you to confirm before it auto-imports a new batch of companies, because companies are billed. Setup guides for each PSA, such as the Syncro guide, are on docs.msportal.ai.
NinjaOne Ticketing is a pilot that currently validates the API connection only and does not import tickets yet; the integrations page lists it as coming soon. If your PSA is not listed, tell us what you use.
Related questions
Does MSPortal replace my PSA?
No. MSPortal keeps the PSA as the system of record for tickets, time and billing. It gives clients a branded portal on top of it and writes tickets, notes and status changes back to the PSA.
Does MSPortal sync tickets with the PSA in real time?
ConnectWise ticket updates arrive by webhook, and Autotask and HaloPSA can use webhooks once set up. Otherwise MSPortal syncs tickets on a schedule of about 5 to 15 minutes, depending on the PSA.
Can clients attach files to Syncro tickets in MSPortal?
No. Syncro notes cannot carry attachments through MSPortal. Attachments work with ConnectWise Manage, HaloPSA and Autotask.
Can I use MSPortal projects without a PSA?
Yes. With PSA project sync turned off, projects live only in MSPortal. See how MSPs share project progress with clients.
Is the PSA integration included in the price?
Yes. PSA and RMM sync are included in every MSPortal plan. See how much MSPortal costs.