Overview
This node interacts with GitHub's API to retrieve multiple issue comments from a specified repository. It is useful for scenarios where users want to gather all comments on issues within a repository for analysis, reporting, or integration with other workflows. For example, a user might use this node to fetch all comments on issues in a project repository to monitor feedback or track discussions.
Use Case Examples
- Fetch all issue comments from the 'n8n-io/n8n' repository to analyze user feedback.
- Retrieve a limited number of issue comments from a specific repository to display recent discussions in a dashboard.
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 from which to fetch issue comments. Can be selected from a list, provided as a URL, or entered by name. |
| Repository Name | The name of the GitHub repository from which to fetch issue comments. Can be selected from a list, provided as a URL, or entered by name. |
| Limit | Maximum number of issue comments to return when not returning all results. |
| Return All | Whether to return all issue comments or limit the number of results. |
| Request Options | Additional HTTP request options such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
id- Unique identifier of the issue comment.body- Content of the issue comment.userlogin- Username of the comment author.
created_at- Timestamp when the comment was created.updated_at- Timestamp when the comment was last updated.issue_url- URL of the issue to which the comment belongs.
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.
- Invalid repository owner or name inputs. Verify that the owner and repository names or URLs are correctly formatted and exist on GitHub.
- API rate limits exceeded. If many requests are made in a short period, GitHub may throttle the API calls. Consider using authentication to increase rate limits or reduce request frequency.
- SSL certificate issues if 'Ignore SSL Issues' is not enabled and the network environment has SSL interception or self-signed certificates.
Links
- GitHub API - Issue Comments - Official GitHub API documentation for issue comments endpoints.