Pull Request
Emit an event when GitHub delivers the pull_request webhook.
Ready-made Workflow
Create a Notion review page when a GitHub pull request is opened. Each child page includes the PR title and number, repository, author, source and target branches, a clickable GitHub link, and Review notes and Follow-up sections. Connect the FastHook GitHub App and Notion, browse to the repository to track, then choose an accessible parent Notion page. The Actions filter is prefilled with opened. Draft PRs are included. Edits, new commits, reviews, closed and reopened PRs do not create another page. Includes an independent fictional English example with German characters. Only new webhook events received after activation are processed; existing PRs are not imported. This is one-way child page creation, not database rows, reviewer assignment or status synchronization. PR bodies, code changes, comments and attachments are not copied. Page details become visible to people with access to the selected Notion parent. Manual workflow reruns can create duplicates.
What gets copied
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Emit an event when GitHub delivers the pull_request webhook.
Create a titled page under an existing Notion page.
Before activation
Connect your own GitHub account and review the provider settings used by this Workflow.
Connect your own Notion account and review the provider settings used by this Workflow.
GitHub · Notion
Keep a release journal in Notion: create a child page when a GitHub release is published. Each page includes the release tag and optional title, repository, author, publication time, pre-release flag, clickable GitHub link, and Review notes and Follow-up sections. Connect the FastHook GitHub App and Notion, browse to the repository to track, then choose an accessible parent Notion page. The Actions filter is prefilled with published. Both stable releases and published pre-releases are included. Draft releases, edits and deleted releases do not create pages. Includes an independent fictional English release example. Release notes, assets and source code are not copied. Only new publication events after activation are processed; existing releases are not imported. This creates child pages, not database rows or deployment verification, and does not synchronize later changes. Page details become visible to people with access to the selected parent. Manual workflow reruns or unpublishing and republishing a release can create duplicates.
GitHub · Notion
Create a Notion triage page when a new GitHub issue is opened. Each child page includes the issue title, repository, author and source link, plus Triage and Notes sections for your team. Connect the FastHook GitHub App and Notion, select a repository, then browse to an accessible parent Notion page. The Actions filter is prefilled with opened, so edits, comments, closed and reopened issues do not create pages. Includes a fictional English example with German characters. Only new events received after activation are processed; existing issues are not imported. This is one-way page creation, not status synchronization. Issue bodies, comments and attachments are not copied. Titles and repository details become visible to everyone with access to the selected Notion parent. This creates child pages, not database rows.
Questions
No. FastHook creates a disconnected Draft. Connect your own GitHub, Notion 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.