Keep release content aligned with deployment status
Deployment status changes. Your content check follows.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
Get Content Item
Tool to retrieve a specific content item by its identifier. use after confirming the environment id and item identifier.
Why this helps
Deployment updates arrive in one place while the content checklist lives elsewhere and gets postponed.
- Connects deployment signals to content review
- Reduces repeated status checking
- Makes release follow-up more predictable
Setup
Build it in a few focused steps.
- 1Connect GitHub and Kontent.ai to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: “When a new deployment status is created, retrieve the relevant Kontent.ai content item and report what content should be checked for this environment.”
- 4Choose the deployment-status trigger, select a channel for reports, and test with one real deployment.
Questions about this workflow
Can it distinguish staging from production?
Yes. Include the environment in the instruction and ask Notis to tailor the report.
What happens on a failed deployment?
The workflow can report the related content item and highlight that the deployment status needs attention.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Kontent ai. A trigger fires from one place; an action lands in another.
GitHub triggers
Kontent ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Content Item
Tool to retrieve a specific content item by its identifier. use after confirming the environment id and item identifier.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Language
Tool to retrieve a specific language by its id. supports management api directly and delivery api via normalization.
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 Language Variant
Tool to retrieve a specific language variant of a content item. use after confirming the item and language identifiers when needing localized content.
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.
List Content Items
Tool to list content items from the delivery api. use when fetching content items for a specified environment, optionally providing a continuation token for pagination.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List Content Types
Tool to list content types within a kontent.ai environment. use when you need to retrieve a paginated list of content type definitions. use after confirming the environment id.
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.
List Languages
Tool to list languages in a kontent.ai project. use when you need to retrieve all languages for a specified environment after confirming the project id.
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 Kontent ai, 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 Kontent ai.