GitHub Issues Read
Overview
The GitHub Issues Read Snap reads issues from a targeted repository, emitting one output document per issue.
Pull requests are automatically excluded from the results. Use the
State field to filter by issue status, and
Labels to narrow results to issues that carry all specified
labels. Use Updated since to perform incremental syncs by
passing the $latest_updated_at value from a previous run. Output
records are ordered by updated_at ascending.

- This is a Read-type Snap.
Works in Ultra Tasks
Supported Accounts
Prerequisites
None.
Snap views
| Type | Description | Examples of upstream and downstream Snaps |
|---|---|---|
| Input |
This Snap has at most one document input view. When connected, field values from the incoming document can be referenced
in expression-enabled fields using the |
|
| Output |
This Snap has one document output view. Each issue is emitted as a separate document containing fields such as
|
|
| Learn more about Error handling. | ||
Snap settings
| Field/Field set | Description |
|---|---|
Label*
String |
Specify a unique name for the Snap. Modify this to be more appropriate, especially if more than one of the same Snaps is in the pipeline. Default value: GitHub Issues Read |
Repository*
String/Expression |
Enter the repository to read issues from, in
Default value: None Example: |
State
Dropdown list |
Select the issue status to filter by.
Default value: all Example: all |
Labels
String/Expression |
Enter a comma-separated list of label names. Only issues that carry all specified labels are returned. Leave blank to return issues regardless of labels. Default value: None Example: |
Updated since
String/Expression |
Enter an ISO-8601 timestamp to return only issues updated at or after that
time. Pass Default value: None Example: |
|
Snap execution Dropdown list
|
Choose one of the three modes in
which the Snap executes. Available options are:
Default value: Validate & execute |
Troubleshooting
| Error | Reason | Resolution |
|---|---|---|
| Invalid repository: <value> | The Repository field does not contain a slash, so
it cannot be parsed as owner/repository_name. |
Enter the repository in owner/repository_name format,
for example SnapLogic/my-repo. |
| 404 Not Found | The repository does not exist, has been renamed, or the authenticated account does not have access to it. | Verify the repository name and owner. Confirm that the personal access token has at least read access to the repository. |