Actions73
- Repository Actions
- Issue Actions
- Pull Request Actions
- User Actions
- Organization Actions
- Release Actions
- Webhook Actions
- Branch Actions
- Commit Actions
- Tag Actions
Overview
This node operation closes an issue in a specified repository on Forgejo. It is useful for automating issue management workflows, such as marking issues as resolved or completed directly from an n8n workflow. For example, after a successful deployment, you could automatically close related issues.
Use Case Examples
- Close an issue by specifying the repository owner, repository name, and issue number.
- Automate issue closure as part of a CI/CD pipeline.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization that owns the repository where the issue exists. |
| Repository | The name of the repository containing the issue to close. |
| Issue Number | The unique number identifying the issue to be closed within the repository. |
Output
JSON
json- The JSON response from the Forgejo API representing the closed issue's details or a success confirmation.
Dependencies
- Requires an API key credential for Forgejo API authentication.
Troubleshooting
- Ensure the provided owner, repository, and issue number are correct and the issue exists.
- Verify that the API credentials have sufficient permissions to modify issues in the repository.
- Common errors include authentication failures, invalid repository or issue identifiers, and insufficient permissions. Check the error message returned in the node output for details.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, useful for understanding the issue close endpoint and request structure.