ServiceNow "Create Change" action failing in CI

By Kaveh Alemi·Latchkey

The ServiceNow DevOps Change action creates a change request from CI. It fails when the instance URL, DevOps integration token, or tool/orchestration id are missing or wrong, or when the DevOps app is not configured for the pipeline.

What this error means

The ServiceNow change step errors with a message about a missing token, an unknown tool id, or a non-2xx response from the DevOps Change API, so no change is created.

Run ServiceNow/servicenow-devops-change@v5
Error: ServiceNow DevOps Change Creation failed: 401 (check devops-integration-token and instance-url)

Common causes

Missing or wrong action inputs

The action needs instance-url, devops-integration-token, tool-id, and the job/context. A missing input or wrong token makes it fail.

The DevOps app is not wired to this pipeline

If the ServiceNow DevOps integration is not configured for the tool/orchestration, the change API rejects the request.

How to fix it

Provide all required inputs from secrets

1. Set instance-url to your instance host and pass the DevOps token as a secret.
2. Provide the correct tool-id from the ServiceNow DevOps config.
3. Ensure the pipeline is registered in the DevOps integration.

- uses: ServiceNow/servicenow-devops-change@v5
  with:
    instance-url: ${{ secrets.SN_INSTANCE_URL }}
    devops-integration-token: ${{ secrets.SN_DEVOPS_TOKEN }}
    tool-id: ${{ secrets.SN_TOOL_ID }}
    job-name: 'deploy'

Confirm the DevOps integration config

Verify the tool/orchestration exists in ServiceNow DevOps and the token maps to it, so the change API accepts the call.

How to prevent it

• Store instance URL, DevOps token, and tool id as secrets.
• Register the pipeline in the ServiceNow DevOps integration.
• Pin the action version and keep inputs in sync with the config.

Frequently asked questions

Related guides

References

• GitHub Actions documentation