Pull Request
Receive pull_request events from the selected repository with Actions filtered to opened. Draft PRs are included, while later edits, commits and reviews are excluded.
Workflow template
Create a Notion review page when a GitHub pull request opens, including draft PRs. Add the PR title, repository, author, branches and source link, with Review notes and Follow-up headings for your team.
How it works
Receive pull_request events from the selected repository with Actions filtered to opened. Draft PRs are included, while later edits, commits and reviews are excluded.
Create a child page titled [PR #number] title beneath your chosen parent. Include repository, author, a clickable GitHub URL, source-to-target branches and empty Review notes and Follow-up headings.
The result
The page gives your team space for its review notes. It does not read the diff, write an automated review or assign reviewers in GitHub.
[PR #60] Review the München release guide
Repository: example-studio/project-tracker Opened by: alex-example GitHub pull request: https://github.com/example-studio/project-tracker/pull/60 Branches: docs/munich-release -> main Review notes Follow-up
Fictional PR. Drafts can create pages, but this prepared page body does not display a draft flag or creation timestamp. PR body, code changes, comments and attachments are not copied.
Before activation
Connect the FastHook GitHub App with repository access and browse to the source repository. Keep opened selected in Actions; draft PRs are included.
Connect Notion and grant the FastHook connection access to the intended parent. Select it in Create a Notion pull request review page. The action creates child pages beneath this parent.
Wait for the trigger to connect, then open a fictional PR in the selected repository. Inspect its child page, branch direction and GitHub link, and confirm the two headings are ready for your notes.
Child pages with empty review sections. This creates ordinary pages, not database rows. Review notes and Follow-up are headings for people to fill in. The recipe neither generates a code review nor assigns a GitHub reviewer.
Draft openings are included without a draft label. The opened filter includes draft PRs, but the Notion mapping does not display the draft flag. Use the source link to inspect readiness and current status. Later commits, reviews and ready-for-review changes do not update the page.
One-way creation and parent access. Only new opened events after activation are processed; older PRs are not imported. Parent-page readers can see copied titles and branch details. Reruns can create another child page because there is no existing-page lookup.
It creates a child page under an existing accessible parent page. Choose the parent in the action; no database schema is required.
Draft PRs are included when opened. The prepared Notion page does not map the draft flag, so follow the GitHub link to check whether a PR is ready for review.
No. Review notes and Follow-up are empty headings for your team. The workflow does not fetch code changes, generate a review or assign GitHub reviewers.
No. The opened filter creates a one-time page. Edits, new commits, reviews, closures and reopenings do not update it; manual reruns can create duplicate pages.
Keep a release journal in Notion: create a child page when a GitHub release is published.
View template →Create a Notion triage page when a new GitHub issue is opened.
View template →