Integrations
PSA connects to every product in The One Stack and several third-party platforms. These integrations eliminate duplicate data entry and keep information flowing across your MSP operations.
Stack Integrations
PSA + CRM
| Direction | What syncs |
|---|---|
| CRM → PSA | Client companies, contacts, and deal data sync automatically |
| PSA → CRM | Ticket activity, client health scores, and service data sync back |
| CRM deal closed | Optionally creates a service contract in PSA |
| CRM quote accepted | Can trigger a ticket for onboarding work |
How it works: PSA and CRM share client records through The One Bus event mesh. When a contact is updated in CRM, a contact.updated event fires and PSA picks it up. The sync is near real-time (typically under 5 seconds).
CRM is the primary source of truth for client and contact information.
PSA + Books
| Direction | What syncs |
|---|---|
| PSA → Books | Invoices, payments, and credit notes post as GL journal entries |
| PSA → Books | Revenue reports aggregate across both systems |
| Books → PSA | Chart of accounts available for GL mapping |
Setup: Go to Finance → Books Integration to configure GL account mapping. Map each work type, product, and service to a revenue account in Books.
When an invoice is created in PSA, the corresponding GL entries (accounts receivable debit, revenue credit) post to Books automatically. Payment recordings trigger the cash/AR reconciliation entries.
PSA + Portal
| Feature | How it works |
|---|---|
| Ticket submission | Clients create tickets through Portal; tickets appear in PSA queues |
| Ticket visibility | Clients view their open and resolved tickets in Portal |
| Replies | Client replies in Portal appear as comments on the PSA ticket |
| Invoices | Clients view and download invoices in Portal |
| Knowledge base | Published KB articles from PSA are accessible in Portal |
| SLA summary | Clients see their SLA compliance stats in Portal |
Setup: Enable Portal access per client at the client record → Portal Access tab. See Client Management for details.
PSA + RMM
| Feature | How it works |
|---|---|
| Alert-to-ticket | RMM device alerts automatically create tickets in PSA with device context |
| Device context | Tickets show the device name, OS, last check-in, and health status |
| Asset linking | Client assets in PSA link to devices managed in RMM |
| Endpoint health | Command Center aggregates RMM device health into client health scores |
How it works: RMM publishes alert.created events to The One Bus. PSA subscribes to these events and creates tickets with the device information pre-populated. The ticket includes a link to the device in RMM for quick remote access.
PSA + Defend
| Feature | How it works |
|---|---|
| Threat-to-ticket | Security detections from Defend create tickets for incident response |
| Threat context | Tickets include detection details, affected device, MITRE ATT&CK mapping |
| Investigation link | Direct link from the ticket to Defend's investigation workspace |
| Escalation | PSA tickets can escalate back to Defend for deeper forensic analysis |
How it works: Defend publishes threat.detected events. PSA creates a P1 or P2 ticket (based on threat severity) in a dedicated Security Incidents queue with full detection context.
PSA + On-Call
| Feature | How it works |
|---|---|
| Ticket-to-alert | P1 tickets created outside business hours trigger On-Call alerts |
| Escalation chain | On-Call routes the alert through the escalation schedule until acknowledged |
| Acknowledgment | When a technician acknowledges the On-Call alert, PSA assigns them to the ticket |
Setup: Configure the On-Call integration at Service Desk → Admin → Escalation Rules. Define which ticket conditions trigger an On-Call alert.
PSA + Projects
| Feature | How it works |
|---|---|
| Ticket linking | Link PSA tickets to Projects milestones and phases |
| Time flow | Time logged on project tickets counts toward project budget tracking |
| Project creation | Create a Projects project directly from a PSA ticket |
See Project Linking for the full workflow.
PSA + Voice
| Feature | How it works |
|---|---|
| Call-to-ticket | Inbound calls through Voice can create tickets with the call recording linked |
| Call logs | Tickets show call history — duration, recording, and caller info |
| Click-to-call | Click a client's phone number in PSA to initiate a Voice call |
| Service desk phone | Integrated phone panel in PSA for taking calls without switching apps |
How it works: Voice publishes call.completed events with caller ID, duration, and recording URL. PSA matches the caller to a client contact and creates or updates a ticket.
Third-Party Integrations
Microsoft 365
PSA integrates with M365 for:
- Entra SSO — single sign-on through Microsoft Entra
- Exchange — email integration for ticket creation (see Email Integration)
- Teams — notifications and ticket updates can be sent to Teams channels via webhook
Configure at Integrations → M365 Config.
Accounting Platforms
| Platform | What it does |
|---|---|
| QuickBooks | Two-way sync of invoices, payments, and chart of accounts |
| Xero | Invoice and payment sync |
| Ramp | Expense tracking sync — Ramp transactions flow to PSA expense management |
Configure at Integrations → QuickBooks / Xero / Ramp.
If you use The One Books as your accounting system, you don't need QuickBooks or Xero integration — Books integration is built in. Third-party accounting integrations are for MSPs using external accounting software.
RMM Platforms (Migration)
For MSPs migrating from other PSA/RMM tools, PSA supports data sync from:
- Autotask — tickets, clients, contacts, time entries, and configuration items
- Datto RMM — device data and alert history
- Domotz — network monitoring data
- ConnectWise ScreenConnect — remote session integration
- ITGlue — documentation and configuration items
These integrations are primarily used during migration. Once you're fully on The One Stack, the native integrations (RMM, Defend, CMDB) replace these.
Pax8 Marketplace
PSA integrates with the Pax8 marketplace for:
- Product catalog sync — Pax8 products available in PSA's product catalog
- Order management — place Pax8 orders from PSA
- License tracking — Pax8 license counts sync to client records
Configure at Integrations → Pax8 Config.
Webhooks
For custom integrations, PSA supports inbound and outbound webhooks:
- Outbound — PSA sends HTTP POST requests when ticket events occur (created, updated, resolved, etc.)
- Inbound — External systems can create or update tickets via PSA's webhook endpoint
Configure webhooks at Admin → Webhooks.
Next Steps
- Email Integration — Detailed email setup guide
- Client Management — CRM sync and Portal access
- Project Linking — PSA-Projects integration details