Content Freezes That Are Visible and Enforced
Content freeze starts? Spaces are automatically labeled to show freeze status. Team sees it immediately and knows not to publish.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update space
Updates the name of a specific space. notes: - the version number is required to ensure you're updating the latest version of the space. - you can get the current version from the sys.version field when fetching space details. - only the name of the space can be updated.
Why this helps
Content freeze periods are announced but team members forget or miss the announcement, leading to accidental publishing during freeze.
- Freeze status is obvious to all team members
- Reduces accidental publishing during freeze
- Visual reminder in space names
- Team coordination improved
Setup
Build it in a few focused steps.
- 1Connect Contentful and your process calendar/announcement system to Notis (one-time setup).
- 2Set up a webhook that fires when a content freeze period begins.
- 3Tell Notis: 'When content freeze starts, rename spaces to prefix them with [FROZEN] or [DO NOT PUBLISH]'.
- 4Choose where Notis confirms the freeze labeling (team Slack, email, etc.).
- 5Test by triggering a freeze and verifying spaces are renamed to show freeze status.
Questions about this workflow
Does this actually prevent publishing?
It labels the spaces to warn team members. Actual publish prevention requires additional Contentful permissions configuration, but the label is a powerful visual cue.
What label should I use?
Use a prefix like [FROZEN], [FREEZE], or [DO-NOT-EDIT]. Keep it obvious so team members see it immediately.
How do I remove the label when freeze ends?
Create a companion automation for freeze end, or manually remove the prefix. Both are quick one-time actions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Postiz to Contentful. A trigger fires from one place; an action lands in another.
Postiz triggers
Contentful actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get space
Retrieves details of a specific space by its id. this action is used to get information about a single space in contentful.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List spaces
Lists all spaces that the authenticated user has access to in contentful. this is a fundamental operation needed before performing any other content management actions since most operations require a space id.
Update space
Updates the name of a specific space. notes: - the version number is required to ensure you're updating the latest version of the space. - you can get the current version from the sys.version field when fetching space details. - only the name of the space can be updated.
Connect any two apps with Notis in the middle.
Postiz and Contentful, 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.