Pull Request
Emit an event when GitHub delivers the pull_request webhook.
→
Ready-made Workflow
Save new GitHub pull requests as Google Drive text files
Create a UTF-8 text file in Google Drive whenever a GitHub pull request is opened. Files include the PR title, full description, repository, author, creation time, draft status, source and target branches, and original PR link. Connect GitHub and Google Drive, browse to a repository and optionally select a destination folder. The Actions filter is prefilled with opened; draft PRs are included. Leaving Parent folder empty saves to My Drive. Filenames use the repository ID and PR number. Includes its own fictional English Freiburg example with German characters. Only new opened events received after activation are processed; existing PRs are not imported. Edits, new commits, reviews, closed and reopened PRs do not create or update files. Markdown remains plain source text; code changes, comments and linked attachments are not downloaded. This is a one-time snapshot, not a code backup, reviewer assignment or two-way synchronization. Files inherit destination folder access; no public sharing is added. Manual reruns can create duplicate files.
Use this templateCreates a new Draft · no credentials copied
What gets copied
The working graph, not another user's secrets
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Save GitHub pull request as a text file
Create a UTF-8 file in My Drive or a selected folder.
Before activation
Connect your accounts in the Draft
GitHub
Connect your own GitHub account and review the provider settings used by this Workflow.
Google Drive
Connect your own Google Drive account and review the provider settings used by this Workflow.
Explore connected apps
Related Workflow templates
GitHub · Google Drive
Save new GitHub issues as Google Drive text files
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.
- 1. GitHub · Issues
- 2. Google Drive · Save GitHub issue as a text file
GitHub · Google Drive
Save published GitHub release notes in Google Drive
Archive published GitHub release notes as UTF-8 text files in Google Drive. Each file contains the tag, optional release title, full notes, repository, author, publication time, pre-release flag and original GitHub link. Connect GitHub and Google Drive, browse to a repository and optionally select a destination folder. The Actions filter is prefilled with published; stable releases and published pre-releases are included. Leaving Parent folder empty saves to My Drive. Filenames use repository and release IDs, so tags containing slashes or German characters do not become folder paths. Includes its own fictional English Nürnberg release example. Only new publication events received after activation are processed; existing releases are not imported. Drafts, edits and deleted releases do not create or update files. Markdown remains plain source text; release assets, source code and binaries are not downloaded. This is a release-notes snapshot, not a deployment check or synchronized backup. Files inherit destination folder access; no public sharing is added. Manual reruns or unpublishing and republishing a release can create duplicates.
- 1. GitHub · Release
- 2. Google Drive · Archive GitHub release notes
Questions
Template FAQ
Does the template copy someone else's credentials?
No. FastHook creates a disconnected Draft. Connect your own GitHub, Google Drive accounts before activation.
Can I change the Steps and mappings?
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
What is copied into my workspace?
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
When does the Workflow start running?
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.