Skip to main content
Back to the connector catalogue

Connector

Datto Autotask PSA

A single agency-level credential, for the whole portfolio.

Your PSA already knows the list of your clients: this connector imports it, then reports for each one the configuration-item inventory, their RMM coverage and warranty status. It proposes no ReCyF level. Autotask does not expose a security measurement that can be reliably interpreted.

Beta

01

What to create in the tool

The access is created in Datto Autotask PSA, not in Vigicap. Vigicap never asks for an administrator's password: it expects an API credential that you create, that you can see, and that you can revoke without us.

Where to generate it

Autotask > Admin > Extensions & Integrations > API User Security : créez un utilisateur « API User (API-only) » et notez son code d'intégration, son identifiant et son secret. Donnez-lui une COPIE PERSONNALISÉE d'un niveau de sécurité API (Autotask en autorise jusqu'à 50) plutôt que le niveau système, qui ouvre l'intégralité des données Autotask, coûts internes compris : dans CRM, « Organization & Contact Access » = All ; dans Object Permissions, « Organizations » et « Devices & Subscriptions » = View uniquement. Vigicap ne lit que ces deux objets. L'URL de zone est trouvée automatiquement à partir de l'identifiant.

Minimum role

Utilisateur de licence « API User (API-only) » portant un niveau de sécurité personnalisé — une copie restreinte, pas le niveau système « API User (system) », qui donne un accès complet à toutes les données Autotask. Dans la catégorie CRM : « Organization & Contact Access » sur « All » (sans quoi aucun client n'est visible), et dans « Object Permissions » les lignes « Organizations » et « Devices & Subscriptions » en « View » seule, Add / Edit / Delete sur « None ».

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

02

What to enter in Vigicap

The exact fields of the connection form, in the order they appear. Values marked “secret” never travel back to the browser: they are encrypted at rest and deleted on disconnection.

The form starts with the instance address, entered separately from the fields below. The public catalogue does not yet publish whether this connector needs one, or what it looks like — so this list is exact about everything else, and silent about that first field.

  • Code d'intégration API
  • Utilisateur API

    L'identifiant de l'utilisateur « API User (API-only) », pas votre compte Autotask.

  • Secret APIsecret

03

Per-client routing

The credential itself is not repeated: one, entered once at agency level, covers the whole portfolio — the difference you feel with forty clients rather than four.

These fields are filled in client by client: they say which PSA account 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.

  • Company ID (companyID)

    Autotask company ID tickets are created under.

    e.g. 0

  • Queue IDoptional
  • Priority IDoptional

    e.g. 2

  • Status IDoptional

    e.g. 1 (New)

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.

Read-only

The reads are read-only: Vigicap writes nothing into the tool while reading it.

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.

What is read, what is kept, for how long and with which rights: the same register, connector by connector, in the data inventory.

Verification

This connector was written from the vendor's documented API and has not yet been run against a real instance. It is marked “Beta” everywhere it appears.

The trademarks and logos mentioned belong to their respective owners and identify the tools Vigicap is compatible with — see the legal notice.