Save GitHub issue as a text file
Create a UTF-8 file in My Drive or a selected folder.
Ready-made Workflow
Create a UTF-8 text file in Google Drive whenever a GitHub issue is opened. Files include the issue title, full description, repository, author, creation time and original issue link. Connect GitHub and Google Drive, browse to a repository and optionally select a destination folder. The Actions filter is prefilled with opened. Leaving Parent folder empty saves to My Drive. Each filename uses the repository ID and issue number to distinguish issues across repositories. Includes its own fictional English Leipzig example. Only new opened events received after activation are processed; existing issues are not imported. Edits, comments, closed and reopened issues do not create or update files. Markdown remains plain source text; linked attachments are not downloaded. This is a one-time snapshot, not an issue backup or two-way synchronization. Files inherit destination folder access; no public sharing is added. Manual reruns can create duplicate files.
What gets copied
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Create a UTF-8 file in My Drive or a selected folder.
Before activation
Connect your own GitHub account and review the provider settings used by this Workflow.
Connect your own Google Drive account and review the provider settings used by this Workflow.
Questions
No. FastHook creates a disconnected Draft. Connect your own GitHub, Google Drive accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.