> This page is for Developers.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.emnify.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.emnify.com/_mcp/server.

# Troubleshoot device connectivity in Jira Service Desk

> Create automations to help your team troubleshoot device connectivity in Jira Service Desk using the emnify REST API

In this guide, you'll learn how to create automations in Jira Service Desk to help your team troubleshoot device connectivity using the emnify REST API.
You'll create three automations:

* [**Fetch current device and SIM statuses**](#create-an-automation-to-fetch-current-device-and-sim-statuses) - Retrieve the current status of the device and SIM card associated with the issue and add a comment.
* [**Reset connectivity**](#create-a-manual-trigger-to-reset-connectivity) - Reset the device's connectivity and comment on the issue.
* [**Get connectivity status**](#create-a-manual-trigger-to-get-the-connectivity-status) - Fetch the current connectivity status of the device and comment on the issue.

## Prerequisites

Before you start, make sure you have the following:

* A [Jira Service Desk account](https://www.atlassian.com/software/jira/service-management/features/service-desk)
* An [emnify account](/quickstart) with at least one device and assigned SIM
* A valid application token associated with your emnify Workspace.
  You can create a new application token in the [emnify Portal](/portal/application-tokens) or the [emnify REST API](/developers/auth/application-tokens).

You also need a custom field for your SIM identifier in your Jira Service Desk project.
To create this field, follow the instructions in the next section.

### Create a custom field for your SIM identifier

All of the automations in this guide rely on a SIM identifier to retrieve data from the emnify REST API.
To access the identifier in Jira Service Desk, create a custom field.

Your team should be familiar with this identifier and use it commonly.
It also needs to be a value available for filtering in the [List Endpoints](/developers/api/endpoint/get-endpoints) API call.

> **Info**
>
> Devices are called "endpoints" in the emnify REST API.

For example, you can use:

* [eUICC Identifier (EID)](https://www.emnify.com/iot-glossary#eid)
* [Integrated Circuit Card Identifier (ICCID)](https://www.emnify.com/iot-glossary#iccid) with or without the final [Luhn checksum digit](https://www.emnify.com/iot-glossary#luhn-checksum-digit)
* [International Mobile Equipment Identity (IMEI)](https://www.emnify.com/iot-glossary#imei)

> **Note**
>
> This guide uses the **ICCID** without the final Luhn checksum digit.

Follow the [Atlassian Support documentation to create a new custom field](https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/) named **ICCID**.
Choose **Short text (plain text only)** for the field type instead of **Number**, as punctuation can cause issues in subsequent API calls.

Describe the field so that your team knows what it's used for.
The following is an example description for the ICCID field that includes links to the emnify glossary:

```txt wordWrap
[Integrated circuit card identifier (ICCID)|https://www.emnify.com/iot-glossary#iccid], a 19-digit code used to identify a SIM card. This value doesn't include the final [Luhn check digit|https://www.emnify.com/iot-glossary#luhn-checksum-digit].
```

Finally, [configure the issue view](https://support.atlassian.com/jira-software-cloud/docs/configure-field-layout-in-the-issue-view/) so the custom field is visible on your issues.

![ICCID custom field as a text box with the ICCID description below it](/_fern-img/66f7e3a14c3176b38082fce9a5ab64ee83211a9038cc987389e253fbbef77cf4.webp)

## Create an automation to fetch current device and SIM statuses

[Automation rules in Jira](https://support.atlassian.com/cloud-automation/docs/create-and-edit-jira-automation-rules/) allow you to perform actions based on specific triggers and set criteria.
To help your team understand the condition of a device and SIM card, you can create an automation rule that fetches the current statuses from the emnify REST API and adds a comment to the issue.

### Step 1: Set up the trigger and conditions \[#step-1-set-up-triggers-fetch-statuses]

To start, choose a [trigger](https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/) that initiates the automation and determines when the rule is run.
In this case, the rule should run when an issue is created or updated.
This guide uses the **Issue created** trigger.

You also want to set up a [condition](https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/) for each automation to ensure the rule only runs when the required SIM identifier is present.

In your Jira Service Desk project, navigate to **Project settings** > **Automation**.

Select **Create rule**.

Add the **Issue created** trigger.

Add the **Issue fields condition** and set the condition to `ICCID is not empty`.

### Step 2: Generate an authentication token for the emnify REST API \[#step-2-generate-auth-token-fetch-statuses]

Next, you need an [action](https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/) to execute when your rule is triggered and the condition passes successfully.
The first action uses your application token and the [Retrieve Authentication Token](/developers/api/authentication/authenticate) call to generate a JSON Web Token (JWT) `auth_token` that authenticates further requests to the emnify REST API.

> **Note**
>
> This API path has a rate limit of 100 requests per IP in a 5-minute window.
> For more information, see [Rate limits](/developers/api-guidelines/rate-limits).

Add the **Send web request** action and configure the fields as follows:

* **Web request URL** - `https://cdn.emnify.net/api/v1/authenticate`

* **HTTP method** - POST

* **Web request body** - Select **Custom data** then add the following JSON payload:

  ```json
  {
    "application_token": "YOUR_APPLICATION_TOKEN"
  }
  ```

* Select **Delay execution of subsequent rule actions until we've received a response for this web request**.
  Alternatively, you can continue running the rule and set up error handling.

* **Headers** - Insert `Content-Type` as a **Key** and add `application/json` as the respective **Value**.

The response contains the `auth_token` you'll use to authenticate further requests.
See [Retrieve Authentication Token](/developers/api/authentication/authenticate) in the emnify documentation for more details about the response structure and examples.

Because this automation requires multiple calls to the emnify REST API, you also need to store the `auth_token` as a variable.
Creating a variable saves a smart value as a semantic name that you can use in other actions or conditions within this rule.

Add a **Create variable** action, then configure the fields as follows:

* **Variable name** - `authToken`
* **Smart value** - `{{webhookResponse.body.auth_token}}`

The authentication token is now stored in the `{{authToken}}` variable for future use.

### Step 3: Use the emnify REST API to get the device details \[#step-3-device-details-fetch-statuses]

After generating your authentication token, you need to determine which device your SIM card is assigned to in the emnify platform.
You can figure this out with the [List Endpoints](/developers/api/endpoint/get-endpoints) API call and use the ICCID value to filter the results.

To filter the results, use the `q` query parameter in the `<field>:<criteria>` format.
The request parameters in Jira automations must be URL-encoded using [smart values](https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/).
Because you previously set a condition to ensure the custom ICCID field isn't empty, you can use the smart value `{{issue.ICCID}}`.

Add a **Send web request** action and configure the fields as follows:

* **Web request URL** - `https://cdn.emnify.net/api/v1/endpoint?q=iccid:{{issue.ICCID}}`
* **HTTP method** - GET
* **Web request body** - Empty, as the URL handles the filtering.
* Select **Delay execution of subsequent rule actions until we've received a response for this web request**.
  Alternatively, you can continue running the rule and set up error handling.
* **Headers** - Insert `Content-Type` and `Authorization` as **Keys** and add the respective **Values** `application/json` and `Bearer {{authToken}}`.
  Make sure there's a non-breaking space between `Bearer` and `{{authToken}}`.

The response contains device information that you'll use in subsequent actions.
See [List Endpoints](/developers/api/endpoint/get-endpoints) in the emnify documentation for more details about the response structure and examples.

### Step 4: Comment on the issue with the device and SIM status

Once you have the corresponding device details, you can use the [`{{webhookResponse}}` smart values](https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/) to write a comment on the issue.

1. Add a **Comment on issue** action.
2. Write a comment referencing the device and SIM status from the response of the previous web request.
3. Select **Prevent duplicates by only adding this comment once to a particular issue**.
   You want to add the comment only once per issue.
4. Select the **Comment Visibility** (either **Internal only** or **Share with customer**).

The following is an example comment that includes links to the relevant documentation:

```txt wordWrap
Device "{{webhookResponse.body.name}}" (ID: {{webhookResponse.body.id}}) is *{{webhookResponse.body.status.description}}* and the attached SIM (ID: {{webhookResponse.body.sim.id}}) is in the [*{{webhookResponse.body.sim.status.description}}*|https://docs.emnify.com/services/sim-lifecycle-management#sim-states] state.
```

### Step 5: Use the emnify REST API to get the connectivity status

Now that you know the device ID, you can pull the current connectivity status of the device using the [Endpoint Connectivity Status](/developers/api/endpoint/endpoint-connectivity-by-id-get) API call.

> **Info**
>
> Instead of using an issue value in the web request URL (for example, `{{issue.ICCID}}`), you want to use data from the previous web request's response.

Add a **Send web request** action, then configure the fields as follows:

* **Web request URL** - `https://cdn.emnify.net/api/v1/endpoint/{{webhookResponse.body.id}}/connectivity`
* **HTTP method** - GET
* **Web request body** - Empty
* Select **Delay execution of subsequent rule actions until we've received a response for this web request**.
  Alternatively, you can continue running the rule and set up error handling.
* **Headers** - Insert `Content-Type` and `Authorization` as **Keys** and add the respective **Values** `application/json` and `Bearer {{authToken}}`.
  Make sure there's a non-breaking space between `Bearer` and `{{authToken}}`.

See [Endpoint Connectivity Status](/developers/api/endpoint/endpoint-connectivity-by-id-get) in the API reference for more information on the response structure and possible statuses.

### Step 6: Edit the existing comment with the connectivity status

Finally, update the comment you added to the issue with the current connectivity status for your team to reference.

Add an **Edit comment** action, then configure the fields as follows:

* **Comment to edit** - Last comment (the comment you created).
* **Comment** - Add the connectivity status from the response of the web request.
* **Comment Visibility** - Defaults to **Existing Visibility** because you're editing an existing comment.

The following is an example comment that uses `{{currentComment}}` to include the existing content and add the connectivity status with links to the relevant documentation:

```txt wordWrap
{{currentComment}}

[Connectivity status|https://www.emnify.com/iot-glossary#connectivity-status]: *{{webhookResponse.body.status.description}}*
```

### Step 7: Define the rule details and turn it on

For this rule to run, you need to define the rule details and then turn it on.
For more information on the different rule details you can edit and what they mean, see [What are rule details in Atlassian Automation?](https://support.atlassian.com/cloud-automation/docs/what-are-rule-details-in-atlassian-automation/)

Select **Rule details**

Add a **Name** for your rule (for example, *Fetch Current Device and SIM Statuses*).
Optionally, add a **Description** to explain the rule's purpose.

Select an **Owner**.
This is the person who receives emails when the rule fails.

Choose an **Actor**.
The selected user performs the actions defined in the rule.
**Automation for Jira** is the default actor and is recommended because it makes it clear to your team that this is an automated process.

Configure your notifications, editing rights, and whether you want to allow other rule actions to trigger this rule.

Review your details, then click **Turn on rule**.

> **Info**
>
> You might need to confirm the name and who can edit the rule, then click **Turn on rule** again.

> **Success**
>
> You should see an **Enabled** badge next to the rule name when the rule has been successfully turned on and is active.

Once active, this rule generates a comment on the issue with the device, SIM, and connectivity status when an issue is created.

![Internal note from Automation for Jira with device and SIM state and Connectivity status OFFLINE](/_fern-img/408efa5e37585f625ece88d093604a3668f70ad903b88d3ded34cbff56ea859d.webp)

## Create a manual trigger to reset connectivity

Often, while troubleshooting, you need to reset the device's connectivity.
You can create [a rule manually triggered](https://support.atlassian.com/cloud-automation/docs/test-a-jira-automation-rule-using-the-manual-trigger/) by your team from the **Actions** on any issue to reset the connectivity using the emnify REST API.

### Step 1: Set up the trigger and conditions \[#step-1-set-up-triggers-reset-connectivity]

In your Jira Service Desk project, navigate to **Project settings** > **Automation**.

Select **Create rule**.

Add the **Manual trigger from issue** trigger.

Add the **Issue fields condition** and set the condition to `ICCID is not empty`.

> **Info**
>
> You don't need to select **Prompt for input when this rule is triggered** because you should have all the information required to reset the connectivity.

### Step 2: Generate an authentication token for the emnify REST API \[#step-2-generate-auth-token-reset-connectivity]

> **Note**
>
> This API path has a rate limit of 100 requests per IP in a 5-minute window.
> For more information, see [Rate limits](/developers/api-guidelines/rate-limits).

Add the **Send web request** action and configure the fields as follows:

* **Web request URL** - `https://cdn.emnify.net/api/v1/authenticate`

* **HTTP method** - POST

* **Web request body** - Select **Custom data** then add the following JSON payload:

  ```json
  {
    "application_token": "YOUR_APPLICATION_TOKEN"
  }
  ```

* Select **Delay execution of subsequent rule actions until we've received a response for this web request**.
  Alternatively, you can continue running the rule and set up error handling.

* **Headers** - Insert `Content-Type` as a **Key** and add `application/json` as the respective **Value**.

The response contains the `auth_token` you'll use to authenticate further requests.
See [Retrieve Authentication Token](/developers/api/authentication/authenticate) in the emnify documentation for more details about the response structure and examples.

Because this automation requires multiple calls to the emnify REST API, you also need to store the `auth_token` as a variable.
Creating a variable saves a smart value as a semantic name that you can use in other actions or conditions within this rule.

Add a **Create variable** action, then configure the fields as follows:

* **Variable name** - `authToken`
* **Smart value** - `{{webhookResponse.body.auth_token}}`

The authentication token is now stored in the `{{authToken}}` variable for future use.

### Step 3: Use the emnify REST API to get the device details \[#step-3-device-details-reset-connectivity]

Add a **Send web request** action and configure the fields as follows:

* **Web request URL** - `https://cdn.emnify.net/api/v1/endpoint?q=iccid:{{issue.ICCID}}`
* **HTTP method** - GET
* **Web request body** - Empty, as the URL handles the filtering.
* Select **Delay execution of subsequent rule actions until we've received a response for this web request**.
  Alternatively, you can continue running the rule and set up error handling.
* **Headers** - Insert `Content-Type` and `Authorization` as **Keys** and add the respective **Values** `application/json` and `Bearer {{authToken}}`.
  Make sure there's a non-breaking space between `Bearer` and `{{authToken}}`.

The response contains device information that you'll use in subsequent actions.
See [List Endpoints](/developers/api/endpoint/get-endpoints) in the emnify documentation for more details about the response structure and examples.

The requests in this automation have varied response formats, so you must also store the device ID as a variable.

Add a **Create variable** action, then configure the fields as follows:

* **Variable name** - `deviceID`
* **Smart value** - `{{webhookResponse.body.id}}`

The device ID is now stored in the `{{deviceID}}` variable for future use.

### Step 4: Use the emnify REST API to reset the connectivity

Next, use your `{{deviceID}}` variable to execute the [Reset Endpoint Connectivity](/developers/api/endpoint/update-endpoint-connectivity-by-id) API call.

Add a **Send web request** action, then configure the fields as follows:

* **Web request URL** - `https://cdn.emnify.net/api/v1/endpoint/{{deviceID}}/connectivity`
* **HTTP method** - PATCH
* **Web request body** - Empty
* Select **Delay execution of subsequent rule actions until we've received a response for this web request**.
  Alternatively, you can continue running the rule and set up error handling.
* **Headers** - Insert `Content-Type` and `Authorization` as **Keys** and add the respective **Values** `application/json` and `Bearer {{authToken}}`.
  Make sure there's a non-breaking space between `Bearer` and `{{authToken}}`.

The response is empty when successful.
See [Reset Endpoint Connectivity](/developers/api/endpoint/update-endpoint-connectivity-by-id) in the emnify documentation for dispatch options.

### Step 5: Comment on the issue with the reset status

1. Add a **Comment on issue** action.
2. Write a comment stating that reset connectivity has been triggered. This comment appears while the rule retrieves the current connectivity status.
3. Select **Prevent duplicates by only adding this comment once to a particular issue**.
   You want to add the comment only once per issue.
4. Select the **Comment Visibility** (either **Internal only** or **Share with customer**).

The following is an example comment:

```txt
🔄 Reset connectivity triggered
```

### Step 6: Use the emnify REST API to get the connectivity status

> **Warning**
>
> When reset connectivity is triggered, the device detaches from the network and waits for the modem to connect again.
> Depending on the device and network conditions, this process can take a few seconds to a few minutes.
> By default, this action runs immediately after the comment is added to the issue, so the connectivity status fetched in this action may not be accurate unless you add a delay (possible with a Premium or Enterprise plan).

Add a **Send web request** action, then configure the fields as follows:

* **Web request URL** - `https://cdn.emnify.net/api/v1/endpoint/{{webhookResponse.body.id}}/connectivity`
* **HTTP method** - GET
* **Web request body** - Empty
* Select **Delay execution of subsequent rule actions until we've received a response for this web request**.
  Alternatively, you can continue running the rule and set up error handling.
* **Headers** - Insert `Content-Type` and `Authorization` as **Keys** and add the respective **Values** `application/json` and `Bearer {{authToken}}`.
  Make sure there's a non-breaking space between `Bearer` and `{{authToken}}`.

See [Endpoint Connectivity Status](/developers/api/endpoint/endpoint-connectivity-by-id-get) in the API reference for more information on the response structure and possible statuses.

### Step 7: Edit the existing comment with the connectivity status

Finally, you need to update the existing comment with the connectivity status for your team to reference.

Add an **Edit comment** action, then configure the fields as follows:

* **Comment to edit** - Last comment (the comment you created).
* **Comment** - Add the connectivity status from the response of the web request.
* **Comment Visibility** - Defaults to **Existing Visibility** because you're editing an existing comment.

The following is an example comment that replaces the existing comment completely and includes the connectivity status with links to the relevant documentation:

```txt wordWrap
✅ Successfully reset connectivity

[Connectivity status|https://www.emnify.com/iot-glossary#connectivity-status]: *{{webhookResponse.body.status.description}}*
```

### Step 8: Define the rule details and turn it on

Select **Rule details**

Add a **Name** for your rule (for example, *Reset Connectivity*).
Optionally, add a **Description** to explain the rule's purpose.

Select an **Owner**.
This is the person who receives emails when the rule fails.

Choose an **Actor**.
The selected user performs the actions defined in the rule.
**Automation for Jira** is the default actor and is recommended because it makes it clear to your team that this is an automated process.

Configure your notifications, editing rights, and whether you want to allow other rule actions to trigger this rule.

Review your details, then click **Turn on rule**.

> **Info**
>
> You might need to confirm the name and who can edit the rule, then click **Turn on rule** again.

> **Success**
>
> You should see an **Enabled** badge next to the rule name when the rule has been successfully turned on and is active.

Once active, the rule is visible from **Actions** on the defined issues.

![Actions menu listing the Reset Connectivity rule under From automation](/_fern-img/87994f7f2512bc183557934d9c7396d7fecc7d0ca346579220b680e1c70ee785.webp)

After it's triggered, this rule generates a comment on the issue indicating a successful reset and the current connectivity status.

![Internal note from Automation for Jira reading Successfully reset connectivity, with Connectivity status OFFLINE](/_fern-img/7d3d288f44e3069e76794f536102f9cb28b5ec1b3dc31cb2b53d458117b3b2cc.webp)

## Create a manual trigger to get the connectivity status

You can also add a manual trigger to fetch a device's current connectivity status.
Setting up this rule follows a similar process to the [manual trigger to reset connectivity](#create-a-manual-trigger-to-reset-connectivity) but with a few changes.

### Step 1: Set up the trigger and conditions \[#step-1-set-up-triggers-get-connectivity-status]

In your Jira Service Desk project, navigate to **Project settings** > **Automation**.

Select **Create rule**.

Add the **Manual trigger from issue** trigger.

Add the **Issue fields condition** and set the condition to `ICCID is not empty`.

> **Info**
>
> You don't need to select **Prompt for input when this rule is triggered** because you should have all the information required to get the connectivity status.

### Step 2: Generate an authentication token for the emnify REST API \[#step-2-generate-auth-token-get-connectivity-status]

> **Note**
>
> This API path has a rate limit of 100 requests per IP in a 5-minute window.
> For more information, see [Rate limits](/developers/api-guidelines/rate-limits).

Add the **Send web request** action and configure the fields as follows:

* **Web request URL** - `https://cdn.emnify.net/api/v1/authenticate`

* **HTTP method** - POST

* **Web request body** - Select **Custom data** then add the following JSON payload:

  ```json
  {
    "application_token": "YOUR_APPLICATION_TOKEN"
  }
  ```

* Select **Delay execution of subsequent rule actions until we've received a response for this web request**.
  Alternatively, you can continue running the rule and set up error handling.

* **Headers** - Insert `Content-Type` as a **Key** and add `application/json` as the respective **Value**.

The response contains the `auth_token` you'll use to authenticate further requests.
See [Retrieve Authentication Token](/developers/api/authentication/authenticate) in the emnify documentation for more details about the response structure and examples.

Because this automation requires multiple calls to the emnify REST API, you also need to store the `auth_token` as a variable.
Creating a variable saves a smart value as a semantic name that you can use in other actions or conditions within this rule.

Add a **Create variable** action, then configure the fields as follows:

* **Variable name** - `authToken`
* **Smart value** - `{{webhookResponse.body.auth_token}}`

The authentication token is now stored in the `{{authToken}}` variable for future use.

### Step 3: Use the emnify REST API to get the device details \[#step-3-device-details-get-connectivity-status]

Add a **Send web request** action and configure the fields as follows:

* **Web request URL** - `https://cdn.emnify.net/api/v1/endpoint?q=iccid:{{issue.ICCID}}`
* **HTTP method** - GET
* **Web request body** - Empty, as the URL handles the filtering.
* Select **Delay execution of subsequent rule actions until we've received a response for this web request**.
  Alternatively, you can continue running the rule and set up error handling.
* **Headers** - Insert `Content-Type` and `Authorization` as **Keys** and add the respective **Values** `application/json` and `Bearer {{authToken}}`.
  Make sure there's a non-breaking space between `Bearer` and `{{authToken}}`.

The response contains device information that you'll use in subsequent actions.
See [List Endpoints](/developers/api/endpoint/get-endpoints) in the emnify documentation for more details about the response structure and examples.

### Step 4: Use the emnify REST API to get the connectivity status

Add a **Send web request** action, then configure the fields as follows:

* **Web request URL** - `https://cdn.emnify.net/api/v1/endpoint/{{webhookResponse.body.id}}/connectivity`
* **HTTP method** - GET
* **Web request body** - Empty
* Select **Delay execution of subsequent rule actions until we've received a response for this web request**.
  Alternatively, you can continue running the rule and set up error handling.
* **Headers** - Insert `Content-Type` and `Authorization` as **Keys** and add the respective **Values** `application/json` and `Bearer {{authToken}}`.
  Make sure there's a non-breaking space between `Bearer` and `{{authToken}}`.

See [Endpoint Connectivity Status](/developers/api/endpoint/endpoint-connectivity-by-id-get) in the API reference for more information on the response structure and possible statuses.

### Step 5: Comment on the issue with the connectivity status

Use the `{{webhookResponse}}` smart values to write a comment on the issue.

1. Add a **Comment on issue** action.
2. Write a comment referencing the connectivity status from the response of the previous web request.
3. Select **Prevent duplicates by only adding this comment once to a particular issue**.
   You want to add the comment only once per issue.
4. Select the **Comment Visibility** (either **Internal only** or **Share with customer**).

The following is an example comment that includes links to the relevant documentation:

```txt wordWrap
[Connectivity status|https://www.emnify.com/iot-glossary#connectivity-status]: *{{webhookResponse.body.status.description}}*
```

### Step 6: Define the rule details and turn it on

Select **Rule details**

Add a **Name** for your rule (for example, *Get Connectivity Status*).
Optionally, add a **Description** to explain the rule's purpose.

Select an **Owner**.
This is the person who receives emails when the rule fails.

Choose an **Actor**.
The selected user performs the actions defined in the rule.
**Automation for Jira** is the default actor and is recommended because it makes it clear to your team that this is an automated process.

Configure your notifications, editing rights, and whether you want to allow other rule actions to trigger this rule.

Review your details, then click **Turn on rule**.

> **Info**
>
> You might need to confirm the name and who can edit the rule, then click **Turn on rule** again.

> **Success**
>
> You should see an **Enabled** badge next to the rule name when the rule has been successfully turned on and is active.

Once active, the rule is visible from **Actions** on the defined issues.

![Actions menu listing the Get Connectivity Status and Reset Connectivity rules](/_fern-img/14594fcc904ace81329d6a13f38edd4bb7dc369828e10220e544a669bcc145f9.webp)

After it's triggered, this rule generates a comment on the issue with the current connectivity status

![Internal note from Automation for Jira with Connectivity status ONLINE](/_fern-img/5fd05833981a14decbcf8160915856157a538c92a9e9827a91b8af6891076cc9.webp)