GuidePublished

ServiceNow integrations – REST, Integration Hub or MID Server?

There are several ways to connect ServiceNow to other systems. How to choose the right method for each integration – and avoid the most common traps.

Why the choice matters

Almost every ServiceNow solution we build has integrations. HR cases need data from the HR system, customer cases from CRM and ERP, and custom applications need to talk to everything from warehouse systems to production data.

There are several ways to build integrations, and the choice affects cost, maintenance and how well the solution survives upgrades. Here is an overview of the most common building blocks.

Inbound: when other systems call ServiceNow

  • Table API – ServiceNow's built-in REST API for reading and writing records. Quick to get started with, but it exposes the table structure directly. Suits simpler cases and internal use.
  • Scripted REST API – your own endpoints with your own logic and validation. Better when you want to control exactly what is received and offer a stable interface that is not affected if the data model changes.
  • Import sets and transform maps – for larger data volumes and regular imports, where data lands in a staging table first and is then transformed.
  • REST API trigger in flows – an inbound call or webhook can start a flow directly in Workflow Studio.

Outbound: when ServiceNow calls other systems

  • Integration Hub and spokes – ready-made connectors to common systems, built as actions used directly in flows. ServiceNow provides a large number of spokes, and custom ones can be built from API specifications.
  • REST steps in flows – for systems without a ready-made spoke, where you still want to work in flows rather than scripts.
  • Scripted REST calls – full control in code. Demands more of maintenance, but sometimes necessary for complex logic.

Keep in mind that Integration Hub is licensed and that outbound calls count as transactions. Check what your licence includes before choosing an approach, especially for high-volume integrations.

MID Server – for systems behind the firewall

If the system you want to reach sits in your own network, such as an on-premises ERP or database, you need a MID Server. It is installed in your network and handles communication between the ServiceNow instance and internal systems, so you do not have to open the firewall for inbound traffic.

How we choose in practice

  1. Is there a ready-made spoke? Use it if your licence allows. It is maintained and upgraded by ServiceNow or a certified partner.
  2. Do you need a stable external interface? Build a Scripted REST API instead of letting other systems write directly to tables.
  3. Large data volumes? Use import sets, so errors can be handled and traced.
  4. Internal system? Plan for a MID Server from the start, including running and monitoring it.
  5. Security and permissions. Use dedicated integration accounts with least privilege, and store credentials in the platform's credential management, never in scripts.

Our experience

The integrations that cause problems are rarely the ones that were hard to build. They are the ones nobody owns. Document every integration: who owns it, which systems and data it touches, how errors are handled and how it is tested during upgrades. It takes an hour per integration and saves many hours when something stops working.

Read more about how we work with integrations on ServiceNow.

Want to know what this means for your platform?

We help you assess what new features and releases mean for your instance – and which ones are worth acting on.

Talk to Colburn