Check related Contentful content as soon as a pull request opens
Keep code review and content review in sync with a concise summary of the relevant Contentful entry.
Trigger
New Pull Request Created
Triggers when a new pull request is created in GitHub, matching the optional configured filters. Emits an event for each newly created pull request. Supports filtering by repository, owner/organisation, author, assignee, label, state, base branch, head branch, and draft status.
Action
GraphQL Content API Query
Tool to execute a GraphQL query against a specified space and environment. Use when fetching Contentful content via GraphQL after obtaining or providing a valid token.
Why this helps
Reviewers may not know whether a code change depends on content that is missing, incomplete, or ready to check.
- Find related content without switching apps to search manually.
- Give reviewers a concise content context summary.
- Surface missing or incomplete content early.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Contentful graphql once in the Notis portal.
- 2Create an automation by telling Notis in plain language or using Automations, New Automation in the portal.
- 3Describe the outcome in one instruction: use the pull request details to find relevant Contentful content and summarize its review readiness.
- 4Pick the New Pull Request Created trigger and choose where run reports should go.
- 5Test with one real pull request and review the result.
Questions about this workflow
Does this publish or change Contentful content?
No. The available Contentful action runs a GraphQL query to fetch content. The automation can summarize results but cannot publish or update entries.
How does it identify the related entry?
Notis can use details in the pull request to form a query when the relevant identifiers or matching content are available. If the relationship is not represented in the available data, provide a matching rule in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Contentful graphql. A trigger fires from one place; an action lands in another.
GitHub triggers
Contentful graphql actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get CMA Token
Tool to retrieve a Contentful Management API (CMA) access token. Use when making CMA calls to ensure valid authorization.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
GraphQL Content API Persisted Query
Tool to execute a persisted GraphQL query via its SHA256 hash. Use after registering a query hash to run cached queries by hash. On first call include full query text; thereafter invoke with only hash and variables.
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.
GraphQL Content API Query
Tool to execute a GraphQL query against a specified space and environment. Use when fetching Contentful content via GraphQL after obtaining or providing a valid token.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Contentful graphql, 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 Contentful graphql.