What HaloPSA data does Scopable sync?

Scopable syncs clients, sites, contacts, products, assets, opportunities, and contracts. Clients are the required foundation. The other record types can be selected during setup.

Does Scopable write data back to HaloPSA?

No. The current HaloPSA integration is read-only. It pulls PSA context into Scopable so quoting, QBR, assessment, and roadmap work can start from current records.

Can HaloPSA and ConnectWise run at the same time?

No. Scopable connects to one PSA at a time. If ConnectWise Manage is active, HaloPSA activation is blocked until ConnectWise is disconnected.

Why do some accounts not see the HaloPSA tab?

HaloPSA is in gradual rollout. If the tab is not visible or the app says the integration is not available for your account, access has not been enabled yet.

Are HaloPSA webhooks required?

No. Webhooks are optional. Without webhooks, data still syncs on schedule. With webhooks, HaloPSA can also send real-time update events to Scopable.

Alpha PSA integration

HaloPSA integration for MSP quoting.

Scopable connects to HaloPSA so client, site, contact, product, asset, opportunity, and contract context can support quoting, QBR, assessment, and roadmap work.

Built for HaloPSA shops that need to know what Scopable reads, what it does not write, and whether the rollout fits their current PSA setup before they commit time to testing.

Start free trial See pricing

Exact supported scope

What the HaloPSA integration actually does.

This is the buyer-facing view of the HaloPSA connection. The setup guide remains the source for API application steps, credentials, webhooks, and troubleshooting.

Records Scopable reads

Clients, sites, contacts, products, assets, opportunities, and contracts from HaloPSA. Clients are always on because the other records depend on them.

Read-only PSA sync

The current version pulls data from HaloPSA into Scopable. No HaloPSA write-back is enabled.

Credential handling

Scopable stores the HaloPSA client secret in its secure vault after the setup wizard tests the connection.

Sync behavior

Admins choose record types, can limit to active clients, can configure webhooks, and then start the initial sync.

Product state checked 2026-07-22. Knowledge Base source last updated 2026-06-22. Anything broader should be treated as unverified until it appears in the setup guide or product release notes.

Data-flow proof

From HaloPSA records to quote-ready context.

The flow below uses the public setup guide and app setup wizard as its source. It shows the data movement without staging a fake tenant or customer screen.

Step 1

Create API access

Create a HaloPSA API-only agent and client-credentials application with the permissions your sync needs.

Step 2

Test the connection

Enter the base URL, auth server when needed, tenant name when hosted, client ID, and client secret.

Step 3

Choose sync scope

Keep clients on, choose the optional record types, and decide whether active clients only is the right boundary.

Step 4

Add webhooks if useful

Copy the webhook URL into HaloPSA if real-time update events matter. Otherwise skip this step.

Step 5

Start the first sync

Review the configuration, save it, and let Scopable begin pulling HaloPSA records into the account.

Limits

This is not a HaloPSA replacement.

HaloPSA is in gradual rollout. Some accounts will not see the tab until it is enabled.

Scopable can connect to one PSA at a time. HaloPSA activation is blocked while ConnectWise Manage is active.

The current HaloPSA integration is read-only. Do not assume quote or opportunity write-back to HaloPSA.

On-premises HaloPSA must be reachable from the internet with valid SSL certificates for Scopable to connect.

The Halo Ticket Namer is a separate optional utility. It is not the full PSA sync described on this page.

Security review

What the technical validator should check.

The HaloPSA path is straightforward, but it still touches customer records. Treat the API app, token host, and webhook setup like production infrastructure.

Use a dedicated HaloPSA API-only agent where possible.
Grant only the permissions the selected sync paths require.
Confirm the Resource Server, Auth Server, and Tenant values before testing.
Keep the client secret out of tickets, docs, chats, and screenshots.
Review sync logs after the first run before quoting from the data.

Buying path

Keep the commercial page and setup guide connected.

Use this page to decide whether the integration fits the MSP workflow. Use the Knowledge Base when the admin is ready to configure HaloPSA.

HaloPSA setup guide

Use this for API application steps, sync selections, optional webhooks, and troubleshooting.

Read the setup guide

Integrations hub

Use this when the buyer needs to understand the whole PSA, Microsoft, catalog, and documentation map.

See all integrations

vCIO software

Use this when HaloPSA data needs to support QBR prep, roadmap decisions, and follow-up work.

See the vCIO workflow

MSP quoting software

Use this when the decision is whether PSA context can make quotes easier to inspect and defend.

See the quote workflow

HaloPSA questions

Test HaloPSA with one real client.

The trial should prove whether HaloPSA records make scope, QBR preparation, roadmap decisions, and quote follow-up easier to trust.

Start free trial See pricing