top of page

Share the Wealth: Outbound REST Integrations in ServiceNow

Updated: Feb 1, 2021

In this week’s Share the Wealth video, Chris Yang of GlideFast gives an overview and demonstration of Outbound Representational State Transfer (REST) Integrations in ServiceNow.

The Challenge

Why do we need REST integration? Consider the following challenges:

  • Data is stored in other enterprise applications.

  • ServiceNow is not the best place to maintain that data.

  • ServiceNow needs that data to support certain business processes.

  • Don’t want to update data manually.

We can set up REST integration as a solution.

What is REST?

REST is a standard created to allow communication between two computers. It can receive data from another system by either making a request (outbound), or listening on a specific endpoint (inbound). The focus of this overview is outbound.

A Few Things You Need:

  • web_service_admin role

  • REST API endpoint

  • MID Server (optional)

  • Authentication- Basic, Oath2.0 Profiles, Token (optional)

The WorkFlow

  1. Send the request to the external system.

  2. Wait for a response to be returned.

  3. Process the response and store the data into an import set.

  4. Transform the import set using a transform map.

  5. Validate the data.

Demo: Cryptocurrency Prices

REST Message

Define the endpoint, request headers, and authentication.

Scheduled Job

  1. Trigger the REST message.

  2. Wait for a response (discusses async in demo).

  3. Process the response.

  4. Populates the import set table (x_crypto_impset).

Transform Map

Transform the import set to our SN table.


Interested in working with experts like Chris? Reach out to our team. We would love to learn more about your ServiceNow challenges and how we can help your organization build better solutions.

527 views0 comments

Recent Posts

See All
bottom of page