We continue to expand our integration capabilities for Assets in Jira Service Management, and are excited to announce support for CDW. In this blog, we’ll walk you through the integration steps and explain how you can keep your asset inventory in sync by using CDW’s webhook and OnLink’s native import capabilities.
CDW is a leading IT solutions provider that serves businesses, government agencies, educational institutions, and healthcare organizations. CDW offers a broad portfolio of products and services, including hardware, software, cloud, cybersecurity, and managed IT solutions. Their hardware management services span procurement, configuration, deployment, inventory tracking, warranty management, and secure end-of-life disposal.
CDW also offers API capabilities, including webhooks, which allow subscribed systems to receive real-time updates on asset-related events such as purchases, dispatches, or lifecycle status changes.
OnLink enables webhooks based imports into Jira Service Management Assets by configuring a secure endpoint to receive asset change notifications. This allows CDW to push asset updates like asset addition, changes, serial number changes, or ownership details directly into Assets in Jira Service Management.
Note: CDW does not currently offer self-service webhook configuration, integration is still possible by working with your CDW account manager or integration specialist.
On your end, setting up OnLink is simple and self-service:
Log in to your OnLink app.
Go to Webhooks in the left-hand menu.
Click the “Add” button to create a new webhook.
Provide a name for your integration (e.g., CDW Asset Import).
Select the “Import to Assets” checkbox.
You will now see fields for:
Workspace ID (linked help text shows how to retrieve it)
Asset Schema and Object Type (select based on your schema structure)
This URL is what CDW will use to push asset data to OnLink.
Share this endpoint, along with authentication credentials, with your CDW representative to enable real-time event delivery.
Here is a sample mapping that you can use as reference.
key:u_asset_tag=Worker_ID
map:u_edc=Name
map:u_customer_name=First_Name
map:u_item_class_code=Dept|Name=${u_item_class_code}
config:auth_scheme=basic_auth
config:auth_username=testuser
config:auth_password=xxxxxxx
Let’s break it down:
key:u_asset_tag=Worker_ID
This line sets Worker_ID from CDW as the unique key mapped to the Jira Assets field u_asset_tag.
map:u_edc=Name
Maps the CDW field Name to the asset attribute u_edc.
map:u_customer_name=First_Name
Maps First_Name from CDW to u_customer_name in Jira Assets.
map:u_item_class_code=Dept|Name=${u_item_class_code}
Composite mapping that sets u_item_class_code by referencing department or name values from CDW input.
config:auth_scheme=basic_auth
Sets the authentication method to basic auth.
config:auth_username / config:auth_password
Credentials that CDW will use to authenticate before pushing data.
Real-time asset updates as CDW processes your hardware orders
Eliminate manual imports or spreadsheet syncing
Better asset management accuracy in Jira Service Management
Enable automations that links assets to HR events e.g onboarding/offboarding through up-to-date asset visibility
Compliance-ready tracking for IT audits and procurement workflows
By using OnLink, we can create an automated update of asset data flowing straight from CDW to Assets in Jira Service Management. No spreadsheets, no file imports or any manual scripts are required.
If you’re already using CDW as your hardware provider, elevate your asset management with OnLink and Assets in Jira Service Management. Please give OnLink a try and let us know your feedback.
Backed By
APPS
PAGES
Company
