GitHub Issues icon

GitHub Issues

Consume issues from the GitHub API
Join our community

Actions4

Overview

This node allows users to create issues in GitHub repositories via the GitHub API. It is useful for automating issue tracking and management workflows, such as automatically opening issues based on external triggers or integrating issue creation into broader automation pipelines. For example, a user can create a new issue with a title, body, and labels in a specified repository owned by a particular user or organization.

Use Case Examples

  1. Automatically create a bug report issue when an error is detected in an application.
  2. Create feature request issues from form submissions.
  3. Log issues from monitoring tools directly into GitHub repositories.

Properties

Name Meaning
Authentication Method used to authenticate with GitHub API, either Access Token or OAuth2.
Repository Owner The owner of the GitHub 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 GitHub repository where the issue will be created. Can be selected from a list, provided as a GitHub repository URL, or entered by name.
Title The title of the issue to be created.
Body The body content or description of the issue.
Labels Labels to assign to the issue. Multiple labels can be added.
Request Options Advanced HTTP request options such as batching, SSL certificate validation, proxy settings, and timeout configuration.

Output

JSON

  • id - Unique identifier of the created issue.
  • number - Issue number within the repository.
  • title - Title of the created issue.
  • body - Body content of the created issue.
  • labels - Array of labels assigned to the issue.
  • state - Current state of the issue (e.g., open, closed).
  • url - URL link to the created issue on GitHub.

Dependencies

  • GitHub API

Troubleshooting

  • Authentication errors due to invalid or expired tokens. Ensure the provided access token or OAuth2 credentials are valid and have the necessary permissions to create issues.
  • Invalid repository owner or name input. Verify that the owner and repository names or URLs are correct and accessible.
  • Network or proxy issues causing request failures. Check proxy settings and network connectivity.
  • SSL certificate validation errors if 'Ignore SSL Issues' is not enabled and the server's SSL certificate is invalid.

Links

Discussion