From c116873a9e6b400fe0c7fecd3394adbf4aedf556 Mon Sep 17 00:00:00 2001 From: Nadia <98525884+Nadia-JSch@users.noreply.github.com> Date: Mon, 13 Jul 2026 16:32:19 +0200 Subject: [PATCH 1/6] 60634: add-catalog-and-intro; external-integrations-index --- .../external-integrations/index.mdx | 114 +++++++++++++++++- 1 file changed, 110 insertions(+), 4 deletions(-) diff --git a/docs/integration/external-integrations/index.mdx b/docs/integration/external-integrations/index.mdx index 11720563b..1de8428e3 100644 --- a/docs/integration/external-integrations/index.mdx +++ b/docs/integration/external-integrations/index.mdx @@ -5,16 +5,122 @@ authors: - d42docadmin --- -Device42 integrates with many popular 3rd party ITSM, CM, SIEM, or IPAM tools. Use the sidebar on the left for guidance on third-party specific software integration. +This page is for administrators who want to connect Device42 to the other tools in their IT ecosystem, such as ITSM platforms, secret managers, alerting tools, and BI applications. Use it as your starting point to find the right integration and follow its dedicated setup guide. + +Device42 integrates with many popular third-party ITSM, configuration management, SIEM, and IPAM tools. Each integration keeps your infrastructure data consistent across systems, so the CMDB you build through discovery stays useful everywhere your teams work. + +## How to Use This Section + +Each integration has its own page with setup steps, prerequisites, and configuration options. Find the integration you need in the catalog below, or browse the full list in the sidebar on the left. + +Before you start, most integrations require: +- Administrator access to both Device42 and the third-party system +- Credentials or API keys for the third-party system +- Network connectivity between Device42 and the third-party system + +Check the individual integration page for its exact prerequisites. + +## Integration Catalog + +The tables below group the available integrations by purpose. + +### ITSM and Service Desk + +Sync discovered infrastructure into your service management and collaboration platforms. + +| Integration | Description | +| --- | --- | +| [ServiceNow](/integration/external-integrations/device42-servicenow-connector.mdx) | Sync IT data from Device42 to your ServiceNow CMDB. | +| [Freshservice](/integration/external-integrations/freshservice-integration/index.mdx) | Sync discovered assets and CIs into Freshservice. | +| [Jira](/integration/external-integrations/jira-integrations/index.mdx) | Connect Device42 to Jira Service Management and Jira Assets. | +| [Cherwell](/integration/external-integrations/cherwell-integration.mdx) | Sync discovered infrastructure assets and relationships into Cherwell. | +| [HP Service Manager](/integration/external-integrations/device42-hp-service-manager-integration.mdx) | Add Device42 infrastructure management capabilities to HPSM. | +| [Zendesk](/integration/external-integrations/device42-zendesk-connector.mdx) | Give your help desk access to up-to-date infrastructure documentation. | +| [Confluence](/integration/external-integrations/device42-confluence-connector.mdx) | Surface Device42 data inside your Atlassian Confluence instance. | + +### Secret and Credential Management + +Pull discovery credentials from your existing secret manager instead of storing them in Device42. + +| Integration | Description | +| --- | --- | +| [CyberArk](/integration/external-integrations/cyberark-integration.mdx) | Use CyberArk-managed credentials for discovery jobs. | +| [Delinea Secret Server](/integration/external-integrations/delinea-secret-server-integration.mdx) | Use Delinea Secret Server-managed credentials for discovery jobs. | +| [HashiCorp Vault](/integration/external-integrations/hashicorp-vault-integration.mdx) | Use HashiCorp Vault-managed credentials for discovery jobs. | +| [Microsoft LAPS](/integration/external-integrations/microsoft-laps-integration.mdx) | Pull local admin passwords from Microsoft LAPS. | + +### Alerting and Incident Management + +Route Device42 alerts to your on-call and monitoring tools. + +| Integration | Description | +| --- | --- | +| [PagerDuty](/integration/external-integrations/pagerduty-integration.mdx) | Notify on-call responders when a Device42 alert is triggered. | +| [Opsgenie](/integration/external-integrations/opsgenie-integration.mdx) | Route Device42 alerts to your incident management platform. | +| [Nagios](/integration/external-integrations/monitor-device42-health-status-in-nagios.mdx) | Monitor Device42 health status from Nagios. | + +### Logging and SIEM + +Forward Device42 audit log events to external logging platforms. + +| Integration | Description | +| --- | --- | +| [External Logging](/integration/external-integrations/external-logging-config.mdx) | Send audit log events to platforms like Splunk or Logstash. | + +### Migration + +Move data into Device42 from other DCIM or migration tools. + +| Integration | Description | +| --- | --- | +| [Aperture VISTA to Device42](/integration/external-integrations/aperture-vista-to-device42-migration.mdx) | Migrate data from Aperture VISTA into Device42. | +| [Azure Migrate](/integration/external-integrations/azure-migrate.mdx) | Work with Device42 data alongside Azure Migrate. | +| [Carbonite](/integration/external-integrations/carbonite-migration.mdx) | Migrate devices using the Device42 Carbonite Migrate feature. | + +### Configuration Management and Automation + +Connect Device42 to your automation, orchestration, and configuration management tooling. + +| Integration | Description | +| --- | --- | +| [Puppet and Chef](/integration/external-integrations/puppet-and-chef-integrations.mdx) | Sync node data between Device42 and Puppet or Chef. | +| [SaltStack](/integration/external-integrations/device42-saltstack-integration.mdx) | Integrate Device42 with the Salt configuration management engine. | +| [StackStorm](/integration/external-integrations/device42-stackstorm-integration.mdx) | Automate IT-management workflows with StackStorm. | +| [Jenkins](/integration/external-integrations/jenkins-integration.mdx) | Authenticate Jenkins jobs against Device42-managed credentials. | +| [Rundeck](/integration/external-integrations/collect-node-data-from-device42-for-rundeck.mdx) | Dynamically pull node data from the Device42 CMDB into Rundeck. | +| [Foreman](/integration/external-integrations/foreman-smart-proxy-plugin.mdx) | Integrate Device42 IPAM with the Foreman smart proxy. | +| [Zapier](/integration/external-integrations/zapier-integration.mdx) | Automate workflows using Zapier and webhooks. | +| [Webhooks](/integration/external-integrations/webhooks-generic-integration.mdx) | Trigger external actions from Device42 events. | + +### Data Access and Business Intelligence + +Query Device42 data directly from external reporting and BI tools. + +| Integration | Description | +| --- | --- | +| [JDBC Driver](/integration/external-integrations/jdbc-driver-integration.mdx) | Connect to Device42 as a JDBC data source. | +| [ODBC Driver](/integration/external-integrations/odbc-driver-integration.mdx) | Connect to Device42 as an ODBC data source. | +| [PowerBI](/integration/external-integrations/powerbi-integration.mdx) | Report on Device42 data in Microsoft PowerBI using the ODBC driver. | + +### Cloud Connector and Global Settings + +Configure how Device42 sends data to cloud-based integrations. + +| Integration | Description | +| --- | --- | +| [Cloud Connector](/integration/external-integrations/device42-cloud-connector-overview.mdx) | Send data from your Device42 appliance to external applications. | +| [Cloud Services Settings](/integration/external-integrations/cloud-services-settings.mdx) | Configure global external integration settings. | ## Download Integration Tools In addition to an extensive API library, Device42 provides connectors that make integrations easy. -**Browse & download integrations:** [https://www.device42.com/integrations/](https://www.device42.com/integrations/) +**Browse and download integrations:** [https://www.device42.com/integrations/](https://www.device42.com/integrations/) ## Tools for Custom Integrations -**Bulk Data Management Tools**: [https://www.device42.com/bulk-data-management/](https://www.device42.com/bulk-data-management/) Device42 RESTful API Documentation: [https://api.device42.com/](https://api.device42.com/) +Use the following resources to build your own integrations: -Various other useful integrations, import, sample scripts, and open source tools we've written can be found on our GitHub site: [https://github.com/device42](https://github.com/device42). +- **Bulk Data Management Tools:** [https://www.device42.com/bulk-data-management/](https://www.device42.com/bulk-data-management/) +- **Device42 RESTful API documentation:** [https://api.device42.com/](https://api.device42.com/) +- **Device42 GitHub:** [https://github.com/device42](https://github.com/device42) for other useful integrations, imports, sample scripts, and open source tools. From 86f795b0280c386a1fd4cb46a04a51c79bece40b Mon Sep 17 00:00:00 2001 From: Nadia <98525884+Nadia-JSch@users.noreply.github.com> Date: Mon, 13 Jul 2026 16:32:20 +0200 Subject: [PATCH 2/6] 60634: add-audience-intro-and-prerequisites; secret-manager-integrations --- .../cyberark-integration.mdx | 12 ++++++++++-- .../delinea-secret-server-integration.mdx | 17 ++++++++++------- .../hashicorp-vault-integration.mdx | 9 +++++++++ 3 files changed, 29 insertions(+), 9 deletions(-) diff --git a/docs/integration/external-integrations/cyberark-integration.mdx b/docs/integration/external-integrations/cyberark-integration.mdx index d8cc3bb1c..3c7691819 100644 --- a/docs/integration/external-integrations/cyberark-integration.mdx +++ b/docs/integration/external-integrations/cyberark-integration.mdx @@ -7,6 +7,8 @@ import ThemedImage from '@theme/ThemedImage' import useBaseUrl from '@docusaurus/useBaseUrl' import account from '/assets/images/cyberark-integration/create_account_for_d42_cyberark.png' +This page is for Device42 administrators who use CyberArk as their secret manager and want Device42 to retrieve discovery credentials from CyberArk instead of storing them locally. By the end, Device42 will securely look up and use CyberArk-managed credentials for your discovery jobs. + Each Device42 autodiscovery job is configured to use one or more sets of system credentials. If you already use CyberArk to manage passwords and other secrets, or simply don't want to use Device42 for this purpose, the Device42 CyberArk integration allows Device42 to securely store and retrieve these credentials externally as your primary secret management solution. CyberArk offers useful features such as automatic password rotation, which can be configured to rotate secrets per your specific corporate policies and industry guidelines. @@ -15,9 +17,15 @@ CyberArk offers useful features such as automatic password rotation, which can b Passwords retrieved from CyberArk are not viewable in Device42. ::: -## Configure CyberArk +## Prerequisites -The CyberArk AIMWebService API is needed for the integration. To use the API, purchase and install the [Central Credential Provider (CCP) plugin](https://docs.cyberark.com/credential-providers/latest/en/content/ccp/installation.htm) on CyberArk. +Before configuring the integration, make sure you have: +- Administrator access to both CyberArk and Device42 +- The CyberArk AIMWebService API available, which requires the [Central Credential Provider (CCP) plugin](https://docs.cyberark.com/credential-providers/latest/en/content/ccp/installation.htm) purchased and installed on CyberArk +- Your **CyberArk URL** and **App Id** +- Network connectivity between the Device42 appliance and CyberArk + +## Configure CyberArk **Configuring CyberArk:** diff --git a/docs/integration/external-integrations/delinea-secret-server-integration.mdx b/docs/integration/external-integrations/delinea-secret-server-integration.mdx index ac63e8cc8..89fe429ee 100644 --- a/docs/integration/external-integrations/delinea-secret-server-integration.mdx +++ b/docs/integration/external-integrations/delinea-secret-server-integration.mdx @@ -3,6 +3,8 @@ title: "Delinea Secret Server Integration" sidebar_position: 8.5 --- +This page is for Device42 administrators who use Delinea Secret Server as their secret manager and want Device42 to retrieve discovery credentials from Delinea instead of storing them locally. By the end, Device42 will securely look up and use Delinea-managed credentials for your discovery jobs. + Each Device42 Autodiscovery job is configured to use one (or more) sets of system credentials. If you already use Delinea Secret Server to manage passwords and other secrets or simply don't want to use Device42 for this purpose, the Device42 Delinea Secret Server integration allows Device42 to securely store and retrieve these credentials externally as your primary secret management solution. Delinea Secret Server offers useful features such as automatic password rotation, which can be configured to rotate secrets per your specific corporate policies and industry guidelines. @@ -11,17 +13,18 @@ Delinea Secret Server offers useful features such as automatic password rotation Please note that passwords retrieved from Delinea Secret Server are not viewable in Device42. ::: -## Configure Delinea Secret Server - -Set up a user account and folder permissions in Delinea Secret Server before connecting to Device42. +## Prerequisites -### Pre-requisites +Before configuring the integration, make sure you have: +- Administrator access to both Delinea Secret Server and Device42 +- Network connectivity between the Device42 appliance and Delinea Secret Server +- A user account in Delinea Secret Server with the **View Secret** permission, plus view access to the folders you want Secrets retrieved from -For the Delinea Secret Server integration to work, you will need to create a user account in Delinea Secret Server with the **View Secret** permission. +While you can use any user account, it is _strongly recommended_ that you use a dedicated application account for Device42. Application accounts are restricted from logging into the UI and can only be used via the API. -This user should also have view access to the desired folder(s) you would like Secrets retrieved from. +## Configure Delinea Secret Server -While you can use any user account, it is _strongly recommended_ that you use a dedicated application account for Device42. Application accounts are restricted from logging into the UI and can only be used via the API. +Set up a user account and folder permissions in Delinea Secret Server before connecting to Device42. ## Configure Device42 diff --git a/docs/integration/external-integrations/hashicorp-vault-integration.mdx b/docs/integration/external-integrations/hashicorp-vault-integration.mdx index b91e16534..46798632d 100644 --- a/docs/integration/external-integrations/hashicorp-vault-integration.mdx +++ b/docs/integration/external-integrations/hashicorp-vault-integration.mdx @@ -3,6 +3,8 @@ title: "HashiCorp Vault Integration" sidebar_position: 12.5 --- +This page is for Device42 administrators who use HashiCorp Vault as their secret manager and want Device42 to retrieve discovery credentials from Vault instead of storing them locally. By the end, Device42 will securely look up and use Vault-managed credentials for your discovery jobs. + Each Device42 autodiscovery job is configured to use one (or more) sets of system credentials. If you already use HashiCorp Vault to manage passwords and other secrets, or simply don't want to use Device42 for this purpose, the Device42 HashiCorp Vault integration allows Device42 to securely store and retrieve these credentials externally as your primary secret management solution. HashiCorp Vault offers useful features such as automatic password rotation, which can be configured to rotate secrets per your specific corporate policies and industry guidelines. @@ -11,6 +13,13 @@ HashiCorp Vault offers useful features such as automatic password rotation, whic Please note that passwords retrieved from HashiCorp Vault are not viewable in Device42. ::: +## Prerequisites + +Before configuring the integration, make sure you have: +- Administrator access to both HashiCorp Vault and Device42 +- Network connectivity between the Device42 appliance and HashiCorp Vault +- The Vault details listed under [Configuring HashiCorp Vault](#configuring-hashicorp-vault) below: an AppRole (Role ID and Secret ID) with read access to the required secret paths, the secret engine path, and the namespace if you use Multi-Tenancy + ## Configuring HashiCorp Vault - **(Required) Role ID / Secret ID:** For the HashiCorp Vault integration to work, you will need to create an AppRole in HashiCorp Vault with a policy that grants "read" to the desired Secret Paths. From 94541ebbd459ae330304090c43c629bd3cadd4eb Mon Sep 17 00:00:00 2001 From: Nadia <98525884+Nadia-JSch@users.noreply.github.com> Date: Mon, 13 Jul 2026 17:19:06 +0200 Subject: [PATCH 3/6] 60634: qa-fix-jenkins-description; external-integrations-index --- docs/integration/external-integrations/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integration/external-integrations/index.mdx b/docs/integration/external-integrations/index.mdx index 1de8428e3..37c47c2a5 100644 --- a/docs/integration/external-integrations/index.mdx +++ b/docs/integration/external-integrations/index.mdx @@ -86,7 +86,7 @@ Connect Device42 to your automation, orchestration, and configuration management | [Puppet and Chef](/integration/external-integrations/puppet-and-chef-integrations.mdx) | Sync node data between Device42 and Puppet or Chef. | | [SaltStack](/integration/external-integrations/device42-saltstack-integration.mdx) | Integrate Device42 with the Salt configuration management engine. | | [StackStorm](/integration/external-integrations/device42-stackstorm-integration.mdx) | Automate IT-management workflows with StackStorm. | -| [Jenkins](/integration/external-integrations/jenkins-integration.mdx) | Authenticate Jenkins jobs against Device42-managed credentials. | +| [Jenkins](/integration/external-integrations/jenkins-integration.mdx) | Pull Device42-stored credentials into Jenkins jobs. | | [Rundeck](/integration/external-integrations/collect-node-data-from-device42-for-rundeck.mdx) | Dynamically pull node data from the Device42 CMDB into Rundeck. | | [Foreman](/integration/external-integrations/foreman-smart-proxy-plugin.mdx) | Integrate Device42 IPAM with the Foreman smart proxy. | | [Zapier](/integration/external-integrations/zapier-integration.mdx) | Automate workflows using Zapier and webhooks. | From e7af8c4598185235f0c7f425908e169264cf6d1b Mon Sep 17 00:00:00 2001 From: Nadia <98525884+Nadia-JSch@users.noreply.github.com> Date: Tue, 14 Jul 2026 11:22:26 +0200 Subject: [PATCH 4/6] 60634: add-audience-intro-and-prerequisites; tier-1-integration-pages --- .../external-integrations/azure-migrate.mdx | 11 +++++++++++ .../external-integrations/cherwell-integration.mdx | 10 +++++++++- .../device42-confluence-connector.mdx | 9 +++++++++ .../device42-stackstorm-integration.mdx | 9 +++++++++ .../device42-zendesk-connector.mdx | 11 ++++++++++- .../external-integrations/jenkins-integration.mdx | 9 +++++++++ .../external-integrations/opsgenie-integration.mdx | 9 +++++++++ .../external-integrations/zapier-integration.mdx | 9 +++++++++ 8 files changed, 75 insertions(+), 2 deletions(-) diff --git a/docs/integration/external-integrations/azure-migrate.mdx b/docs/integration/external-integrations/azure-migrate.mdx index 9ab4502ec..3f1e9a3e2 100644 --- a/docs/integration/external-integrations/azure-migrate.mdx +++ b/docs/integration/external-integrations/azure-migrate.mdx @@ -3,8 +3,19 @@ title: "Azure Migrate" sidebar_position: 2 --- +This page is for administrators who want to use Device42 as an assessment tool within Azure Migrate and export discovered business applications from Device42 to Azure for migration planning. By the end, your Device42 business application data appears in the Azure Migrate portal for assessment. + You can get to Azure Migrate directly @ [https://portal.azure.com/#create/Microsoft.AzureMigrate](https://portal.azure.com/#create/Microsoft.AzureMigrate) +## Prerequisites + +To export data from Device42 to Azure Migrate, make sure you have: +- An Azure account with access to the Azure portal +- An Azure Migrate project (created in the [Setting up Device42 from the Azure Migrate Portal](#setting-up-device42-from-the-azure-migrate-portal) section below) +- An Azure Active Directory app registration with a client secret, assigned the **Contributor** role on the subscription +- The following details collected from Azure: **Tenant ID**, **Subscription ID**, **Client ID**, **Client Secret**, and the **Migrate Project Name** +- A running Device42 instance with business applications to export + ## Setting up Device42 from the Azure Migrate Portal 1\. Begin by signing up for an Azure account if you don’t already have one. You’ll have to provide a credit card to verify your identity, and agree to the conditions to continue: diff --git a/docs/integration/external-integrations/cherwell-integration.mdx b/docs/integration/external-integrations/cherwell-integration.mdx index f5c5849a6..b23b8097b 100644 --- a/docs/integration/external-integrations/cherwell-integration.mdx +++ b/docs/integration/external-integrations/cherwell-integration.mdx @@ -3,9 +3,17 @@ title: "Cherwell Integration" sidebar_position: 4 --- +This page is for administrators who want to keep their Cherwell CMDB in sync with the infrastructure Device42 discovers. By the end, discovered assets and configuration items (CIs) from Device42 are synced into Cherwell, either once or on a schedule. + Use the [Device42-Cherwell integration](https://www.device42.com/integrations/cherwell) to sync discovered infrastructure assets and configuration items (CIs) from Device42 to your Cherwell CMDB. -The Device42-Cherwell integration requires a working Cherwell installation, Device42 instance, and assumes a Linux server with Python version 3.5 or later. +## Prerequisites + +Before configuring the integration, make sure you have: +- A working Cherwell installation, with administrator access to Cherwell Service Management Administrator +- A running Device42 instance +- A Linux server with Python version 3.5 or later to run the integration script +- Network connectivity between the Linux server, Cherwell, and Device42 ## Configuring Cherwell diff --git a/docs/integration/external-integrations/device42-confluence-connector.mdx b/docs/integration/external-integrations/device42-confluence-connector.mdx index 48eaa13b4..79d93cd2a 100644 --- a/docs/integration/external-integrations/device42-confluence-connector.mdx +++ b/docs/integration/external-integrations/device42-confluence-connector.mdx @@ -3,6 +3,8 @@ title: "Confluence Integration" sidebar_position: 7 --- +This page is for Confluence administrators who want to surface Device42 infrastructure data inside their Atlassian Confluence instance. By the end, you can display and link to Device42 objects within Confluence pages and keep that data synchronized. + This integration connects Device42 to your Atlassian Confluence instance with the following features: - Display details of particular Device42 object (devices, racks, PDUs and parts are supported). @@ -11,6 +13,13 @@ This integration connects Device42 to your Atlassian Confluence instance with th - Synchronize Device42 data with Confluence manually or periodically. - Filter set of Device42 CIs to display inside macros for specific space. +## Prerequisites + +Before installing the add-on, make sure you have: +- A Confluence user with the **Confluence System Administrators** global permission to install the add-on, and **Confluence Administrators** permission to configure it +- A running Device42 instance +- A stable network connection between the server hosting Confluence and the server hosting Device42 + ## Install the Confluence Integration Add-On Device42's Atlassian Confluence add-on (aka "Device42 CMDB Connector for Confluence") can be found [in the Atlassian Marketplace](https://marketplace.atlassian.com/apps/1213754/device42-cmdb-connector-for-confluence?hosting=server&tab=overview). You can easily install it using the UPM (Universal Plugin Manager) built in to Confluence. However, if you have some special requirements (e.g. an environment that blocks Confluence from access to the internet), it is possible to install the Device42 Confluence integration plugin manually. Please note that the plugin requires a stable connection between the servers hosting your Confluence application and that which is hosting Device42 for successful operation. diff --git a/docs/integration/external-integrations/device42-stackstorm-integration.mdx b/docs/integration/external-integrations/device42-stackstorm-integration.mdx index a86f9dc93..3145a0a07 100644 --- a/docs/integration/external-integrations/device42-stackstorm-integration.mdx +++ b/docs/integration/external-integrations/device42-stackstorm-integration.mdx @@ -6,8 +6,17 @@ sidebar_position: 28.5 import ThemedImage from '@theme/ThemedImage' import useBaseUrl from '@docusaurus/useBaseUrl' +This page is for automation engineers who want to drive Device42 actions from StackStorm workflows. By the end, StackStorm can query and update Device42 in response to trigger events, using the Device42 integration plugin. + [StackStorm](https://docs.stackstorm.com/overview.html#about) is well suited to automate a range of IT-management workflows. In response to a trigger event, you can get the StackStorm-Device42 integration to update device details, set user permissions, send Device42 data to other systems, and more. +## Prerequisites + +Before setting up the integration, make sure you have: +- A StackStorm instance. This guide runs StackStorm in a [Docker](https://docs.docker.com/get-docker/) container managed with [Docker Compose](https://docs.docker.com/compose/install/), which is suitable for testing but not production. See the [StackStorm installation options](https://docs.stackstorm.com/install/index.html) for production installs. +- A running Device42 instance, with Device42 credentials to configure the integration plugin +- Network connectivity between StackStorm and Device42 + ## Set Up the Integration The steps for setting up the StackStorm integration are: diff --git a/docs/integration/external-integrations/device42-zendesk-connector.mdx b/docs/integration/external-integrations/device42-zendesk-connector.mdx index 455d5a2ee..104d6a91f 100644 --- a/docs/integration/external-integrations/device42-zendesk-connector.mdx +++ b/docs/integration/external-integrations/device42-zendesk-connector.mdx @@ -6,8 +6,17 @@ sidebar_position: 30 import ThemedImage from '@theme/ThemedImage' import useBaseUrl from '@docusaurus/useBaseUrl' +This page is for administrators who want to give their Zendesk help desk access to Device42 infrastructure data through support tickets. By the end, you can link Device42 CIs to Zendesk tickets and view Device42 infrastructure details from within Zendesk. + Device42 discovery keeps your infrastructure documentation up-to-date, and with the Zendesk connector, your help desk can access IT infrastructure information via support tickets. +## Prerequisites + +Before setting up the integration, make sure you have: +- Administrator access to both Zendesk and Device42 +- Your [Device42 Cloud Connector](/integration/external-integrations/device42-cloud-connector-overview.mdx) configured (under **Tools > Integrations > Cloud Services**) to allow communication between Device42 and Zendesk +- A Zendesk API token, created as described in [Create a Zendesk API Token](#create-a-zendesk-api-token) below + ## Benefits of the Device42-Zendesk Integration With the Device42-Zendesk integration, you'll benefit from the ability to: @@ -21,7 +30,7 @@ With the Device42-Zendesk integration, you'll benefit from the ability to: Before creating an External Integration in Device42 and installing the integration plugin in Zendesk, you need to create a Zendesk API Token. -As a prerequisite, ensure your [Device42 Cloud Connector](integration/external-integrations/device42-cloud-connector-overview.mdx) is configured (under **Tools > Integrations > Cloud Services**) to allow communication between Device42 and Zendesk. +As a prerequisite, ensure your [Device42 Cloud Connector](/integration/external-integrations/device42-cloud-connector-overview.mdx) is configured (under **Tools > Integrations > Cloud Services**) to allow communication between Device42 and Zendesk. ### Create a Zendesk API Token diff --git a/docs/integration/external-integrations/jenkins-integration.mdx b/docs/integration/external-integrations/jenkins-integration.mdx index 5b1aad6e9..2705c01de 100644 --- a/docs/integration/external-integrations/jenkins-integration.mdx +++ b/docs/integration/external-integrations/jenkins-integration.mdx @@ -3,6 +3,8 @@ title: "Jenkins Integration" sidebar_position: 14 --- +This page is for administrators who want their Jenkins automation jobs to pull credentials from Device42's built-in secret store instead of storing them in Jenkins or in scripts. By the end, Jenkins jobs can reference Device42-stored secrets as variables, retrieved through the Device42 API at run time. + If you use Jenkins, the popular open-source automation server, it's likely your automated jobs authenticate against one or more local and/or remote systems as part of their tasks. The Device42/Jenkins integration allows Device42 to securely store & retrieve these credentials within Device42, which boasts a robust built-in secret/password management solution. Instead of trying to store new or existing credentials in your automation scripts, or in Jenkins in addition to countless other locations, leverage the centralized secret store in Device42. Simply add or update a secret/password in Device42, and with the Jenkins integration, your automation instantly has access to the updated credentials. Forget manual credentials updates across your infrastructure! @@ -11,6 +13,13 @@ If you like this integration, check out the [Device42 integration page](https://   +## Prerequisites + +Before installing the integration, make sure you have: +- A Jenkins instance with administrator access to upload and manage plugins +- A running Device42 Main Appliance with its API accessible from Jenkins +- The Device42 Jenkins plugin (`Device42.hpi`), either [downloaded](https://github.com/device42/device42-jenkins-credentials-plugin/) or built from source (building from source requires **Maven**) + ## Installing the Device42-Jenkins Integration ![Jenkins](/assets/images/Jenkins-logo-butler-transparent.png) diff --git a/docs/integration/external-integrations/opsgenie-integration.mdx b/docs/integration/external-integrations/opsgenie-integration.mdx index 6075cfe81..6f0436d6e 100644 --- a/docs/integration/external-integrations/opsgenie-integration.mdx +++ b/docs/integration/external-integrations/opsgenie-integration.mdx @@ -3,8 +3,17 @@ title: "Opsgenie Integration" sidebar_position: 22 --- +This page is for administrators who want Device42 alerts to reach their on-call responders in Opsgenie. By the end, a triggered Device42 alert is automatically routed to Opsgenie as an incident. + Device42 integrates with Opsgenie to automatically route alerts to your incident management platform. This page explains how to configure the integration and set up alert forwarding. +## Prerequisites + +Before setting up the integration, make sure you have: +- Access to Opsgenie **Settings** to add an API integration +- An Opsgenie API key with the **Create and Update Access** option enabled +- Administrator access to Device42 to add an external integration and configure alerts + ## Set Up an API Key in Opsgenie - Click **Settings** in the Opsgenie top navigation bar. diff --git a/docs/integration/external-integrations/zapier-integration.mdx b/docs/integration/external-integrations/zapier-integration.mdx index 99c5dbed3..221613166 100644 --- a/docs/integration/external-integrations/zapier-integration.mdx +++ b/docs/integration/external-integrations/zapier-integration.mdx @@ -6,6 +6,8 @@ sidebar_position: 29 import ThemedImage from '@theme/ThemedImage' import useBaseUrl from '@docusaurus/useBaseUrl' +This page is for administrators who want to trigger automated actions in other apps whenever a Device42 resource changes. By the end, a change in Device42 fires a webhook that runs a Zapier "Zap" in the app of your choice. This example creates a Google Sheets row each time a device is added. + [Zapier](https://zapier.com/) is a versatile workflow automation tool based on "if-this-then-that" logic. You can create an automation sequence, known as a "Zap", to perform actions in response to changes made to Device42 resources. Zapier supports response actions using features of a [variety of apps](https://zapier.com/apps), including Jira, MySQL Server, and Google products. In this example, we'll have Zapier create a new row in a Google spreadsheet of the webhook payload whenever a new device is added to the Device42 main appliance. The process consists of the following broad steps: @@ -15,6 +17,13 @@ In this example, we'll have Zapier create a new row in a Google spreadsheet of t - Configure the Zapier response action. - Test the automation. +## Prerequisites + +Before creating the Zap, make sure you have: +- A Zapier account +- A Device42 main appliance with access to the webhooks feature (**Tools > Webhooks**) +- An account for the app you want Zapier to act on (this example uses Google Sheets) + ## Generate the Zapier Endpoint 1. Log in to your Zapier account and click on the **+ Create Zap** button. From 4dcabb36a215808d8f08a54bcbf68470f9605e63 Mon Sep 17 00:00:00 2001 From: Nadia <98525884+Nadia-JSch@users.noreply.github.com> Date: Tue, 14 Jul 2026 17:28:15 +0200 Subject: [PATCH 5/6] 60634: link-format-no-leading-slash; external-integrations --- .../external-integrations/azure-migrate.mdx | 2 +- .../device42-zendesk-connector.mdx | 4 +- .../external-integrations/index.mdx | 62 +++++++++---------- 3 files changed, 34 insertions(+), 34 deletions(-) diff --git a/docs/integration/external-integrations/azure-migrate.mdx b/docs/integration/external-integrations/azure-migrate.mdx index 3f1e9a3e2..067fb8190 100644 --- a/docs/integration/external-integrations/azure-migrate.mdx +++ b/docs/integration/external-integrations/azure-migrate.mdx @@ -70,7 +70,7 @@ You’ll see confirmation the deployment has been initialized. For help installing Device42, head over to the Device42 documentation: [https://docs.device42.com](https://docs.device42.com). 1. The [Getting Started with Installation section is a great place to begin! [installation](getstarted/deploy-device42/index.mdx). -2\. Once you’ve installed, you’ll want to begin discovering your environment. See the “Getting started with autodiscovery” section of the documentation here: [getstarted/getting-started-with-auto-discovery.mdx](/getstarted/getting-started-with-auto-discovery.mdx). +2\. Once you’ve installed, you’ll want to begin discovering your environment. See the “Getting started with autodiscovery” section of the documentation here: [getstarted/getting-started-with-auto-discovery.mdx](getstarted/getting-started-with-auto-discovery.mdx). 3\. When you’ve finished with discovery and assessment, you can export your discovered data back to Microsoft Azure. Instructions on exporting can be found here: [applications/business-services/building-business-services-in-device42.md#section-15](apps/business-services/building-business-services-in-device42.mdx#section-15). diff --git a/docs/integration/external-integrations/device42-zendesk-connector.mdx b/docs/integration/external-integrations/device42-zendesk-connector.mdx index 104d6a91f..fe84361f6 100644 --- a/docs/integration/external-integrations/device42-zendesk-connector.mdx +++ b/docs/integration/external-integrations/device42-zendesk-connector.mdx @@ -14,7 +14,7 @@ Device42 discovery keeps your infrastructure documentation up-to-date, and with Before setting up the integration, make sure you have: - Administrator access to both Zendesk and Device42 -- Your [Device42 Cloud Connector](/integration/external-integrations/device42-cloud-connector-overview.mdx) configured (under **Tools > Integrations > Cloud Services**) to allow communication between Device42 and Zendesk +- Your [Device42 Cloud Connector](integration/external-integrations/device42-cloud-connector-overview.mdx) configured (under **Tools > Integrations > Cloud Services**) to allow communication between Device42 and Zendesk - A Zendesk API token, created as described in [Create a Zendesk API Token](#create-a-zendesk-api-token) below ## Benefits of the Device42-Zendesk Integration @@ -30,7 +30,7 @@ With the Device42-Zendesk integration, you'll benefit from the ability to: Before creating an External Integration in Device42 and installing the integration plugin in Zendesk, you need to create a Zendesk API Token. -As a prerequisite, ensure your [Device42 Cloud Connector](/integration/external-integrations/device42-cloud-connector-overview.mdx) is configured (under **Tools > Integrations > Cloud Services**) to allow communication between Device42 and Zendesk. +As a prerequisite, ensure your [Device42 Cloud Connector](integration/external-integrations/device42-cloud-connector-overview.mdx) is configured (under **Tools > Integrations > Cloud Services**) to allow communication between Device42 and Zendesk. ### Create a Zendesk API Token diff --git a/docs/integration/external-integrations/index.mdx b/docs/integration/external-integrations/index.mdx index 37c47c2a5..7c125de42 100644 --- a/docs/integration/external-integrations/index.mdx +++ b/docs/integration/external-integrations/index.mdx @@ -30,13 +30,13 @@ Sync discovered infrastructure into your service management and collaboration pl | Integration | Description | | --- | --- | -| [ServiceNow](/integration/external-integrations/device42-servicenow-connector.mdx) | Sync IT data from Device42 to your ServiceNow CMDB. | -| [Freshservice](/integration/external-integrations/freshservice-integration/index.mdx) | Sync discovered assets and CIs into Freshservice. | -| [Jira](/integration/external-integrations/jira-integrations/index.mdx) | Connect Device42 to Jira Service Management and Jira Assets. | -| [Cherwell](/integration/external-integrations/cherwell-integration.mdx) | Sync discovered infrastructure assets and relationships into Cherwell. | -| [HP Service Manager](/integration/external-integrations/device42-hp-service-manager-integration.mdx) | Add Device42 infrastructure management capabilities to HPSM. | -| [Zendesk](/integration/external-integrations/device42-zendesk-connector.mdx) | Give your help desk access to up-to-date infrastructure documentation. | -| [Confluence](/integration/external-integrations/device42-confluence-connector.mdx) | Surface Device42 data inside your Atlassian Confluence instance. | +| [ServiceNow](integration/external-integrations/device42-servicenow-connector.mdx) | Sync IT data from Device42 to your ServiceNow CMDB. | +| [Freshservice](integration/external-integrations/freshservice-integration/index.mdx) | Sync discovered assets and CIs into Freshservice. | +| [Jira](integration/external-integrations/jira-integrations/index.mdx) | Connect Device42 to Jira Service Management and Jira Assets. | +| [Cherwell](integration/external-integrations/cherwell-integration.mdx) | Sync discovered infrastructure assets and relationships into Cherwell. | +| [HP Service Manager](integration/external-integrations/device42-hp-service-manager-integration.mdx) | Add Device42 infrastructure management capabilities to HPSM. | +| [Zendesk](integration/external-integrations/device42-zendesk-connector.mdx) | Give your help desk access to up-to-date infrastructure documentation. | +| [Confluence](integration/external-integrations/device42-confluence-connector.mdx) | Surface Device42 data inside your Atlassian Confluence instance. | ### Secret and Credential Management @@ -44,10 +44,10 @@ Pull discovery credentials from your existing secret manager instead of storing | Integration | Description | | --- | --- | -| [CyberArk](/integration/external-integrations/cyberark-integration.mdx) | Use CyberArk-managed credentials for discovery jobs. | -| [Delinea Secret Server](/integration/external-integrations/delinea-secret-server-integration.mdx) | Use Delinea Secret Server-managed credentials for discovery jobs. | -| [HashiCorp Vault](/integration/external-integrations/hashicorp-vault-integration.mdx) | Use HashiCorp Vault-managed credentials for discovery jobs. | -| [Microsoft LAPS](/integration/external-integrations/microsoft-laps-integration.mdx) | Pull local admin passwords from Microsoft LAPS. | +| [CyberArk](integration/external-integrations/cyberark-integration.mdx) | Use CyberArk-managed credentials for discovery jobs. | +| [Delinea Secret Server](integration/external-integrations/delinea-secret-server-integration.mdx) | Use Delinea Secret Server-managed credentials for discovery jobs. | +| [HashiCorp Vault](integration/external-integrations/hashicorp-vault-integration.mdx) | Use HashiCorp Vault-managed credentials for discovery jobs. | +| [Microsoft LAPS](integration/external-integrations/microsoft-laps-integration.mdx) | Pull local admin passwords from Microsoft LAPS. | ### Alerting and Incident Management @@ -55,9 +55,9 @@ Route Device42 alerts to your on-call and monitoring tools. | Integration | Description | | --- | --- | -| [PagerDuty](/integration/external-integrations/pagerduty-integration.mdx) | Notify on-call responders when a Device42 alert is triggered. | -| [Opsgenie](/integration/external-integrations/opsgenie-integration.mdx) | Route Device42 alerts to your incident management platform. | -| [Nagios](/integration/external-integrations/monitor-device42-health-status-in-nagios.mdx) | Monitor Device42 health status from Nagios. | +| [PagerDuty](integration/external-integrations/pagerduty-integration.mdx) | Notify on-call responders when a Device42 alert is triggered. | +| [Opsgenie](integration/external-integrations/opsgenie-integration.mdx) | Route Device42 alerts to your incident management platform. | +| [Nagios](integration/external-integrations/monitor-device42-health-status-in-nagios.mdx) | Monitor Device42 health status from Nagios. | ### Logging and SIEM @@ -65,7 +65,7 @@ Forward Device42 audit log events to external logging platforms. | Integration | Description | | --- | --- | -| [External Logging](/integration/external-integrations/external-logging-config.mdx) | Send audit log events to platforms like Splunk or Logstash. | +| [External Logging](integration/external-integrations/external-logging-config.mdx) | Send audit log events to platforms like Splunk or Logstash. | ### Migration @@ -73,9 +73,9 @@ Move data into Device42 from other DCIM or migration tools. | Integration | Description | | --- | --- | -| [Aperture VISTA to Device42](/integration/external-integrations/aperture-vista-to-device42-migration.mdx) | Migrate data from Aperture VISTA into Device42. | -| [Azure Migrate](/integration/external-integrations/azure-migrate.mdx) | Work with Device42 data alongside Azure Migrate. | -| [Carbonite](/integration/external-integrations/carbonite-migration.mdx) | Migrate devices using the Device42 Carbonite Migrate feature. | +| [Aperture VISTA to Device42](integration/external-integrations/aperture-vista-to-device42-migration.mdx) | Migrate data from Aperture VISTA into Device42. | +| [Azure Migrate](integration/external-integrations/azure-migrate.mdx) | Work with Device42 data alongside Azure Migrate. | +| [Carbonite](integration/external-integrations/carbonite-migration.mdx) | Migrate devices using the Device42 Carbonite Migrate feature. | ### Configuration Management and Automation @@ -83,14 +83,14 @@ Connect Device42 to your automation, orchestration, and configuration management | Integration | Description | | --- | --- | -| [Puppet and Chef](/integration/external-integrations/puppet-and-chef-integrations.mdx) | Sync node data between Device42 and Puppet or Chef. | -| [SaltStack](/integration/external-integrations/device42-saltstack-integration.mdx) | Integrate Device42 with the Salt configuration management engine. | -| [StackStorm](/integration/external-integrations/device42-stackstorm-integration.mdx) | Automate IT-management workflows with StackStorm. | -| [Jenkins](/integration/external-integrations/jenkins-integration.mdx) | Pull Device42-stored credentials into Jenkins jobs. | -| [Rundeck](/integration/external-integrations/collect-node-data-from-device42-for-rundeck.mdx) | Dynamically pull node data from the Device42 CMDB into Rundeck. | -| [Foreman](/integration/external-integrations/foreman-smart-proxy-plugin.mdx) | Integrate Device42 IPAM with the Foreman smart proxy. | -| [Zapier](/integration/external-integrations/zapier-integration.mdx) | Automate workflows using Zapier and webhooks. | -| [Webhooks](/integration/external-integrations/webhooks-generic-integration.mdx) | Trigger external actions from Device42 events. | +| [Puppet and Chef](integration/external-integrations/puppet-and-chef-integrations.mdx) | Sync node data between Device42 and Puppet or Chef. | +| [SaltStack](integration/external-integrations/device42-saltstack-integration.mdx) | Integrate Device42 with the Salt configuration management engine. | +| [StackStorm](integration/external-integrations/device42-stackstorm-integration.mdx) | Automate IT-management workflows with StackStorm. | +| [Jenkins](integration/external-integrations/jenkins-integration.mdx) | Pull Device42-stored credentials into Jenkins jobs. | +| [Rundeck](integration/external-integrations/collect-node-data-from-device42-for-rundeck.mdx) | Dynamically pull node data from the Device42 CMDB into Rundeck. | +| [Foreman](integration/external-integrations/foreman-smart-proxy-plugin.mdx) | Integrate Device42 IPAM with the Foreman smart proxy. | +| [Zapier](integration/external-integrations/zapier-integration.mdx) | Automate workflows using Zapier and webhooks. | +| [Webhooks](integration/external-integrations/webhooks-generic-integration.mdx) | Trigger external actions from Device42 events. | ### Data Access and Business Intelligence @@ -98,9 +98,9 @@ Query Device42 data directly from external reporting and BI tools. | Integration | Description | | --- | --- | -| [JDBC Driver](/integration/external-integrations/jdbc-driver-integration.mdx) | Connect to Device42 as a JDBC data source. | -| [ODBC Driver](/integration/external-integrations/odbc-driver-integration.mdx) | Connect to Device42 as an ODBC data source. | -| [PowerBI](/integration/external-integrations/powerbi-integration.mdx) | Report on Device42 data in Microsoft PowerBI using the ODBC driver. | +| [JDBC Driver](integration/external-integrations/jdbc-driver-integration.mdx) | Connect to Device42 as a JDBC data source. | +| [ODBC Driver](integration/external-integrations/odbc-driver-integration.mdx) | Connect to Device42 as an ODBC data source. | +| [PowerBI](integration/external-integrations/powerbi-integration.mdx) | Report on Device42 data in Microsoft PowerBI using the ODBC driver. | ### Cloud Connector and Global Settings @@ -108,8 +108,8 @@ Configure how Device42 sends data to cloud-based integrations. | Integration | Description | | --- | --- | -| [Cloud Connector](/integration/external-integrations/device42-cloud-connector-overview.mdx) | Send data from your Device42 appliance to external applications. | -| [Cloud Services Settings](/integration/external-integrations/cloud-services-settings.mdx) | Configure global external integration settings. | +| [Cloud Connector](integration/external-integrations/device42-cloud-connector-overview.mdx) | Send data from your Device42 appliance to external applications. | +| [Cloud Services Settings](integration/external-integrations/cloud-services-settings.mdx) | Configure global external integration settings. | ## Download Integration Tools From 3af630c69ec26a5cdfd9ba1116c7071654a923ae Mon Sep 17 00:00:00 2001 From: Nadia <98525884+Nadia-JSch@users.noreply.github.com> Date: Tue, 14 Jul 2026 17:58:30 +0200 Subject: [PATCH 6/6] 60634: qa-soften-zendesk-prerequisite; zendesk-integration --- .../external-integrations/device42-zendesk-connector.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integration/external-integrations/device42-zendesk-connector.mdx b/docs/integration/external-integrations/device42-zendesk-connector.mdx index fe84361f6..62e1d9f6a 100644 --- a/docs/integration/external-integrations/device42-zendesk-connector.mdx +++ b/docs/integration/external-integrations/device42-zendesk-connector.mdx @@ -13,7 +13,7 @@ Device42 discovery keeps your infrastructure documentation up-to-date, and with ## Prerequisites Before setting up the integration, make sure you have: -- Administrator access to both Zendesk and Device42 +- Access to Zendesk and Device42 to configure the integration - Your [Device42 Cloud Connector](integration/external-integrations/device42-cloud-connector-overview.mdx) configured (under **Tools > Integrations > Cloud Services**) to allow communication between Device42 and Zendesk - A Zendesk API token, created as described in [Create a Zendesk API Token](#create-a-zendesk-api-token) below