Issues
Receive issues events from the selected repository with the Actions filter set to opened. Existing issues and later changes are excluded.
Workflow template
Save each newly opened GitHub issue as a UTF-8 text file in Google Drive. Include the full description and source metadata in a one-time snapshot, with a filename based on repository ID and issue number.
How it works
Receive issues events from the selected repository with the Actions filter set to opened. Existing issues and later changes are excluded.
Create GitHub-{repository ID}-issue-{number}.txt with the issue title, repository, author, creation time, link and full body. Save to the optional selected folder or My Drive.
The result
Each successful event creates a separate .txt file. Markdown from the issue body remains source text inside the file rather than becoming a rendered Google document.
GitHub issue #73: Review Leipzig onboarding checklist Repository: example-studio/support-portal Opened by: alex-example Created: 2026-09-16T18:00:00Z Source: https://github.com/example-studio/support-portal/issues/73 Description Prepare the onboarding checklist for the Leipzig support team. - Confirm ownership - Review the handoff notes
Fictional issue. Linked attachments are not downloaded. The repository ID in the filename distinguishes the same issue number across different repositories.
Before activation
Connect the FastHook GitHub App with repository access and browse to the intended repository. Leave opened selected in Actions to snapshot new issues only.
Connect Google Drive and optionally choose a Parent folder in Save GitHub issue as a text file. A blank folder saves to My Drive. Review destination access because the file includes the full issue description.
Activate and wait for the trigger to connect, then open a fictional issue with a short description. Check the generated filename, source fields and body in Drive. No existing issue is exported merely by activating the workflow.
A creation-time snapshot, not an issue backup. Only opened events received after activation create files. Edits, comments, closures and reopenings do not create or update files. There is no historical import or two-way synchronization.
Plain text with the original Markdown source. The file is UTF-8 text/plain and includes the issue body. Markdown remains source text, and linked attachment files are not downloaded. The Drive text-file action supports up to 20,000 characters, so large descriptions can exceed its limit.
Names identify issues but do not prevent duplicates. The filename combines repository ID and issue number. Each action run creates a new file rather than looking up and replacing an earlier one; manual reruns can create duplicate names.
Destination permissions govern the copied content. Files inherit destination folder access. The workflow adds no public sharing, but anyone with destination access can read the copied description and metadata independently of their GitHub access.
It is created in the connected account’s My Drive. Select a Parent folder in the action if you want a specific destination.
Yes. It includes title, repository, author, creation time, source link and description. Markdown remains plain source text, and linked attachment files are not downloaded.
No. The opened filter creates a one-time snapshot. Later edits, comments, closures and reopenings do not change it, and existing issues are not imported.
No. It distinguishes issue numbers across repositories, but the action always creates a new file. Rerunning an event can create another file with the same name.
Archive published GitHub release notes as UTF-8 text files in Google Drive.
View template →Create a UTF-8 text file in Google Drive whenever a GitHub pull request is opened.
View template →