Check related Contentful content after a README update
Keep documentation changes visible alongside potentially related Contentful content.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
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.
Why this helps
A README can change without anyone checking whether associated product or help content still agrees.
- See related structured content after documentation changes.
- Catch possible wording or reference mismatches sooner.
- Create a review summary without manually searching Contentful.
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 changed README details to run a persisted Contentful query and summarize related entries for review.
- 4Pick the GitHub Repository README Changed trigger and choose where run reports should go.
- 5Test with one real README change and review the result.
Questions about this workflow
Can the workflow determine whether the README and entry truly conflict?
Notis can compare the returned content with the README details available in the event, but the result is a review aid. Any matching criteria or product-specific rules should be stated in the instruction.
Does it update the Contentful entry?
No. The available persisted-query action fetches content and returns results; it does not write changes.
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.