GitHub Issues icon

GitHub Issues

Consume issues from the GitHub API
Join our community

Actions4

Overview

This node interacts with GitHub's API to retrieve information about a specific issue within a repository. It is useful for workflows that need to fetch detailed data about an issue, such as its status, description, comments, and other metadata. Practical examples include automating issue tracking, integrating GitHub issues with project management tools, or triggering actions based on issue updates.

Use Case Examples

  1. Fetch details of a specific issue by its ID to display in a dashboard.
  2. Automatically retrieve issue information to update a project management system.
  3. Use issue data to trigger notifications or other automated workflows.

Properties

Name Meaning
Authentication Method used to authenticate with GitHub API, either via Access Token or OAuth2.
Repository Owner The owner of the GitHub repository. Can be selected from a list, provided as a URL, or entered by name.
Repository Name The name of the GitHub repository. Can be selected from a list, provided as a URL, or entered by name.
Issue The specific issue to retrieve. Can be selected from a list or entered by its ID.
Request Options Additional options for the request such as batching, SSL certificate validation, proxy settings, and timeout.

Output

JSON

  • id - Unique identifier of the issue.
  • title - Title of the issue.
  • body - Detailed description or content of the issue.
  • state - Current 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.
  • user
    • login - Username of the issue creator.
  • assignees - List of users assigned to the issue.
  • labels - Labels associated with the issue.

Dependencies

  • GitHub API

Troubleshooting

  • Ensure the authentication credentials (Access Token or OAuth2) are valid and have the necessary permissions to access the repository and issues.
  • Verify that the repository owner and repository name are correctly specified and accessible with the provided credentials.
  • Check the issue ID is correct and exists in the specified repository.
  • If using URL input modes, ensure the URLs are correctly formatted as per the validation regex.
  • If requests fail due to SSL issues, consider enabling the 'Ignore SSL Issues' option, but be aware of security risks.
  • Adjust timeout settings if the GitHub API is slow to respond or if network latency is high.

Links

Discussion