OnLink · Webhooks
OnLink webhooks let any system POST events straight into Jira Service Management or Assets: an incident opens in BigPanda, an invoice changes in Snowflake, a deployment finishes, and the ticket gets created or Assets object is created in seconds, with no custom code or middleware.
|
|
Batch import (scheduled)
|
Webhook (event-based)
|
|---|---|---|
|
Trigger
|
OnLink pulls from the source API on a schedule
|
The source POSTs to OnLink when something happens
|
|
Latency
|
Minutes to hours, depending on the schedule
|
Seconds
|
|
Best for
|
Full inventories: devices, people, CIs
|
Incidents, invoices, deployments, lifecycle events
|
|
Configuration
|
Connection, request, pagination, mapping
|
Webhook, auth scheme, mapping; no schedule
|
|
Reconciliation
|
Each run refreshes every record
|
Each event updates one record, keyed on an ID
|
A few examples where event-based wins:
An incident is attached to the affected CI in Assets the moment it opens, and updated as its status changes.
Finance records land in Assets as they change, next to the hardware they paid for.
Record what happened to an asset, when, and from which pipeline, as it occurs.
BigPanda’s Notifications Webhook is the outbound half of this integration. It lets BigPanda POST incident data to an external system whenever an incident is shared or changes state.
{
"incident": {
"id": "5555370aabc20a001145d6g9",
"status": "Critical",
"active": true,
"severity": "Critical",
"flapping": false,
"resolved": false,
"snooze": {
"snoozed": false,
"wake": null,
"autoCancel": false
},
"startedOn": 1649576282,
"changedOn": 1649576282,
"updatedOn": 1652897578,
"endedOn": null,
"alerts": [
{
"id": "5555370aabc20a001145c5e9",
"status": "Critical",
"startedOn": 1649576282,
"endedOn": null,
"changedOn": 1649576282,
"updatedOn": 1649576282,
"active": true,
"primaryProperty": "host",
"secondaryProperty": "check",
"sourceSystem": "nagios.est",
"description": "CPU is 98%",
"tags": [
{
"name": "check",
"value": "CPU"
},
{
"name": "_cluster",
"value": "modiin-prod"
},
{
"name": "run-book",
"value": "https://mywiki.com/Evyatar-11/modiin-prod"
},
{
"name": "host",
"value": "Evyatar-11"
}
]
},
{
"id": "555537133ec0020012c96a28",
"status": "Critical",
"startedOn": 1649576282,
"endedOn": null,
"changedOn": 1649576282,
"updatedOn": 1649576282,
"active": true,
"primaryProperty": "host",
"secondaryProperty": "check",
"sourceSystem": "nagios.est",
"description": "CPU is 98%",
"tags": [
{
"name": "check",
"value": "CPU"
},
{
"name": "host",
"value": "web3"
},
{
"name": "_cluster",
"value": "modiin-prod"
},
{
"name": "run-book",
"value": "https://mywiki.com/web3/modiin-prod"
}
]
}
]
},
"links": {
"landingPage": "http://bigp.io/9ad55554d5c116e4"
},
"incidentTags": [
{
"id": "itd_priority_1",
"value": 1000
}
],
"relatedChanges": [
{
"suggested_by_bigpanda": true,
On the OnLink side, the goal is to stand up an endpoint that BigPanda can call, authenticate the caller, and land the payload in the right object type. The full walkthrough lives in our BigPanda to JSM Assets documentation, but here’s the shape of it.
Open the OnLink application, go to Webhooks, and click Add.
Give the webhook a name, then select Import to Assets. Enter your Workspace ID, choose the target Asset Schema, and select the Object Type the incoming records should land in — for this example, an Incident object type in your CMDB schema.
BigPanda authenticates with basic auth, so set an auth scheme, username, and password on the webhook before you publish it. These go in the same Attributes box as the field mapping, using config: lines — we'll look at the exact syntax in the next section. These are the credentials BigPanda will present on every call, and OnLink will reject anything that doesn't match.
Publishing generates the OnLink webhook URL. That URL is what goes into BigPanda's callback configuration, along with the same username and password.
Send a test payload from BigPanda and confirm the object shows up in your Assets object type. This is the step worth being patient with — a test payload from the real source is far more informative than a hand-crafted one, because it exercises the actual field names and nesting you'll be mapping against.
Note that there's no polling schedule to configure here, and no import window to tune. The endpoint is live, and records arrive when events happen.
Mapping is where the BigPanda payload becomes an Assets object. In the webhook’s Attributes box, you declare the mapping one line at a time, using the form prefix:<source field>=<target>. Here’s the complete configuration for our BigPanda example:
key:incident.id=Incident ID
map:incident.status=status
map:incident.resolved=resolved
map:incident.alerts.0.id=alert_id
map:incident.alerts.0.status=alert_status
map:incident.alerts.0.description=alert_description
config:auth_scheme=basic_auth
config:auth_username=onlink_bigpanda
config:auth_password=enc__••••••••
If you have use cases where you want to capture events into Assets as they happen, start a free trial of OnLink on the Atlassian Marketplace.
A published OnLink URL that an outside system calls with a JSON payload when something happens. OnLink authenticates the caller, maps the payload fields to Assets attributes and creates or updates the object. No schedule, no polling.
When the time between the event and the Assets update matters: incidents, invoices, deployments, HR events such as a new hire. Use scheduled imports for full inventories where you want every record refreshed each run. Most customers run both from the same OnLink install.
With config: lines in the webhook mapping: config:auth_scheme=basic_auth with a username and password, or config:auth_scheme=header_token with a random token the source sends in a header. Unauthenticated calls are rejected.
Any system that can POST JSON to a URL with basic auth or a header token: BigPanda, Paychex, TriNet, Justworks, Ashby, Lever and HubSpot are documented examples, and Snowflake or your CI/CD pipeline work the same way.
No. The webhook lands the record in Assets by itself. You can still trigger Jira Automation rules on the resulting object or ticket if you want follow-on actions.
Event-based imports for Assets
Start a free trial of OnLink on the Atlassian Marketplace. Webhooks, scheduled imports and 100+ sources in one app.
If you have use cases where you want to capture webhook events into Assets — incidents, invoices, purchase orders, deployments, or anything else that arrives as it happens, give OnLink a try.
With webhooks to Assets:
RELATED