# Issue Closed

> Windows | Cross-platform

## Project compatibility

Windows | Cross-platform

## Overview

| Description | API Method | API Path | Notes |
| --- | --- | --- | --- |
| The Issue Closed trigger starts a workflow when an existing issue is transitioned to a closed state in the monitored repository. | GET | /repos/{owner}/{repo}/issues | Pre-filtered by `state=closed` |

## Input

| Parameter | Description | Data Type |
| --- | --- | --- |
| Repository | Repository to monitor for issues being closed. | string |
| Filter | Optional issue filter (issue number, repository name, state, title, body, assignee, milestone) restricting which closed issues trigger. | variable |

## Output

| Parameter | Description | Data Type |
| --- | --- | --- |
| Issue ID | ID of the issue that was closed and triggered. | string |
| Issue | Hydrated issue object at the time of closure. | Object |

:::note
* In API workflows, a single
response object is returned as the output. Any required fields can be extracted directly from this object.
* In RPA workflows, some output
parameters may differ, but the necessary values can still be retrieved from the response object even if they are not explicitly exposed.
:::