SikurdHelp
Open Sikurd

PSA integration

Auto-create tickets in ConnectWise, Autotask, HaloPSA, or Syncro.

/dashboard/settings/psa is where you connect Sikurd to your PSA so alerts auto-create tickets and resolutions auto-close them. Pro+.

Supported PSAs

  • ConnectWise Manage / Manage cloud.
  • Autotask PSA.
  • HaloPSA.
  • Syncro.

Setting up

Each PSA has its own credential set. Typically you'll need:

  • API URL (e.g. https://api.connectwise.com/v2026.x/apis/3.0/).
  • Company ID / tenant identifier.
  • Public key + private key (ConnectWise), secret + integration code (Autotask), API key (Syncro), or client ID + client secret (HaloPSA).

Credentials are encrypted at rest using AES-256-GCM and only decrypted in-memory when a ticket fires.

Company mappings

After credentials, you map each Sikurd instance to a PSA company:

  1. Settings → PSA → Mappings.
  2. Pick the instance + the matching PSA company from a searchable dropdown.
  3. Save.

Unmapped instances either:

  • Route their alerts to a default fallback company (configure under Settings → PSA → Default mappings), or
  • Skip PSA entirely until mapped.

What flows where

When an alert with PSA routing enabled fires:

  1. Sikurd creates a ticket in the mapped company.
  2. Ticket subject = "[Sikurd] [Alert Type] on [Instance]".
  3. Ticket body = severity, alert details, link back to the Sikurd alert page.
  4. When the alert resolves in Sikurd, the corresponding ticket auto-closes (status changes to "Closed" with a resolution note).

Two-way sync (planned)

Closing the ticket in the PSA → resolves the Sikurd alert is on the roadmap. Today, sync flows one way: Sikurd → PSA.

Testing

Settings → PSA → Test connection verifies the credentials work without firing a real ticket. Simulate alert on any instance fires a real ticket with "(TEST)" in the subject.