The Faddom JSM integration automatically pushes your live infrastructure discovery data into Jira Service Management - Assets, keeping your CMDB accurate without manual maintenance. By using Faddom's discovery capabilities, we are able to populate multiple types of objects directly into JSM using Faddom's schema. You can then use Assets Data Manager to map Faddom's object types into your schema.
What Faddom syncs to JSM
Faddom automatically creates and populates the following object types in your JSM Assets schema.
All server object types share the following attributes: Faddom server ID, display name, IP address, subnet, Faddom risk score, platform, OS name, OS family, MAC address, CPU core count, memory, and a link to the server properties page in Faddom. Any custom tags defined in Faddom are also synced as additional attributes on all server objects.
Object type | Additional platform-specific attributes |
VMware VM | VM ID, VM name, host name, vCenter management server |
AWS Instance | Instance ID, instance type, region, availability zone, VPC, subnet ID |
GCP VM | Instance ID, instance type, project ID, zone |
Azure VM | VM ID, VM size, region, resource group, subscription ID |
Nutanix VM | VM ID, cluster ID, host ID, Prism Central ID, controller IP |
Oracle Cloud VM | Instance ID, instance shape, compartment ID, region, availability domain, virtual cloud network ID |
Manually Added Server | Standard server attributes only |
Other IP Addresses | Standard server attributes only |
Application | Application ID, application name, type (Entry, Tracked, or Tag-Based), parent folder name, application map URL, related servers |
Prerequisites
Before setting up the integration, make sure you have the following:
Faddom is installed with data sources configured
A Jira Service Management Premium or Enterprise plan
The Faddom JSM Integration app was installed from the Atlassian Marketplace
Set up the integration
The setup involves two parts: configuring a schema in JSM and connecting it to Faddom.
Part 1: Create a schema in JSM
Follow the steps below to create and configure an asset schema in JSM.
Step by step:
In JSM, go to Assets, select Schemas, and select Create Schema.
Select Blank Schema, enter a name, and select Create Schema.
Go to Schema Settings, select Imports, and select Create Import.
Select Faddom as the import type and select Next.
Enter a name for the import and select Next.
Wait 20–30 seconds while Faddom automatically creates all object types, attributes, and mappings in your schema. No manual configuration is required.
Once complete, go back to the schema to confirm the object types were created successfully.
Part 2: Connect JSM to Faddom
Follow the steps below to connect your JSM schema to Faddom and run your first sync.
Step by step:
In the Faddom JSM Integration app, copy the Webhook URL from the top of the page.
Generate an authentication token. Save this token somewhere safe - it won't be shown again.
Locate your newly created schema at the bottom of the page and copy the Import ID In Faddom, go to Settings, select Integrations, and select Jira Service Management.
Select New Integration and enter the following:
The webhook URL
The import ID
The authentication token
A name for the integration
Select the asset types to sync - servers, applications, or both.
Select Save.
Select Run to run your first manual sync. This takes approximately 30 seconds, depending on the number of assets.
Set a sync schedule
You can set up a schedule to keep JSM Assets automatically up to date.
In Faddom, go to Settings, select Integrations, select Jira Service Management, and select your integration. From here, configure a sync schedule that fits your needs.
Tip: A scheduled sync ensures JSM Assets always reflects your live infrastructure without any manual effort.
Sync history
To review past syncs, select your integration from the "Jira Service Management" integrations list. The sync history shows the integration name, synced entities, record counts, and whether each sync was triggered manually or by a schedule.