Read and report
Read current open and closed issues in one selected GitHub Cloud repository, including titles, descriptions, states, lock flags and timestamps. Pull requests and code are excluded.
Read the repository's issues and keep approved title and description corrections in the same project workflow.
Updated November 2026
Read current open and closed issues in one selected GitHub Cloud repository, including titles, descriptions, states, lock flags and timestamps. Pull requests and code are excluded.
Eligible teammates can propose the supported changes listed below. The owner reviews the exact values and approves every proposed change before it is applied to GitHub.
Illustrative workflows using the supported capabilities. Connect your own account to work with your data.
Bring current open and closed issues into your reporting destination. Review issue titles, descriptions and timestamps while keeping pull requests and code outside this report.
A teammate proposes a clearer title or replacement Markdown description for an existing issue. The owner reviews the exact text before it reaches the selected repository; issue state and code remain outside this action.
Writes start disabled. The owner enables permitted actions and eligible teammates. Only fields supported by an enabled action can be proposed; some actions also support individual owner-selected writable fields.
Updates the title and Markdown description of an existing unlocked issue in one selected GitHub Cloud repository. The owner chooses writable fields. Description edits replace existing Markdown; edits containing mentions are rejected. Public repository edits are public and notifications or GitHub Actions may react. External edits can race execution. No code, pull requests, issue state, assignment, comments, creation or deletion.
The owner selects supported writable fields for this action before teammates can propose changes.
Choose the connection, permitted actions and eligible teammates. Select individual writable fields where the action supports it.
Choose an existing record and propose specific supported values. A proposal does not apply the change.
Check the current and proposed values, then approve that individual change. Changed records or permissions require a fresh review.
View the result in the audit history. An uncertain write is not automatically retried.
Provider permissions and workflows still apply. Source automations or notifications may react to approved changes.
Connected assistants can read available reports. Source changes use the separate Actions & approvals workflow in Datapipe.
Start with a controlled connection1 reporting datasets with their own fields. Choose a dataset in the app, then select the columns you need.
Current accessible open and closed issues in one selected GitHub Cloud repository, independent of report dates. Issue IDs, numbers, titles, Markdown descriptions, state, lock flags and timestamps are retrievable. Pull requests, code, comments and historical productivity metrics are excluded.
Current accessible open and closed issues in one selected GitHub Cloud repository, independent of report dates. Issue IDs, numbers, titles, Markdown descriptions, state, lock flags and timestamps are retrievable. Pull requests, code, comments and historical productivity metrics are excluded.
10 report fields across 1 datasets.
Browse the documented fields below. In the app, choose your project connection to load its field list. Availability depends on API permissions, report type, and compatible field combinations. Property-specific custom fields appear after connecting.
No fields match. Try another search or choose All.
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
Use an assistant to understand the reports. Propose source changes separately in Datapipe, where the owner reviews and approves every change.
Sample
| Issue ID | Issue number | Issue title | Markdown description | Issue state | Locked | Created at | Updated at |
|---|---|---|---|---|---|---|---|
| 1,240 | 7 | Review client brief | Card payment | open | false | 1,240 | Oct 27 |
| 640 | 640 | 640 | Refund | 640 | 640 | 640 | Oct 28 |
| 210 | 210 | 210 | Invoice | 210 | 210 | 210 | Oct 29 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Current accessible open and closed issues in one selected GitHub Cloud repository, independent of report dates. Issue IDs, numbers, titles, Markdown descriptions, state, lock flags and timestamps are retrievable. Pull requests, code, comments and historical productivity metrics are excluded.
Free to start. Paid plans add more connections and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 connections.
No. Name a project, add a connection, then choose a report and destination.
Datapipe reads the supported reports listed on this page and offers the write actions shown above. Writes start disabled. The owner enables permitted actions and eligible teammates; individual writable-field selection is available on supported actions. Every team member's proposed change needs a separate owner review and approval. Provider permissions still apply.
This page lists 10 report fields across 1 datasets. You pick the columns when you build the report.
Current accessible open and closed issues in one selected GitHub Cloud repository, independent of report dates. Issue IDs, numbers, titles, Markdown descriptions, state, lock flags and timestamps are retrievable. Pull requests, code, comments and historical productivity metrics are excluded. Account permissions and the records available from the provider determine which rows can be read.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.