---
title: "Service Graph Connectors Or Custom Integrations: Which Route Fits?"
description: When to use a Service Graph Connector, when to build a custom integration, and the identifier test that decides whether either one creates duplicates.
image: https://www.apexconfiguration.com/hubfs/AI-Generated%20Media/Images/Structured%20Cabling%20Patch%20Panel%20with%20Technicians%20Hand.png
---

[![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png "APEX CONFIGURATION GROUP")](https://www.apexconfiguration.com/)

[![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png "APEX CONFIGURATION GROUP")](https://www.apexconfiguration.com/)

- [Home](https://www.apexconfiguration.com)
- ServiceNow
    - [ServiceNow CMDB](https://www.apexconfiguration.com/servicenow-cmdb)
    - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check)
    - [CMDB Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation)
    - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services)
    - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools)
- Maximising ServiceNow
    - [CMDB Health Dashboard](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow)
    - [CMDB Dependency Mapping](https://www.apexconfiguration.com/cmdb-relationship-table)
    - [CMDB Configuration Items](https://www.apexconfiguration.com/cmdb-configuration-items)
    - [CMDB Workspace](https://www.apexconfiguration.com/cmdb-workspace-servicenow)
    - [CMDB Best Practice](https://www.apexconfiguration.com/cmdb-best-practices)
    - [ServiceNow Discovery](https://www.apexconfiguration.com/servicenow-discovery-setup)
    - [Service Mapping](https://www.apexconfiguration.com/servicenow-service-mapping)
- About
    - [How We Help](https://www.apexconfiguration.com/about-apex)
    - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb)
    - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb)
- Resources
    - [Blog](https://www.apexconfiguration.com/blog)
    - [Contact Us](https://www.apexconfiguration.com/contact-us)

[Contact Us](https://www.apexconfiguration.com/contact-us)

[Contact Us](https://www.apexconfiguration.com/contact-us)

- [Home](https://www.apexconfiguration.com)
- ServiceNow

    - [ServiceNow CMDB](https://www.apexconfiguration.com/servicenow-cmdb)
    - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check)
    - [CMDB Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation)
    - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services)
    - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools)
- Maximising ServiceNow

    - [CMDB Health Dashboard](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow)
    - [CMDB Dependency Mapping](https://www.apexconfiguration.com/cmdb-relationship-table)
    - [CMDB Configuration Items](https://www.apexconfiguration.com/cmdb-configuration-items)
    - [CMDB Workspace](https://www.apexconfiguration.com/cmdb-workspace-servicenow)
    - [CMDB Best Practice](https://www.apexconfiguration.com/cmdb-best-practices)
    - [ServiceNow Discovery](https://www.apexconfiguration.com/servicenow-discovery-setup)
    - [Service Mapping](https://www.apexconfiguration.com/servicenow-service-mapping)
- About

    - [How We Help](https://www.apexconfiguration.com/about-apex)
    - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb)
    - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb)
- Resources

    - [Blog](https://www.apexconfiguration.com/blog)
    - [Contact Us](https://www.apexconfiguration.com/contact-us)

[Contact Us](https://www.apexconfiguration.com/contact-us)

[tel:+442080588135](tel:+442080588135)[mailto:contact@apexconfiguration.com](mailto:contact@apexconfiguration.com)<https://www.linkedin.com/company/apex-configuration-group>

[IRE](https://www.apexconfiguration.com/blog/tag/ire)[ServiceNow](https://www.apexconfiguration.com/blog/tag/servicenow)

[Service Graph Connectors](https://www.apexconfiguration.com/blog/tag/service-graph-connectors)[Duplicate CIs](https://www.apexconfiguration.com/blog/tag/duplicate-cis)

# Service Graph Connectors Or Custom Integrations: Which Route Fits?

[![Warren O'Neill](https://www.apexconfiguration.com/hs-fs/hubfs/warren-oneill.webp?width=40&height=40&name=warren-oneill.webp)](https://www.apexconfiguration.com/blog/author/warren-oneill)

by [Warren O'Neill](https://www.apexconfiguration.com/blog/author/warren-oneill)

 7 min read

Nov 7, 2026, 9:00:01 AM

Last updated on 7 Nov 2026, 09:00:01

Use a Service Graph Connector wherever one exists for the source and carries the attributes you need. It loads data through the Identification and Reconciliation Engine, registers itself as a data source for reconciliation, and is maintained by someone other than your platform team. Build a custom integration only when there's no connector, or when the connector can't supply a value you've already decided you need. Whichever route you take, whether the integration helps or harms your configuration management database (CMDB) comes down to the identifier the source supplies, and whether your identification rules can actually use it.

## Key Takeaways

- Use a Service Graph Connector wherever one exists for the source and carries the attributes you need. Build a custom integration only when there's no connector or the connector can't supply a value you need.
- A connector registers its own data source, lands errors where you can report on them and is maintained through the ServiceNow Store. A scripted integration gives you none of that by default.
- Every integration is only as safe as the identifier it supplies. If the incoming record has nothing the identification rules can match on, the engine creates a new configuration item every time, and those duplicates never appear in de-duplication tasks.
- Pick one source to create configuration items for each cloud class, and let the others update specific attributes through reconciliation rules. Compare CMDB counts with the provider's console every month.
- Don't edit a Store connector. Build a small supplementary integration that updates only the missing attributes.
- Put every new data source through a gate before it writes to the CMDB. Record the classes it may create, the identifier for each, its precedence, its owner and the sub-production test evidence.

This article covers what a connector gives you that a scripted integration doesn't, the identifier test, how to run Microsoft Configuration Manager and Microsoft Intune side by side, where cloud data fits, and the rules a custom integration has to follow to be safe.

## What Service Graph Connectors do that a script doesn't

A Service Graph Connector is a ServiceNow Store application built on a standard pattern. It pulls data from the source into staging tables, transforms it, and passes it to the Identification and Reconciliation Engine, which decides whether each record updates an existing configuration item (CI) or creates a new one.

Three things follow from that pattern. Every record carries its data source, so reconciliation rules can decide which source is allowed to write which attribute. Errors land somewhere you can report on, instead of disappearing in a script log. And when the source vendor changes their interface, the connector is updated through the Store instead of by your team at short notice.

A connector still has costs. Store updates need testing before they reach production, like any other application. And you should check how your subscription counts the CIs a connector creates, before you point it at a source with a large estate behind it.

## The identifier question comes before the route

An integration of either kind is only as safe as the identifier it supplies. If the incoming record has nothing the identification rules can match on, the engine creates a new CI every time.

On a broadcast estate running to tens of millions of CIs, a cloud security tool was connected on the understanding that it was the definitive source for all cloud servers. It exposed no identifier for cloud virtual machines that matched anything discovery had already written. Every instance it reported was created as a new CI.

Because the engine had nothing to match on, it didn't see these records as duplicates, so they never appeared in the de-duplication tasks. A cloud administrator noticed only because the CMDB held twice as many instances as he could see in the tool. By then, change requests had been raised against the wrong CIs and change impact had been missed.

We stopped the tool creating cloud server CIs and brought them in through the Service Graph Connector for Amazon Web Services instead. Everything else the tool supplied carried on flowing in. The tool was fine. It just wasn't the right source for that class.

Before switching on any source, do three things:

1. List the identifiers it supplies for each class it will write to.
2. Confirm that at least one of them appears in the identification rule for that class.
3. Run it in a sub-production instance and compare a duplicate report grouped by serial number, and by cloud or hypervisor identifier, before and after.

Our article on [ServiceNow identification rules](https://www.apexconfiguration.com/blog/servicenow-identification-rules-how-cmdb-duplicate-prevention-really-works) covers the matching mechanics.

## Running Configuration Manager and Intune side by side

Microsoft Configuration Manager and Microsoft Intune both have Service Graph Connectors, and many estates run both. Co-managed devices appear in each, and servers may also be reached by ServiceNow Discovery. Without reconciliation rules, the last source to run wins every attribute.

Serial number is the identifier that usually lets all three meet on the same record. The harder decision is which source owns which attribute. A starting point we often use:

| Attribute area | Usual authority | Reason |
| --- | --- | --- |
| Server hardware and operating system | ServiceNow Discovery | Direct and current where discovery can reach |
| Installed software on managed Windows devices | Configuration Manager | Agent-based inventory is usually the most complete |
| Enrolment and compliance state on end-user devices | Intune | It holds the management relationship for those devices |
| Servers discovery can't reach | Configuration Manager, as a fallback | Better than no record, with the gap tracked |

Treat the table as a starting point for your own design, and record the reasoning with each rule. Our article on [reconciliation rules](https://www.apexconfiguration.com/blog/servicenow-reconciliation-rules-which-source-wins) explains how precedence and staleness settings work together.

## Cloud data: connector, discovery or both

For cloud estates you may have a Service Graph Connector for the provider, ServiceNow cloud discovery, and third-party security or cost tools that all describe the same virtual machines.

Pick one source to create CIs for each cloud class. Let the others update specific attributes only, through reconciliation rules. The creator should be the source with the most reliable identifier for that class. For the broadcast estate above, that was the provider's connector.

Then compare the CMDB count for each class with the provider's console every month. A mismatch is the cheapest alarm you'll ever get.

## When a custom integration is the right call

Custom integrations are sometimes the only option. The common cases are a source with no connector, an in-house system, or a connector that doesn't carry an attribute you've decided you need.

In the last case, resist editing the connector. Changes to a Store application can be overwritten by the next update or block it altogether. Build a small supplementary integration that updates only the missing attributes, and leave the connector as supplied.

Whatever the reason, a custom integration should meet the same standard as a connector:

- It writes through the Identification and Reconciliation Engine's programming interface, never directly to CMDB tables.
- It registers a named data source, so reconciliation rules can control it.
- It lands data in a staging table first, so failed records can be inspected.
- Its error log has a named owner who reviews it on a schedule.
- Its identifier for each class is documented and tested.

An integration that fails any of these is creating risk that someone else will pay for later, usually during a major incident.

## A gate for every new data source

Most integration problems we fix were preventable at the point the source was switched on. A simple gate prevents them.

Before any new source writes to the CMDB, it goes through the change advisory board or your design authority with five answers on the record: which classes it may create, which it may only update, the identifier for each, its reconciliation precedence, and its owner. Add a sixth, the test evidence from sub-production, and the gate becomes hard to wave through.

Track one key performance indicator (KPI) per source: CIs it created in the last month that were later flagged as duplicates. A source with a rising count needs its identifier revisited. Our article on [why integrations fail without accurate data](https://www.apexconfiguration.com/blog/servicenow-integration-accurate-data-value) covers the downstream effects.

## How Apex helps

Our discovery and integration coverage review covers horizontal discovery and third-party tool integration together. It establishes what's missing from your estate view, which sources are creating CIs they shouldn't, and which should be moved to a Service Graph Connector. It's scoped at the initial consultation against your estate and requirements.

Where multiple sources are fighting over the same records, our data quality assessment measures de-duplication, normalisation and reconciliation against weighted critical success factors, KPIs and metrics, and shows which rules are letting records through.

You can [book a CMDB diagnostic call](https://www.apexconfiguration.com/cmdb-diagnostic-call) to talk through your integration choices, or [book a meeting](https://www.apexconfiguration.com/book-a-meeting) with one of our consultants.

## Frequently asked questions

### What is a Service Graph Connector?

It's a ServiceNow Store application that brings data from a third-party source into the CMDB through a standard pattern of staging, transformation and the Identification and Reconciliation Engine. Each connector registers its own data source, so reconciliation rules can control what it writes.

### Can I customise a Service Graph Connector?

It's safer not to. Changes to a Store application can be overwritten or block future updates. If the connector lacks an attribute you need, build a small supplementary integration that updates only that attribute.

### Should Configuration Manager or ServiceNow Discovery own server data?

Where discovery can reach a server, it's usually the better authority for hardware and operating system attributes. Configuration Manager is often the better authority for installed software, and a useful fallback for servers discovery can't reach. Set this per attribute in your reconciliation rules.

### Why do some integration duplicates never appear in de-duplication tasks?

De-duplication tasks are raised when the engine finds more than one possible match. If an incoming record has no identifier the rules can match on, there's no match to find, so the engine creates a new CI and raises nothing. Comparing CMDB counts with the source's own console exposes these.

*Written by Warren O'Neill, Apex Configuration Group.*

Book a free call to discuss how Apex can help you on your journey to a better CMDB

 

[![\<p\>CMDB Diagnostic Call\</p\>](https://hubspot-no-cache-eu1-prod.s3.amazonaws.com/cta/default/147949153/interactive-378363509978.png)](https://www.apexconfiguration.com/hs/cta/wi/redirect?encryptedPayload=AVxigLIChL2gyHMxAoJxVSQaRvQ5wnYPV7dj5qDkux5VaQuxWn3vPxxjlRDQyS5qUxdVRBsnGuMdenCr1Pj2lUES6rlpbKom1SdvERf5%2FLs2jhZy2qfZESINrP73s%2FcmYVIy2bJMOW1EZTe5vVcPJ0XM2RpKa2tQDofeLyG5dg%2BZ5kFXwN%2BxQKR9xONQAurcvyx0DvVYXZCCHwXaZKlt49irdAQspv%2Fn5vVgqJXvDoXbASs%3D&webInteractiveContentId=378363509978&portalId=147949153)

- Recent
- Topics
- Archive

Recent

### Recent

Topics

### Topics

- [ServiceNow (50)](https://www.apexconfiguration.com/blog/tag/servicenow)
- [CMDB (35)](https://www.apexconfiguration.com/blog/tag/cmdb)
- [CMDB Data Quality (13)](https://www.apexconfiguration.com/blog/tag/cmdb-data-quality)
- [ServiceNow Discovery (9)](https://www.apexconfiguration.com/blog/tag/servicenow-discovery)
- [Case Studies (8)](https://www.apexconfiguration.com/blog/tag/case-studies)
- [Service Mapping (8)](https://www.apexconfiguration.com/blog/tag/service-mapping)
- [Change Management (7)](https://www.apexconfiguration.com/blog/tag/change-management)
- [IT Governance (6)](https://www.apexconfiguration.com/blog/tag/it-governance)
- [Vulnerability Management (6)](https://www.apexconfiguration.com/blog/tag/vulnerability-management)
- [CI Ownership (5)](https://www.apexconfiguration.com/blog/tag/ci-ownership)
- [Duplicate CIs (5)](https://www.apexconfiguration.com/blog/tag/duplicate-cis)
- [Compliance & Audit (4)](https://www.apexconfiguration.com/blog/tag/compliance-audit)
- [Configuration Management (4)](https://www.apexconfiguration.com/blog/tag/configuration-management)
- [Data Model Design (4)](https://www.apexconfiguration.com/blog/tag/data-model-design)
- [Enterprise Risk Management (4)](https://www.apexconfiguration.com/blog/tag/enterprise-risk-management)
- [ITOM (4)](https://www.apexconfiguration.com/blog/tag/itom)
- [Incident Management (4)](https://www.apexconfiguration.com/blog/tag/incident-management)
- [Service Graph Connectors (4)](https://www.apexconfiguration.com/blog/tag/service-graph-connectors)
- [Agentic AI (3)](https://www.apexconfiguration.com/blog/tag/agentic-ai)
- [Cyber Security (3)](https://www.apexconfiguration.com/blog/tag/cyber-security)
- [IRE (3)](https://www.apexconfiguration.com/blog/tag/ire)
- [Manufacturing (3)](https://www.apexconfiguration.com/blog/tag/manufacturing)
- [Problem Management (3)](https://www.apexconfiguration.com/blog/tag/problem-management)
- [Broadcast & Media (2)](https://www.apexconfiguration.com/blog/tag/broadcast-media)
- [CI Reconciliation (2)](https://www.apexconfiguration.com/blog/tag/ci-reconciliation)
- [CMDB Remediation (2)](https://www.apexconfiguration.com/blog/tag/cmdb-remediation)
- [CSDM (2)](https://www.apexconfiguration.com/blog/tag/csdm)
- [Dependency Views (2)](https://www.apexconfiguration.com/blog/tag/dependency-views)
- [IT Asset Management (2)](https://www.apexconfiguration.com/blog/tag/it-asset-management)
- [IT Cost Optimisation (2)](https://www.apexconfiguration.com/blog/tag/it-cost-optimisation)
- [Managed Services (2)](https://www.apexconfiguration.com/blog/tag/managed-services)
- [ServiceNow Advisory (2)](https://www.apexconfiguration.com/blog/tag/servicenow-advisory)
- [Operational Efficiency (1)](https://www.apexconfiguration.com/blog/tag/operational-efficiency)

See all

Archive

### Archive

- [November 2026 (2)](https://www.apexconfiguration.com/blog/archive/2026/11)
- [October 2026 (21)](https://www.apexconfiguration.com/blog/archive/2026/10)
- [September 2026 (16)](https://www.apexconfiguration.com/blog/archive/2026/09)
- [August 2026 (2)](https://www.apexconfiguration.com/blog/archive/2026/08)
- [July 2026 (4)](https://www.apexconfiguration.com/blog/archive/2026/07)
- [June 2026 (3)](https://www.apexconfiguration.com/blog/archive/2026/06)
- [May 2026 (2)](https://www.apexconfiguration.com/blog/archive/2026/05)

See all

### Subscribe by email

Share this

[Share on X](https://x.com/intent/post?url=https://www.apexconfiguration.com/blog/service-graph-connectors-or-custom-integrations-which-route-fits&text=Service+Graph+Connectors+Or+Custom+Integrations%3A+Which+Route+Fits%3F) [Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https://www.apexconfiguration.com/blog/service-graph-connectors-or-custom-integrations-which-route-fits&t=Service+Graph+Connectors+Or+Custom+Integrations%3A+Which+Route+Fits%3F) [Share on LinkedIn](https://www.linkedin.com/shareArticle?mini=true&url=https://www.apexconfiguration.com/blog/service-graph-connectors-or-custom-integrations-which-route-fits&t=Service+Graph+Connectors+Or+Custom+Integrations%3A+Which+Route+Fits%3F)

Previous story

[← Service Mapping: From Business Criticality To Infrastructure Impact](https://www.apexconfiguration.com/blog/service-mapping-from-business-criticality-to-infrastructure-impact)

<https://www.apexconfiguration.com/blog>

![Warren O'Neill](https://www.apexconfiguration.com/hs-fs/hubfs/warren-oneill.webp?width=64&height=64&name=warren-oneill.webp)

By [Warren O'Neill](https://www.apexconfiguration.com/blog/author/warren-oneill)

Co-owner and Technology Director at Apex Configuration Group, based in Bath, UK. Warren specialises in ServiceNow CMDB and CSDM, ITOM Discovery, Service Mapping and pattern development, with a focus…

[Full profile & credentials →](https://www.apexconfiguration.com/blog/author/warren-oneill)

### Get Email Notifications

[![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png)](https://www.apexconfiguration.com/)

ServiceNow CMDB specialists delivering enterprise-grade implementation, remediation, and managed services.

Address: 20 Wenlock Road, London,  
England, N1 7GU

VAT Number: 505 0347 31

Company Number: 15871442

Email: [contact@apexconfiguration.com](mailto:contact@apexconfiguration.com)

<iframe title="Cyber Essentials certificate" style="margin: 0px; display: inline-block; border-image: initial; border: medium none currentcolor;" xml="lang" src="https://registry.blockmarktech.com/certificates/fb6a3f80-c037-4589-a043-1b781ef328f9/widget/?tooltip_position=top_left&amp;theme=transparent&amp;hover=t" width="114" height="140"></iframe>

[Follow Apex Configuration Group on LinkedIn](https://www.linkedin.com/company/apex-configuration-group)

Services

- [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check)
- [Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation)
- [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services)
- [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools)
- [Health Dashboard & Reporting](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow)

Company

- [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb)
- [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb)
- [About](https://www.apexconfiguration.com/about-apex)
- [Blog](https://www.apexconfiguration.com/blog)

Resources

- [Contact Us](https://www.apexconfiguration.com/contact-us)
- [CMDB Diagnostic Call](https://www.apexconfiguration.com/cmdb-diagnostic-call)
- [Book A Meeting](https://www.apexconfiguration.com/book-a-meeting)

 © 2026 Apex Configuration Group. All rights reserved.

ServiceNow is a trademark of ServiceNow, Inc. We are not affiliated with or endorsed by ServiceNow.

- [Terms](https://www.apexconfiguration.com/terms)
- [Cookies](https://www.apexconfiguration.com/cookie-policy)
- [Privacy](https://www.apexconfiguration.com/privacy-policy)

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://www.apexconfiguration.com/#organization",
  "@type" : [ "Organization", "ProfessionalService" ],
  "address" : {
    "@type" : "PostalAddress",
    "addressCountry" : "GB",
    "addressLocality" : "London",
    "addressRegion" : "England",
    "postalCode" : "N1 7GU",
    "streetAddress" : "20 Wenlock Road"
  },
  "alternateName" : "Apex Configuration Group",
  "areaServed" : "GB",
  "contactPoint" : {
    "@type" : "ContactPoint",
    "areaServed" : "GB",
    "availableLanguage" : "en",
    "contactType" : "customer service",
    "telephone" : "+44 20 8058 8135"
  },
  "identifier" : {
    "@type" : "PropertyValue",
    "propertyID" : "UK Companies House company number",
    "value" : "15871442"
  },
  "image" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/Configuration-data.webp",
  "legalName" : "Apex Configuration Group Ltd",
  "logo" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png",
  "name" : "Apex Configuration Group Ltd",
  "sameAs" : [ "https://www.linkedin.com/company/apex-configuration-group", "https://find-and-update.company-information.service.gov.uk/company/15871442", "https://www.crunchbase.com/organization/apex-configuration-group-ltd" ],
  "telephone" : "+44 20 8058 8135",
  "url" : "https://www.apexconfiguration.com/"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://www.apexconfiguration.com/#website",
  "@type" : "WebSite",
  "inLanguage" : "en-GB",
  "name" : "Apex Configuration Group",
  "publisher" : {
    "@id" : "https://www.apexconfiguration.com/#organization"
  },
  "url" : "https://www.apexconfiguration.com/"
}
```

```json
{
  "@context" : "https://schema.org",
  "@type" : "WebPage",
  "description" : "When to use a Service Graph Connector, when to build a custom integration, and the identifier test that decides whether either one creates duplicates.",
  "inLanguage" : "en-GB",
  "name" : "Service Graph Connectors Or Custom Integrations: Which Route Fits?",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png"
    },
    "name" : "Apex Configuration Group Ltd",
    "url" : "https://www.apexconfiguration.com/"
  },
  "url" : "https://www.apexconfiguration.com/blog/service-graph-connectors-or-custom-integrations-which-route-fits"
}
```

```json
{
  "@context" : "https://schema.org",
  "@type" : "BreadcrumbList",
  "itemListElement" : [ {
    "@type" : "ListItem",
    "item" : "https://www.apexconfiguration.com/",
    "name" : "Home",
    "position" : 1
  }, {
    "@type" : "ListItem",
    "item" : "https://www.apexconfiguration.com/blog/service-graph-connectors-or-custom-integrations-which-route-fits",
    "name" : "Service Graph Connectors Or Custom Integrations: Which Route Fits?",
    "position" : 2
  } ]
}
```

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Warren O'Neill",
    "sameAs" : [ "https://www.linkedin.com/in/warren-oneill/" ],
    "url" : "https://www.apexconfiguration.com/blog/author/warren-oneill"
  },
  "dateModified" : "2026-11-07T09:00:01+0000",
  "datePublished" : "2026-11-07T09:00:01+0000",
  "headline" : "Service Graph Connectors Or Custom Integrations: Which Route Fits?",
  "image" : [ "https://147949153.fs1.hubspotusercontent-eu1.net/hubfs/147949153/AI-Generated%20Media/Images/Structured%20Cabling%20Patch%20Panel%20with%20Technicians%20Hand.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://www.apexconfiguration.com/blog/service-graph-connectors-or-custom-integrations-which-route-fits",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png"
    },
    "name" : "Apex Configuration Group Ltd",
    "url" : "https://www.apexconfiguration.com/"
  }
}
```