Overview
This node allows you to create new issues in GitHub repositories via the GitHub API. It is useful for automating issue tracking workflows, such as automatically opening bug reports, feature requests, or task items based on external triggers or data.
Practical examples include:
- Creating an issue when a form is submitted on a website.
- Opening a bug report automatically from error monitoring tools.
- Logging tasks or reminders into a project repository.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: either "Access Token" or "OAuth2" |
| Repository Owner | The owner of the repository where the issue will be created. Can be selected from a list, provided as a GitHub URL, or entered by name. |
| Repository Name | The name of the repository where the issue will be created. Can be selected from a list, provided as a GitHub URL, or entered by name. |
| Title | The title of the issue (required) |
| Body | The body content of the issue (optional) |
| Labels | One or more labels to assign to the issue. Each label is a string. |
Output
The node outputs JSON data representing the created GitHub issue. This typically includes details such as the issue ID, URL, title, body, labels, state, and other metadata returned by the GitHub API.
The node does not output binary data.
Dependencies
- Requires a valid GitHub API authentication token, either via an access token or OAuth2 credentials.
- The node uses the official GitHub REST API endpoint
https://api.github.com. - No additional external dependencies are required beyond the configured credentials.
Troubleshooting
- Authentication errors: Ensure that the provided access token or OAuth2 credentials have sufficient permissions to create issues in the target repository.
- Invalid repository owner or name: Verify that the owner and repository names are correct and accessible by the authenticated user.
- Validation errors: The title field is required; missing it will cause errors.
- Label errors: Labels must exist in the repository or be valid strings; otherwise, the API may reject them.
- API rate limits: If you encounter rate limit errors, check your GitHub API usage and consider using authentication with higher limits.