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 creating bug reports, feature requests, or task assignments directly from n8n workflows. For example, a user can automatically create an issue when a form is submitted or when an error is detected in an application.

Use Case Examples

  1. Automatically create a GitHub issue when a customer submits a bug report via a web form.
  2. Create issues in a repository to track tasks generated from project management tools.

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 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 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 the owner and repository fields are correctly filled and match existing GitHub entities.
  • Network or proxy issues causing request failures. Check proxy settings and network connectivity.
  • SSL certificate validation errors if using self-signed certificates. Use the 'Ignore SSL Issues' option cautiously if necessary.

Links

Discussion