ServiceNow Integration
Step-by-step guide for connecting ServiceNow.
ServiceNow Integration
The ServiceNow integration connects CrownSync Playbooks to your ServiceNow ITSM instance, enabling bi-directional synchronisation of incident data. When an incident is created or updated in CrownSync, it is automatically reflected in ServiceNow, and vice versa.
Prerequisites
- A ServiceNow instance (any supported version)
- A ServiceNow user account with API access and the
itilrole - Admin role in CrownSync Playbooks
- Network connectivity between ServiceNow and the CrownSync API endpoint
Connection Setup
Open Integration Settings
Navigate to Admin → Integrations and select ServiceNow from the available integrations.
Enter Connection Details
Enter your ServiceNow instance URL (e.g. https://yourcompany.service-now.com). Choose your authentication method:
- Basic Authentication — Enter a ServiceNow username and password
- OAuth 2.0 — Enter a Client ID and Client Secret from a ServiceNow OAuth application

Test and Save
Click Test Connection to verify the credentials, then click Save.
Use a Dedicated Service Account
Create a dedicated ServiceNow service account for the CrownSync integration rather than using a personal account. This ensures the integration continues to work when team members leave and makes audit trail attribution clearer.
Sync Direction
You can configure the sync direction to suit your workflow:
- Outbound only— CrownSync pushes incident data to ServiceNow. Updates in ServiceNow are not reflected back.
- Bi-directional— Changes in either system are synchronised to the other. Requires a webhook configured in ServiceNow (see below).
Severity Mapping
CrownSync incident severity levels map to ServiceNow's Impact and Urgency fields as follows by default:
| ServiceNow Priority | CrownSync Severity |
|---|---|
| 1 - Critical | Critical |
| 2 - High | High |
| 3 - Moderate | Medium |
| 4 - Low | Low |
You can customise these mappings from the integration settings page to match your organisation's ServiceNow configuration.
Category Mapping
CrownSync incident categories (e.g. Ransomware, Business Email Compromise, Data Breach) are mapped to ServiceNow categories. You can configure the target category and subcategory for each CrownSync incident type in the integration settings.
Inbound Webhook Setup (ServiceNow → CrownSync)
For bi-directional sync, configure a Business Rule in ServiceNow to send updates back to CrownSync:
- In ServiceNow, navigate to System Definition → Business Rules
- Create a new Business Rule on the
incidenttable - Set it to run on update operations
- In the Advanced script, add an HTTP POST to the CrownSync webhook URL displayed in your integration settings
- Include your CrownSync API key in the request headers
- Test by updating an incident in ServiceNow and confirming it appears in CrownSync
Testing the Integration
After setup, verify the integration by:
- Creating a test incident in CrownSync Playbooks
- Confirming it appears in ServiceNow with the correct fields
- Updating the incident in ServiceNow (if using bi-directional sync)
- Confirming the update is reflected in CrownSync
Troubleshooting
- Connection refused— Verify the instance URL is correct and accessible from the internet
- Authentication failed— Check the credentials and ensure the user has the
itilrole - Incidents not syncing— Check the sync direction setting and verify the webhook is configured correctly
- Field mapping errors— Review the severity and category mappings to ensure they match valid ServiceNow values
Information
All integration activity is logged in the audit log, including successful syncs, failed attempts, and configuration changes.
Integration instructions last verified: April 2026
Was this page helpful?