Skip to main content

CrownSync Service Desk Integration

Native first-party two-way sync with CrownSync's own Service Desk.

CrownSync Service Desk Integration

CrownSync Playbooks integrates natively with CrownSync Service Desk — both products are built and operated by CrownSync, so the integration is first-party: one API key, no middleware, and true two-way synchronisation. If you do not run a separate ITSM, this is the fastest way to give incidents a full ticketing lifecycle.

What Syncs

  • Incident declared — a CS-n ticket is raised in the Service Desk, pre-routed to the Playbooks support queue, with severity mapped to ticket impact and urgency.
  • Status changes (both directions)— resolving or closing an incident resolves and closes its ticket through the desk’s own workflow (SLA clocks, resolution email and audit trail all behave as if an agent worked it); a support agent resolving or closing the ticket updates the incident the same way.
  • Severity and priority (both directions)— incident severity changes re-derive the ticket’s priority; an agent’s priority override flows back to incident severity.
  • Major incidents (both directions) — a critical incident flags the ticket as a major incident in the desk; an agent declaring a major incident marks the linked incident critical.

Information

Closed tickets are immutable in the Service Desk by design. If an incident is reopened after its ticket was closed, Playbooks raises a fresh linked ticket automatically — mirroring the desk’s own reply-after-close behaviour — and continues syncing against it.

Prerequisites

  • A CrownSync Service Desk API key (cssd_…) — issued by the CrownSync support team; contact [email protected] if you do not have one
  • Your organisation’s support contact email address
  • Admin role in CrownSync Playbooks

Connection Setup

  1. Go to Admin → Integrations → Service Desk Integration and choose CrownSync Service Desk.
  2. Paste your API key and enter the requester email — tickets raised by the integration are opened under this address, and it receives the CS-n acknowledgement emails.
  3. Click Test Connection, review the default severity and status mappings, and choose Two-way sync.
  4. Activate. The inbound webhook is registered with the Service Desk automatically — there is nothing to configure on the desk side.

How It Works

Outbound changes call the Service Desk ticket API directly; inbound changes arrive on a webhook the integration registers at activation (and removes if you pause or disconnect). Every sync action is recorded in the integration’s Recent Sync Activity log, and on the desk side each API-driven change is audited and noted on the ticket timeline with the integration’s name.

Tip

Replies work through the ticket itself: the requester answers the CS-n acknowledgement email and the conversation threads onto the ticket — no extra configuration needed.

Was this page helpful?