Answer workspace requests with a Contentful space list
A workspace request can start with a simple question: which spaces can we use? Have Notis return the accessible list when your system sends the request.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Workspace questions can sit unanswered while someone switches tools and checks access manually.
- Give workspace requests a consistent response.
- Reduce manual checks during intake.
- Help requesters choose a next step sooner.
Setup
Build it in a few focused steps.
- 1Connect Contentful to Notis once through the portal.
- 2Create an automation with a prompt to list accessible Contentful spaces when a workspace request arrives.
- 3Select an incoming webhook trigger and choose a channel for run reports.
- 4Send one real test request from the connected backend and review the result.
Questions about this workflow
What starts this workflow?
A connected external tool or custom backend sends an HTTP request to the Notis webhook.
Does this verify permissions on a specific space?
It lists spaces accessible to the connected Contentful account. It does not change permissions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Contentful. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
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.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear 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.