@devries-cameron20 / composio Mirror · read-only
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 04:45 UTC

next
md 1.24 KB

type: "guide" title: "ServiceNow authentication" description: "Current instance-specific authentication setup for ServiceNow." category: "auth-config" visibility: "public" timestamp: "2026-08-17T00:00:00Z" tags:

- "servicenow"

ServiceNow authentication

ServiceNow credentials and instance subdomain are collected at different stages

The current servicenow toolkit supports Basic, OAuth2, and S2S OAuth2. OAuth auth-config creation accepts the ServiceNow application's client ID and client secret. Connection initiation then requires the instance subdomain, such as mycompany for mycompany.service-now.com.

ServiceNow registers an inbound OAuth client inside a ServiceNow instance. A client registered in one customer instance does not automatically authorize an unrelated instance. Use a separate customer-owned auth config when different customers supply different ServiceNow application registrations.

Use delegated OAuth2 when a user should sign in and consent. Use S2S OAuth2 for a backend integration whose identity and permissions are configured by the ServiceNow administrator. Fetch the current toolkit metadata before building a form because the required fields are separated into auth_config_creation and connected_account_initiation.