Skip to content
Notis

Spaces That Stay Synchronized With Your Projects

The moment a project launches, your Contentful space is automatically renamed to match. No manual updates, no naming drift.

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

Project names and Contentful space names get out of sync, causing team confusion about which space corresponds to which project.

  • Spaces always match project names
  • Eliminates team confusion about which space to use
  • Reduces time spent searching for the right space
  • Keeps naming consistent as projects evolve

Setup

Build it in a few focused steps.

  • 1Connect Contentful to Notis in the portal (one-time setup).
  • 2Set up a webhook trigger: when your project management system signals a project launch, Notis receives the notification.
  • 3Create the automation with plain language: 'When a project launches, rename the corresponding Contentful space to match the project name'.
  • 4Choose where Notis notifies you of successful renames (Slack, email, etc.).
  • 5Test by launching a test project and verifying the space name updates automatically.

Questions about this workflow

How does Notis know which space to rename?

You specify this in the automation setup - either by space ID, or by naming convention. For example, 'rename the space that starts with Dev-' or 'use space ID xyz123'.

What if I don't have a project management webhook?

You can also trigger this via a manual webhook request from any tool that supports HTTP calls, or ask Notis to suggest the best integration for your workflow.

Is the old space name preserved anywhere?

The space ID remains the same; only the display name changes. Contentful tracks version history, so you can see what it was called before.

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.

TriggerScheduled

Get space

Retrieves details of a specific space by its id. this action is used to get information about a single space in contentful.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

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.

ActionInstant

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.