Skip to main content
Back to the connector catalogue

Connector

ConnectWise Manage

Outbound ticketing integration: Vigicap files tickets into it.

Your actions go into ConnectWise Manage as tickets, with their title and description: the action plan stops being a list to re-key into the tool your technicians already work in. No ReCyF level is proposed. Pushing a ticket does not measure a client's posture.

01

What to create in the tool

The access is created in ConnectWise Manage, not in Vigicap.

Where to generate it

ConnectWise → System → Members → API Members: create an API member (public + private keys). The site URL is the bare host — https://your-instance.connectwise.net — without the version path your browser shows. The integration clientId is Vigicap's own: there is nothing for you to fetch from developer.connectwise.com.

Minimum role

Membre d'API ConnectWise (clés publique + privée). ÉCRITURE : droit de création sur le board de tickets visé. LECTURE : droit de lecture sur ce même board (Service Desk → Service Tickets), pour relire le statut d'un ticket déjà créé.

Taken from the vendor's own role model, and checked before publication.

02

What to enter in Vigicap

  • Company identifier
  • Public key
  • Private keysecret

03

Per-client routing

These fields are filled in client by client: they say which account in the ticketing tool the ticket must land under. A wrong value does not fail the push — it succeeds against someone else, which is why Vigicap checks them the moment you type them.

  • Service board ID

    ConnectWise board the ticket is created on. That board must have a default status and a default team, or ConnectWise refuses to create the ticket.

    e.g. 1

  • Client company ID

    ID of the client's company in ConnectWise.

    e.g. 250

04

What it does, and what it does not do

ReCyF objectives it pre-fills

This connector feeds no ReCyF objective, and that is not a gap: it does not measure a client's posture.

What goes out to the tool

This connector WRITES: it creates a ticket from an action in the plan.

What comes back

The state of an already-created ticket comes back: its status, its closing date, its last activity. A closed ticket becomes a PROPOSAL a consultant confirms — never an action closed of its own accord. An agency that closes its own ticket must not be able to mark its own homework in the document an auditor reads.

How Vigicap handles your credentials.

Verification

This connector has been run end to end against a real instance of the tool, not merely tested against a mock.

What this connector does, exactly

  • It writes. Your actions go into ConnectWise Manage as tickets, with their title and their description.
  • It then reads those tickets' state back, so the action plan stops being a list to retype into the tool your technicians already work in.

What it does not read

A client's security posture. It is the only connector in this list that measures nothing: filing a ticket does not measure posture. No ReCyF level is proposed, and none will be from this source.

What these signals do not prove

  • A ticket created proves an action was transmitted. It proves neither that it was done nor that it had the intended effect — reading the state back gives the first half of that answer, and a connector reading would give the second.
  • Three credentials are enough to write into your PSA: companyId, publicKey and privateKey. Treat them as write access, because that is what they are.
Can it be used read-only?
No. This connector exists to write tickets; it has no posture-reading mode.
What happens if a ticket is closed on the ConnectWise side?
The state read back changes. That is the only feedback the integration takes from your PSA.