Overview
This node interacts with GitHub's API to retrieve multiple comments from issues within a specified repository. It is useful for scenarios where you want to analyze, monitor, or process discussions happening on GitHub issues programmatically. For example, you might use it to gather all comments on issues to perform sentiment analysis, track user feedback, or automate responses based on comment content.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with GitHub API. Options: "Access Token" (personal access token) or "OAuth2" (OAuth 2.0 authentication). |
| Repository Owner | The owner of the GitHub repository. Can be selected by listing users, providing a GitHub URL (e.g., https://github.com/n8n-io), or entering the owner's name directly. |
| Repository Name | The name of the GitHub repository. Can be selected by listing repositories, providing a GitHub repository URL (e.g., https://github.com/n8n-io/n8n), or entering the repository name directly. |
| Return All | Boolean flag indicating whether to return all issue comments or limit the number of results. If true, the node paginates through all available comments. |
| Limit | When "Return All" is false, this sets the maximum number of issue comments to return (minimum 1, maximum 100). |
Output
The node outputs JSON data representing the retrieved issue comments. Each item in the output corresponds to a single issue comment object as returned by the GitHub API, typically including fields such as:
id: Unique identifier of the comment.body: Text content of the comment.user: Information about the author of the comment.created_atandupdated_at: Timestamps for creation and last update.- Other metadata related to the comment and its context.
No binary data output is produced by this node.
Dependencies
- Requires a valid GitHub API authentication credential, either an access token or OAuth2 token.
- Needs network access to GitHub's REST API at
https://api.github.com. - Uses internal methods to list users and repositories for resource selection.
Troubleshooting
- Authentication errors: Ensure that the provided access token or OAuth2 credentials have sufficient permissions to read issue comments in the target repository.
- Invalid repository or owner input: Verify that the repository owner and name are correctly specified and exist on GitHub.
- Rate limiting: GitHub enforces API rate limits; if exceeded, the node may fail to retrieve data. Consider using authenticated requests to increase limits.
- Pagination issues: When "Return All" is enabled, the node handles pagination automatically. If incomplete data is returned, check network stability or API response headers.
- Validation errors: Input URLs or names must match expected patterns; otherwise, validation errors will occur.