Recheck content when pull request readiness changes
A draft, reviewer, label, or merge-state change can be the right moment to revisit content readiness.
Trigger
Pull Request State / Properties Changed
Triggers when a specific GitHub pull request changes any of these tracked properties: state (open/closed), title, body, draft status, lock status, merge status, assignees, labels, requested reviewers, or milestone. The payload includes the full current PR details, the list of changed field names, and their previous values.
Action
Get Ordered Documents
Tool to fetch prismic documents ordered by a specified field. use after obtaining a valid api ref when you need sorted document results, e.g., orderings='[my.article.date desc]'.
Why this helps
Important PR changes can happen without anyone reopening the related content review.
- Connects workflow changes to content follow-up.
- Surfaces recent documents when readiness shifts.
- Reduces missed review moments during busy launches.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Prismic once through the Notis portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: When a GitHub pull request property changes, retrieve the recently updated Prismic documents related to it and explain whether a release content review is needed.
- 4Choose the pull request properties changed trigger and select a channel for run reports.
- 5Test it with one PR changing from draft to ready for review.
Questions about this workflow
Which PR changes are useful?
Draft status, labels, reviewers, merge state, and base branch changes are especially useful signals.
Does it block the PR?
No. It provides context and a follow-up suggestion without changing GitHub or Prismic state.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Prismic. A trigger fires from one place; an action lands in another.
GitHub triggers
Prismic actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Prismic Documents with Fulltext Search
Tool to fetch prismic documents using a full-text search predicate. use after obtaining the repository's master ref when you want to search for specific terms within documents.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Content API: Get Documents with Integration Fields
Tool to fetch prismic documents including integration fields data. use when you need both core content and integration fields in one query. call after obtaining a valid ref token.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Get Prismic Documents with Predicates
Tool to fetch prismic documents using specified predicates. use when filtering documents based on multiple conditions after obtaining the repository's master ref.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Prismic: Query Documents
Tool to query prismic documents using predicates and pagination. use when you need to fetch multiple documents from a repository after obtaining a ref.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Prismic Document by ID
Tool to retrieve a specific prismic document by its id. use after obtaining a content ref.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Prismic: Get Documents by Custom Field
Tool to fetch prismic documents by custom field predicate. use after obtaining a repository ref when filtering content by field constraints.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Get Prismic Documents by Tag
Tool to fetch prismic documents by tag. use when retrieving all documents associated with a specific tag.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Get Prismic Documents by Type
Tool to fetch prismic documents by type. use when you need to retrieve documents with a specific custom type after obtaining the repository's master ref.
Connect any two apps with Notis in the middle.
GitHub and Prismic, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Prismic.