Skip to main content
Back to the connector catalogue

Connector

Atera

Outbound ticketing integration: Vigicap files tickets into it.

Your actions go into Atera 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 Atera, not in Vigicap.

Where to generate it

Atera → Admin → API: generate your API key. The client ID comes from the customer record (Customer ID).

Minimum role

Clé d'API Atera. ÉCRITURE : la clé Atera n'est pas cloisonnable en lecture seule — elle porte les droits du compte qui l'a créée. LECTURE : la même clé relit le ticket ; aucune portée distincte n'existe, ce qui est précisément pourquoi la phrase précédente est écrite telle quelle.

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

02

What to enter in Vigicap

  • API 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.

  • Contact ID (EndUserID)

    Atera contact ID (End User) tickets are attached to — the client is inferred from it.

    e.g. 12

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 was written from the vendor's documented API and has not yet been run against a real instance.