Skip to main content
Plan a ServiceNow workflow that reads an approved incident and drafts a work note. Keep assignment changes, state transitions, and customer-visible comments as separate decisions.
There is no native ServiceNow connector in the current catalog. This guide covers preparation for an external integration, not a released incident runner.

​
Prepare incident access

You need an instance administrator, a test incident, and an agreed list of tables and fields the integration may access.
1

Review the instance's access controls

ServiceNow’s REST API documentation describes Basic or OAuth authentication and endpoint, table, and field access controls. Select an approved method and the minimum required roles. Do not use an administrator account as a shortcut around a rejected request.
2

Define a precise incident lookup

Resolve the instance, table, and record’s sys_id. Return only required incident fields. Have your service constrain filters and identifiers instead of accepting unrestricted generated queries. A field omitted by access control should remain unavailable.
3

Review the destination field

Confirm the target incident, text, and intended audience before a future write. Review work notes separately from comments and verify visibility in your instance. On timeout or conflict, read the current record before retrying. Do not report a state transition as complete without its saved result.
Use auth connections for supported manual configuration and tool authoring for the action contract. Your integration still owns instance-specific authorization and execution.

​
Frequently asked questions

Authentication identifies the caller. Endpoint, table, and field controls determine what that caller can access. Review those controls with the instance administrator.
No. The provider’s workflow rules and authorization still apply. Validate permitted changes against the current record.