Skip to content

ServiceNow

Create, read and update ServiceNow incidents, and create and list service requests and change requests, through the Table API.
Nodes ServiceNow (actions), ServiceNow Trigger (polling)
Auth OAuth 2.0 with your own ServiceNow OAuth application. Basic auth does not work yet.
Availability Limited release. Not yet in the palette for customer workspaces.

Connecting

OAuth 2.0 (works)

  1. In your ServiceNow instance, open System OAuth → Application Registry and create an OAuth API endpoint for external clients.
  2. Add the Redirect URL from Flero's credential dialog.
  3. In Flero, choose OAuth 2.0 and enter your instance name, for example dev12345 for dev12345.service-now.com.
  4. Paste the client ID and secret, keep the read and write scopes, and click Connect with ServiceNow.

Basic auth (does not work)

The credential dialog offers a username and password, but the connector does not send Basic authentication. Requests made with a Basic credential arrive unauthenticated. Use OAuth.

Operations

Table Operation Fields
Incident List incidents sysparm_limit, sysparm_query
Incident Get incident sys_id
Incident Create incident short_description, description, priority, category, caller_id
Incident Update incident sys_id; short_description, description, state, priority, assigned_to
Service request List service requests, Create service request short_description, requested_for
Change request List change requests, Create change request short_description, type, risk

ServiceNow wraps the record in result, so a new incident's sys_id is {{ $node["Create Incident"].output.data.result.sys_id }}.

For other tables, call the Table API with the HTTP Request node.

Triggers

The ServiceNow Trigger polls the list operations, every 5 minutes by default. It is in limited release.

Common errors

Symptom Check
401 with a Basic credential Basic auth is not sent. Use OAuth.
401 with OAuth The token expired and could not refresh. Reconnect.
403 The signed-in user's ServiceNow roles do not allow that table.
Requests go to the wrong instance Check the instance name on the credential.

Found something out of date? This page lives in the Flero docs content set.