Documentation
Integrations
Connect Jira and ServiceNow so flows can open tickets and incidents, and keep each connection verified.
Overview
Integrations connect DeviceQuest to Jira and ServiceNow. Each connection is a connector: a name, the site or instance URL, and the account DeviceQuest signs in with. Flows use connectors in their Create ticket action to open Jira issues or ServiceNow incidents. Open the page from Admin → Integrations in the sidebar.
DeviceQuest tests every connector against the provider before you can save it, and shows on each card whether the latest test passed. You need connectors:read to see connectors and connectors:write to add, edit, test or delete them.
Screen tour
- Refresh: reloads the connectors and their test status.
- Add Connector: opens the Add Connector sheet.
Once connectors exist, a summary above the cards shows how many there are and how many are verified, failed or not verified, and each connector has its own card (see Connector cards). With no connectors yet, the page shows Connect your first tool with an Add Connector button.
Add a connector
- Name: how the connector is listed here and in the flow builder.
- Provider: Jira or ServiceNow. The fields below change with the provider.
- The site or instance URL, followed by the account and its API token or password.
- Test connection: checks the URL and credentials with the provider. The result appears next to the button.
- Save Connector: available after a successful test.
- Click Add Connector.
- Enter a Name, for example
Production Jira. - Choose the Provider.
- Fill in the connection fields (see Fields).
- Click Test connection. DeviceQuest contacts the provider and shows the result. While the test has not passed, the sheet reads “A successful connection test is required before saving.”
- When the test succeeds, click Save Connector. The message “Connector created.” appears and the new card shows Verified.
Changing the URL, the account or the credential clears the test result, so test again before you save. Click Cancel to close the sheet without saving.
Fields
Jira
| Field | Description | Rules |
|---|---|---|
| Name | The connector’s display name. | Required. |
| Jira site URL | Your Jira Cloud site, for example https://your-company.atlassian.net. | Required, for example https://…. |
| Atlassian email | The email of the Atlassian account DeviceQuest uses. | Required. |
| API token | An API token created in that Atlassian account. | Required. Stored with the connector and never shown again. |
ServiceNow
| Field | Description | Rules |
|---|---|---|
| Name | The connector’s display name. | Required. |
| ServiceNow instance URL | Your instance, for example https://instance.service-now.com. | Required, for example https://…. |
| Username | The ServiceNow account DeviceQuest uses. A dedicated integration account is recommended. | Required. |
| Password | The password of that account. | Required. Stored with the connector and never shown again. |
Connector cards
Each card shows the provider logo, the Name, the provider and the instance host, plus:
- Last verified: when the latest test ran, or Never tested.
- Created and, after a change, Updated.
- When the latest test failed, the reason the provider gave.
The card buttons are Test connection, Edit and Delete.
Statuses
| Status | Meaning | Next possible status |
|---|---|---|
| Verified | The latest test signed in to the provider successfully. | Test failed, after a test that fails |
| Test failed | The latest test failed. The card shows the reason. | Verified, after a test that passes |
| Not verified | The connector has not been tested yet. | Verified or Test failed |
Click Test connection on a card at any time to re-check it, for example after you rotate the API token in Atlassian.
Edit a connector
- Click Edit on the connector’s card. The sheet opens with the current name, provider, URL and account.
- Change what you need. The stored API token or password is kept unless you enter a new one.
- Click Test connection, and when it succeeds, click Save Connector.
Flows that use the connector pick up the change on their next run.
Delete a connector
- Click Delete on the card.
- The Delete connector? dialog says the connector will be disconnected and removed.
- Click Delete to confirm, or Cancel to keep it.
Before you delete a connector, change any flow whose Create ticket action uses it to another saved connection.