Atlassian Assets

Atlassian Assets + Konnectify

Atlassian Assets Integration with Konnectify

Connect Atlassian Assets (formerly Insight) to Konnectify to manage CMDB and IT asset records—create, retrieve, update, and delete asset objects as part of your Jira Service Management processes.

Objects 0 Triggers 4 Actions

ON THIS PAGE

→ What is Atlassian Assets? → API & Authentication → How to connect → Triggers (0) → Actions (4) → Popular automations → FAQ

What is Atlassian Assets?

Atlassian Assets (formerly Insight) is Jira Service Management’s asset and configuration management (CMDB) capability. It helps teams model schemas, object types, attributes, and objects to keep a reliable source of truth for IT assets and relationships.

By integrating Atlassian Assets with Konnectify, you can automate asset record lifecycle operations from your workflows—keeping your CMDB in sync with service requests, onboarding/offboarding processes, and operational systems.

New to Atlassian Assets?

Get started with Jira Service Management and Assets to model and manage your CMDB.

Explore Atlassian →

New to Konnectify?

Build workflows that connect Atlassian Assets to your helpdesk, HRIS, IAM, or internal tools—without heavy engineering.

Create a Konnectify account →

What you can automate

• Create new asset objects for onboarding and procurement

• Update object attributes from external systems (HR, IAM, MDM)

• Fetch object details during ticket triage and enrichment

• Delete stale or decommissioned assets on lifecycle events

• Standardize asset records across schemas and object types

• Keep your CMDB consistent with downstream automation steps

API & Authentication

OAuth 2.0 authorization

Konnectify connects to Atlassian Assets using OAuth 2.0. During connection setup, you’ll be redirected to Atlassian to grant access; then Konnectify stores only the authorized tokens needed to make API calls (not your Atlassian password). Offline access is used so workflows can run in the background.

Requested permissions typically include reading and managing:

CMDB schema, object types, and attributes
CMDB objects (read/write/delete)
Service Management request context (as applicable)

Plan limits & rate limits

Atlassian API availability and Assets features can vary by Jira Service Management plan and your organization’s configuration. If you hit API rate limits, Konnectify will retry where possible—design workflows with batching and backoff in mind.

Official docs: Atlassian Cloud APIs (Jira Service Management) and Assets API docs.

How to connect Atlassian Assets to Konnectify

Prerequisites

An Atlassian Cloud organization with Jira Service Management and Assets enabled
An Atlassian OAuth 2.0 (3LO) app with a Client ID and Client Secret
Your Atlassian Domain (e.g., my-company)
Permission to access and modify Assets objects in the relevant schema

Add Atlassian Assets to a Workflow

Create or open a workflow in Konnectify.
Search for Atlassian Assets in the app picker.

Authorize via OAuth 2.0

Enter your Domain, Client ID, and Client Secret.
Click Connect, then approve access in Atlassian when prompted.

Configure the Action

Select the action you need (Create, Get, Update, or Delete Object).
Map required IDs and attribute values from previous steps.

Important Deleting an object is permanent. In production workflows, consider adding an approval step or a condition (e.g., only delete when an asset is in a “Decommissioned” state).

Test the Workflow

Run a test with sample IDs and attribute payloads.
Verify the object changes in Atlassian Assets.

Activate the Workflow

Turn on the workflow.
Monitor runs and add alerts for failures or rate-limit retries.

Triggers 0

This integration currently has no triggers. You can still build workflows by using Atlassian Assets actions after triggers from other apps (e.g., ticket creation, onboarding events, or scheduled runs).

Tip If you need “when an object changes” style automations, use a trigger from another system (or a schedule trigger) and then call Get Object to detect changes before updating your downstream records.

Actions 4

Use actions to create and manage Assets objects inside your workflows.

Objects 4 actions

Create Object

Create a new asset record

Get Object

Gets the details of a specific object by its ID.

Update Object

Updates the attribute values of an existing object.

Delete Object

Permanently deletes an object from Assets.

Popular automations

Examples of common Atlassian Assets workflows you can build with Konnectify (using triggers from other apps or schedules).

Enrich service tickets with asset details

When a ticket is created in your helpdesk, fetch the related asset record and attach key fields (owner, warranty, location) to the ticket.

New Ticket (other app) → Get Object → Update Object

Provision assets for employee onboarding

When a new employee starts, create an asset object (e.g., Laptop, Phone) and stamp default attributes like assigned user and start date.

New Employee (other app) → Create Object

Keep CMDB attributes in sync with your source of truth

On a schedule, fetch an object and update attributes like status, cost center, or location based on your inventory system.

Scheduled Run (Konnectify) → Get Object → Update Object

Decommission assets on offboarding

When an offboarding request is approved, update the asset status—or permanently remove the object if your policy requires it.

Offboarding Approved (other app) → Update Object → Delete Object

FAQ

How does authentication work for Atlassian Assets in Konnectify?

The integration uses OAuth 2.0. You provide a Client ID/Secret for your Atlassian OAuth (3LO) app and approve access in Atlassian. Konnectify uses the resulting access/refresh tokens to call the Assets APIs.

Which Atlassian plans are supported?

Support depends on whether Jira Service Management Assets is enabled in your Atlassian Cloud instance and whether your plan includes the required Assets functionality. If an endpoint is unavailable for your plan, the workflow step will fail with an Atlassian API error.

How do triggers work for this integration?

This connector currently provides no native Atlassian Assets triggers. Use triggers from other apps (tickets, HR, IAM, inventory), or a scheduled trigger in Konnectify, then call Assets actions like Get Object / Update Object.

How can I prevent duplicate asset objects?

There is no dedicated upsert action in this version. A common pattern is: Get Object (when you already have an object ID) → Update Object. If you only have an external identifier, maintain an internal mapping (e.g., in a database/table step) from external ID to Assets object ID.

What happens if Atlassian rate-limits my workflow?

If Atlassian responds with a throttling or transient error, Konnectify will retry when possible. To reduce rate-limit risk, avoid tight loops, use schedule spacing, and only call Get Object when needed.

Can I connect multiple Atlassian organizations or sites?

Yes. Create separate Konnectify connections for each Atlassian domain/site (and OAuth app credentials if required). Then select the correct connection inside each workflow step.

How do I know which attributes to send when creating or updating an object?

Attributes are defined by your Assets schema and object type. Use Atlassian Assets configuration (or the Assets API) to confirm attribute IDs, required fields, and data types (text, select, reference, date, etc.). If an update fails, the API error usually indicates which attribute/value is invalid.

Ready to automate your Atlassian Assets workflows?

Connect Atlassian Assets to Konnectify and keep your CMDB and asset records consistent across your tools.

Get started free →