---
title: Connect AI agents to ServiceNow
slug: servicenow
integration: ServiceNow
category: support
connectionType: oauth-rest
status: published
publishedAt: "2026-05-06T18:13:40.817Z"
lastUpdated: "2026-05-06T18:13:44.295Z"
canonical: "https://fidelic.ai/integrations/servicenow"
topSearchQueries:
  - "servicenow mcp"
  - "chatgpt servicenow"
  - "servicenow ai integration"
---

# Connect AI agents to your ServiceNow instance

*AI agents that read your ServiceNow tables, draft new records, and post the result to Slack — IT runbook briefs, incident summaries, and HR ticket hygiene.*

## The connection

Fidelic agents connect to ServiceNow through OAuth + the ServiceNow Table API. Your agent reads the tables and records the instance admin explicitly grants — Incident, Change, Knowledge, or any custom table you authorize.

When the agent reads, it stays inside the tables you've shared. Nothing leaves your ServiceNow instance unless the agent posts a brief to [Slack](https://slack.com/) or creates a record in a table you authorized.

## Permissions requested

- Read records in tables the instance admin explicitly grants
- Create new records in tables the agent has write access to
- Read user metadata for proper attribution

Official docs: <https://docs.servicenow.com/bundle/utah-application-development/page/integrate/inbound-rest/concept/c_RESTAPI.html>

## Before you start

- A ServiceNow instance — any tier.
- Instance admin role.
- A Slack workspace where the agent will live and post.
- A decision on which ServiceNow tables the agent should reach.
- About five minutes for the OAuth flow.

## How to connect

1. **Sign in to Fidelic and pick the agent.** From the Roster, choose the agent that needs [ServiceNow](https://www.servicenow.com/) access.
1. **Authorize **[**ServiceNow**](https://www.servicenow.com/)**.** Click Connect [ServiceNow](https://www.servicenow.com/). The OAuth dialog opens; sign in with your instance admin account. The app appears in System OAuth → Application Registry.
1. **Pick the tables the agent should reach.** Pick the tables and records the agent will read or write to.
1. **Confirm and finish.** The agent runs a test read. When it passes, your [Slack](https://slack.com/) channel shows a Connected to [ServiceNow](https://www.servicenow.com/) message.
1. **Try the first agent action.** Ask for an IT runbook brief in [Slack](https://slack.com/).

## How you'll know it worked

Three signals confirm the connection is live.

- **Slack — **your channel shows a Connected to ServiceNow message naming the agent and the tables it can reach.
- **ServiceNow — **System OAuth → Application Registry shows the Fidelic OAuth app with the tables you authorized.
- **First output — **the agent answers with citations to specific ServiceNow records.

## Connection limits

Where the connection draws the line:

- **· **The agent only reads tables the admin explicitly grants.
- **· **ServiceNow workflows and business rules run server-side; the agent reads their output.
- **· **For Now Assist or Virtual Agent integration, those run separately.

## Where the data goes

The connection runs inside your sandboxed [Anthropic](https://www.anthropic.com/) project. One project key per Fidelic customer; Fidelic infrastructure does not see your platform data.

Anything the agent reads stays inside your environment. The only data that leaves is what the agent posts to [Slack](https://slack.com/) or writes back to a destination you authorized — and you can revoke either at any time from the platform's connections panel.

---
Canonical: https://fidelic.ai/integrations/servicenow