# ServiceNow Integration Best Practices

Source: https://userguide.qualytics.io/settings/integrations/ticketing/servicenow/deep-dive/best-practices/

Understand how linked ServiceNow incidents appear in Qualytics, how status syncs work, and make the most of the integration.

## Tickets Section

Once linked, tickets appear in the **Tickets** section of the anomaly.

Each entry shows:

- The **incident number** (e.g., `INC0008111`), a link that opens the incident in ServiceNow in a new tab when Qualytics has the incident's address (otherwise it is plain text).
- The incident's **state** as of the last read from ServiceNow.
- The incident title.
- **Synced X ago**, the time of the last sync in either direction, or **Linked X ago** before the first one.
- A **Two-way** / **Read only** button that sets how this one incident is synced. It is shown while the integration itself is set to two-way sync, and it is visible but not clickable without the **Author** team permission on the anomaly's datastore. Saving the change also needs the **Manager** role.
- An **Unlink ticket**  button that removes the link. It is shown to users with the **Author** team permission on the anomaly's datastore, and to an **Admin**. Unlinking also needs the **Manager** role.

## Syncing Status and Comments

When anomaly status changes in Qualytics:

- Adds a timestamped work note to the linked ServiceNow incident

**Example:** Acknowledging an anomaly in Qualytics:

The status change is reflected in ServiceNow as a work note:

> **Note**
>
> By default status changes add work notes but do **not** change the incident's state. Turn on **Anomaly status sync** in the integration settings to move two-way incidents to the mapped state as well.

> **Tip**
>
> Multiple tickets can be linked to a single anomaly. Use this to track related issues across different teams or instances.

## See Also

- **Permissions**

  The roles, team permissions, and ServiceNow-side permissions each action needs.

  [Permissions](https://userguide.qualytics.io/settings/integrations/ticketing/servicenow/deep-dive/permissions/)
- **How It Works**

  Data flow direction, what gets synced, field mapping, and what the integration can and cannot do.

  [How It Works](https://userguide.qualytics.io/settings/integrations/ticketing/servicenow/deep-dive/how-it-works/)
- **Sync Behavior**

  What happens on each operation: creating and linking incidents, the incident states, and the two sync modes.

  [Sync Behavior](https://userguide.qualytics.io/settings/integrations/ticketing/servicenow/deep-dive/sync-behavior/)
- **Requirements**

  The ServiceNow instance, the account Qualytics authenticates as, and what it must be allowed to do.

  [Requirements](https://userguide.qualytics.io/settings/integrations/ticketing/servicenow/deep-dive/requirements/)

*Last updated: October 5, 2026.*
