GitHub Issues icon

GitHub Issues

Consume issues from the GitHub API
Join our community

Actions4

Overview

This node integrates with the GitHub API to create issues in a specified GitHub repository. It is useful for automating issue tracking workflows, such as automatically logging bugs, feature requests, or tasks from other systems into GitHub repositories. For example, it can be used to create an issue when a customer support ticket is received or when an error is detected in an application.

Use Case Examples

  1. Automatically create a GitHub issue when a new support ticket is created in a helpdesk system.
  2. Log errors detected in a monitoring system as GitHub issues for developers to track and resolve.

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 options for the API request such as batching, SSL certificate validation, proxy settings, and timeout.

Output

JSON

  • id - The unique identifier of the created issue.
  • url - The URL of the created issue on GitHub.
  • title - The title of the created issue.
  • body - The body content of the created issue.
  • labels - The labels assigned to the created issue.
  • state - The state of the issue (e.g., open, closed).
  • created_at - Timestamp when the issue was created.
  • updated_at - Timestamp when the issue was last updated.

Dependencies

  • GitHub API

Troubleshooting

  • Authentication errors due to invalid or expired tokens. Ensure the access token or OAuth2 credentials are valid and have the necessary permissions to create issues.
  • Invalid repository owner or name causing 404 errors. Verify the owner and repository names or URLs are correct and accessible.
  • API rate limits exceeded. Consider using authentication and batching options to manage request rates.
  • SSL certificate validation errors if using self-signed certificates. Use the 'Ignore SSL Issues' option cautiously if needed.

Links

Discussion