Should I use the native ServiceNow integration API's or use Mulesoft to control all API's regardless if a native API is available?

[pszpakowski]

There are several API's available that are used within the ServiceNow instance.  GitHub, Jenkins, Flexara, etc.  My question is with Mulesoft integrated should we use Mulesoft to integrate these API's or use the native API's from ServiceNow?  Benefits and Negatives of each?  What are your thoughts?

[Rahul Priyadars]

Before Going into Solution- May i have your use case in more functional way? What is the end Goal ?

Just to let you know - We are using Another ESB (Dell Boomi) like Mulesoft to Integrate our Domain Separated Service Now Instance which is used by Shared Services Team. 

Our use cases forced us to use Dell Boomi as Middle layer for almost all service now integrations.

Regards

RP

[pszpakowski]

Have you had to re-develop these API's.  Use case would be any api. 

[Rahul Priyadars]

we have not developed API in our case.

Dell Boomi has many inbuilt connector and even it was for service now- But OOTB Connector was not able to fulfill our needs. So we built Boomi Processes using HTTP connector. This uses Service Now standard APIs.

Our data processing and data transformation is happening at Boomi layer. Also no load or Performance issue on Source/Destination system.

System1 ----Throw data-----> Dell boomi (Transform/Translate/Process) -----> System2

System2-----Throw Data----->Dell boomi (Transform/Translate/Process) -----> System1

All done using standard APIs of System1 , Boomi and System 2.

Hope this helps.

Regards

RP

[GustavoR10]

What kind of issues did you found that make you think that connectors are not enough?