Syncing Jira Assets (cloud) with ServiceNow CMDB

I am looking to implement a one-way sync from Jira Service Management Cloud (Assets/CMDB) to ServiceNow CMDB tables using Exalate, and i need clarification on whether this is achievable and what the recommended approach would be.

My use case is straightforward in concept: we have CIs stored as objects in Jira Assets (organized in object schemas with attributes), and we want those CIs to be pulled and used to populate the corresponding ServiceNow CMDB tables (e.g. cmdb_ci_server, cmdb_ci_business_app, etc.) as records. We are not syncing Jira issues — we want to sync the Assets objects themselves, independently of any linked issue (if possible).

My questions are: (1) Is there a supported or recommended way to have Exalate read directly from Jira Cloud Assets objects? (2) Is the Basic Auth HTTP Client workaround for this use case, and are there any documented examples? (3) Has anyone implemented a Jira Cloud Assets → ServiceNow CMDB pipeline with Exalate.

Any info from the team or community would be greatly appreciated :smiling_face_with_sunglasses: .

Hi @txylos ,

Welcome to the Exalate Community Portal, and thank you for posting your query here. I will be reviewing this and write you back soon.

Kind regards,

Ashar, Exalate Support

Hello @txylos ,

Exalate does not support syncing Jira Assets (CMDB objects) as a native entity.

However, this can be achieved using Script Mode with custom HTTP calls to the Jira Assets REST API. This allows you to fetch object data and pass it through the sync payload.

In practice, since Exalate’s synchronization is typically triggered via work items (issues), these scripts are usually executed in that context, even if the actual data being synchronized comes from Assets.

On the ServiceNow side, CMDB tables are supported out of the box, so Exalate can directly create or update records (e.g., cmdb_ci_server, cmdb_ci_business_app) without additional workarounds.

While there is no out-of-the-box template for Jira Assets → ServiceNow CMDB, this approach is commonly used for building custom integrations.

Hope this helps! :slightly_smiling_face:

Kind regards,

Ashar