ServiceNow Baramundi Integration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hello Community,
anybody already done a ServiceNow Baramundi Integration ?
We are currently using MECM for Software Distribution for Windows Client
and consider a change to the Software Distribution tool Baramundi.
For MECM there is a OOTB Integration (SCCM Spoke) availible. Using this Spoke we are able to issue
activities from ServiceNow against MECM.
For Baramundi there is no OOBT integration availible, so it has to be implemented using the bConnect REST API (we want to use the Baramundi Cloud Solution, NOT on-prem).
Therefore the REST API seems to be the only option for integration.
Is there anybody in the community who has done this before ?
We would highly appreciate it when he/she would share his/her experience (easy/difficult to implement) ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
40m ago
Hi there my Friend
Yes — it’s definitely possible to integrate Baramundi with ServiceNow, but since there’s no OOTB spoke like there is for MECM/SCCM, it will require a custom REST API integration using Baramundi’s bConnect API.
Here’s how it usually works:
Outbound from ServiceNow: You can use RESTMessageV2 or basically Flow Designer REST actions to call Baramundi’s API to trigger software deployments, queries, or other jobs.
Inbound to ServiceNow: Baramundi can send updates back via webhook, or you can poll its API for status, updating RITMs or tasks accordingly.
Optional orchestration: You could wrap this in Flow Designer flows or even build a small custom IntegrationHub spoke for reusability.
How hard is it?
If you’re familiar with RESTMessageV2 or Flow Designer -> it’s moderate effort.
If you want bi-directional sync with retries, error handling, etc. → medium complexity. Most of the work is mapping Baramundi actions/status to ServiceNow records.
Some Great Tips Learned Along The Way:
Keep authentication and error handling clean — REST integrations fail often if you skip retries.
Consider storing all integration actions in a single custom table for easier tracking.
If you want to save development time, an iPaaS solution (like ONEiO) can sit between ServiceNow and Baramundi to handle the integration.
At the End of the Day:
No OOTB spoke exists → REST API is your best option.
It’s totally doable and many teams integrate ServiceNow with third-party management tools this way.
@YD2 - Please give a Thumbs up and Accepted Solution if you find Helpful! Thanks Kindly