Skip to content
Notis

Client Spaces That Set Themselves Up

New client signed? Your Contentful space is already renamed and ready. Zero manual space configuration.

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

Manually creating and naming Contentful spaces for each new client, creating delays in onboarding and risk of naming inconsistency.

  • Clients get ready-to-use spaces instantly
  • No delays waiting for manual setup
  • Consistent naming across all client spaces
  • Reduces repetitive manual work during onboarding

Setup

Build it in a few focused steps.

  • 1Connect Contentful and your client management system to Notis (one-time integrations).
  • 2Set up a webhook that fires when a new client is activated in your system.
  • 3Tell Notis: 'When a new client signs up, rename a Contentful space to [ClientName] Content Space' (specify the naming pattern).
  • 4Choose where Notis confirms the space setup (Slack, email, or internal tool).
  • 5Test with a test client to ensure the space renames with the correct format.

Questions about this workflow

How do I specify which space gets renamed for each client?

You can pre-create client spaces with placeholder names, then Notis renames them when the client launches. Or use a naming convention that Notis recognizes.

Can this set up permissions too?

This automation focuses on space naming. If you need permission setup, you can chain it with a follow-up workflow or manual step.

What if a client name changes?

You can trigger a space rename manually, or create a second automation to update space names when client names change.

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.