# Triagic + ServiceNow: ticket investigations over your business systems, read-only

> ServiceNow in Triagic: Read incidents, changes, CMDB records, and knowledge articles. Read-only, with a credential you configure.

Source: https://triagic.com/integrations/servicenow

## What you can ask

- Pull the ServiceNow record for this customer and summarise the last three interactions
- In ServiceNow, has anyone else reported this since Monday?
- Which ServiceNow tickets from this account are still open, and who owns them?
- Does ServiceNow show a refund or a failed payment for order 8812?
- What did the customer say in the ServiceNow thread before this ticket was filed?

## What the agent can do

- `servicenow_query_table`
- `servicenow_get_record`
- `servicenow_list_tables`
- `servicenow_describe_table`
- `servicenow_aggregate`
- `servicenow_list_attachments`
- `servicenow_get_attachment`
- `servicenow_download_attachment`
- `servicenow_list_instances`
- `servicenow_get_status`
- `servicenow_test_connection`
- `servicenow_check_capabilities`

## Connect in three steps

1. **Mint a read-only credential in ServiceNow.** Create a dedicated user or token that can only read. The server's own read-only switch refuses create, update and delete, plus an allowlist of the query, get and describe tools.
2. **Add it in the Triagic portal.** Integrations, then Add shared data source, then ServiceNow. Fill in: Instance URL (required); Username (required): A service account with REST API access. Give it a read-only role: itil is enough to read incidents and changes.; Password (required); OAuth client ID (required): System OAuth → Application Registry → Create an OAuth API endpoint for external clients. Copy the Client ID from the registered application.; OAuth client secret (required): From the same Application Registry record. The client-credentials grant is used, so the token belongs to the application rather than to a person. Grant that application only read access.; API key (required): System Web Services → API Key. It is sent as the x-sn-apikey header, and reaches only the REST endpoints its associated inbound authentication profile allows.; Bearer token (required): A token you already hold; it is sent verbatim as Authorization: Bearer. Nothing here refreshes it, so the integration stops when it expires.
3. **Let a desktop pick it up.** Saving validates the shape of what you typed. The first desktop app to sync starts ServiceNow locally and reports running or degraded with the error text.

Setup reference: https://triagic.com/docs/integrations/business#servicenow

## Read-only, by construction

The server's own read-only switch refuses create, update and delete, plus an allowlist of the query, get and describe tools.

## FAQ

**Can Triagic change anything in ServiceNow?**
No. The server's own read-only switch refuses create, update and delete, plus an allowlist of the query, get and describe tools. Give it a read-only credential as well, so the guarantee does not rest on one layer.

**What do I need to connect ServiceNow?**
Instance URL, Username, Password, OAuth client ID, OAuth client secret, API key, Bearer token. The desktop app on a member's machine starts the connection; the portal never holds a live process.

**Does ServiceNow cost extra?**
No. Every connector is included in the seat price. Start a 14-day trial without a card.

## Related integrations

- [Atlassian](https://triagic.com/integrations/atlassian)
- [Stripe](https://triagic.com/integrations/stripe)
- [Slack](https://triagic.com/integrations/slack)
- [Notion](https://triagic.com/integrations/notion)