Complete step-by-step technical setup for binding OpsPilot to ServiceNow. Covers REST table API endpoints, OAuth2 token configuration, MID server proxying, and incident webhooks.
Architecture Overview & Authentication Scopes
PromptImageLab OpsPilot connects to ServiceNow via standard Table REST APIs (api/now/table/incident) or private MID Server endpoints. OAuth2.0 Client Credentials or Basic Auth with Service Accounts are both supported. For on-premise ServiceNow instances, the MID Server acts as a secure outbound proxy.
Configuring the Table API Connection
In ServiceNow, create a Service Account (non-interactive user) with the "rest_api_explorer" and "itil" roles. Generate OAuth2 credentials from System OAuth → Application Registry. Paste the client_id and client_secret into OpsPilot Connections.
Configuring Incident Creation Webhooks
In ServiceNow, create a Business Rule or REST Message trigger to POST to the OpsPilot webhook endpoint on incident creation. OpsPilot processes the payload asynchronously — typical analysis latency is under 8 seconds for standard incident descriptions with attached log text.
MID Server Proxying for On-Premise Instances
For ServiceNow instances behind corporate firewalls, deploy the PromptImageLab MID Server Agent alongside your existing ServiceNow MID Server. The agent registers as an ECC Queue consumer and routes OpsPilot API calls through the secure MID Server tunnel without opening inbound firewall rules.