Rebrands That Sync Instantly Across Contentful
Brand rebrand happens? All your Contentful spaces update automatically. No scrambling to rename things manually.
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
During a rebrand, manually updating space names across many Contentful instances is error-prone and easy to forget, leaving outdated names in place.
- All spaces update simultaneously
- No risk of forgotten spaces with old brand names
- Rebrand feels complete and coordinated
- Reduces coordination overhead during transitions
Setup
Build it in a few focused steps.
- 1Connect Contentful to Notis (one-time setup).
- 2Set up a webhook trigger from your internal rebrand announcement channel or system.
- 3Tell Notis: 'When the rebrand is announced, rename all Contentful spaces that contain [OldBrandName] to [NewBrandName]' (or by pattern).
- 4Choose where Notis confirms all renames were successful (Slack, email, internal updates).
- 5Test by running a dry-run or simulation to verify the rename pattern works as expected.
Questions about this workflow
Can I control which spaces get renamed?
Yes. Specify spaces by name pattern, ID, or other criteria. You can exclude legacy or external spaces from the rebrand sync if needed.
What if some spaces have complex naming schemes?
Describe the naming pattern in your automation prompt, and Notis will interpret and update accordingly. For example, 'Rename spaces that start with [Brand]- to [NewBrand]-'.
Are there any limits to how many spaces I can rename at once?
Contentful doesn't limit batch renames, and Notis will process them systematically and confirm completion.
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.