bitlync Docs

Coverage

Coverage.

What exists on each connector today.

ConnectWiseHaloPSASuperOpsNinjaOneScalePadPax8Hudu
TicketRead and WriteRead and WriteRead and Write————
Billing line itemRead and WriteRead and Write—————
ProjectRead and WriteRead and Write—————
AgreementReadReadRead————
CompanyReadReadRead——Read and WriteRead
Company custom fieldsWrite (live; field created once in your stack; grant off by default)Write (live; field created once in your stack; grant off by default)—————
ContactList and matchList and match—————
MemberListList—————
TimeWriteWrite—————
Boards, statuses, prioritiesListList—————
Device———Read———
Software———Read———
Action item————Read and Write——
Initiative————Read and Write——
Product—————Read—
Subscription—————Read—
Invoice—————Read—
Order—————Write—
Document——————Read and Write
Configuration———————
Asset——————Read

Read = from the PSA into Bitlync. Write = to the PSA. List = list-only.

SuperOps is one connection for PSA and RMM. The sandbox offers tickets (read and write), companies (read), and agreements (read). It has no custom-field value writes, no agreement-line writes, and no draft contracts. Contacts, projects, members, time, board lists, devices, and software are not offered. There is no coverage manifest, so those cells stay unsupported.

First connect: Halo and ConnectWise. Halo and ConnectWise company custom fields: POST /tenants/{tenant_id}/companies/write writes a value on an existing company with vendor_native, and ensure_custom_field creates the missing field definition. The field works live on Halo and ConnectWise. It is created once in your stack under the MSP's standing psa.company.field.create grant, and an existing field with the same label is reused. The field label shows on Configure. Value writes use the psa.company.update grant, off by default.