Bring the Requested Content Item Into Review
Let an existing review signal bring the right CMS item into view.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Content Item
Tool to retrieve a specific content item by its identifier. use after confirming the environment id and item identifier.
Why this helps
Review requests from other systems can create a separate search task before anyone can respond.
- Connect an external review signal to a focused item lookup.
- Reduce manual retrieval before a content decision.
- Keep the requested item details available in the run report.
Setup
Build it in a few focused steps.
- 1Connect Kontent.ai to Notis once in the portal.
- 2Create an automation in the portal or ask Notis in plain language, then configure an incoming webhook trigger.
- 3Write one instruction asking Notis to retrieve the content item clearly identified by the external review request and summarize it.
- 4Choose a channel for run reports and connect the external tool or backend to the webhook.
- 5Test with one real review request that includes a valid item identifier.
Questions about this workflow
Does Notis create the webhook request?
The webhook trigger starts when an external tool or custom backend sends an HTTP request.
What if the request has no item identifier?
The instruction should have Notis report the missing identifier and avoid retrieving a guessed item.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Kontent ai. A trigger fires from one place; an action lands in another.
Linear triggers
Kontent ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Content Item
Tool to retrieve a specific content item by its identifier. use after confirming the environment id and item identifier.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Language
Tool to retrieve a specific language by its id. supports management api directly and delivery api via normalization.
Comment Received Trigger
Triggered when a comment is received.
Get Language Variant
Tool to retrieve a specific language variant of a content item. use after confirming the item and language identifiers when needing localized content.
Issue Created Trigger
Triggered when a new issue is created.
List Content Items
Tool to list content items from the delivery api. use when fetching content items for a specified environment, optionally providing a continuation token for pagination.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
List Content Types
Tool to list content types within a kontent.ai environment. use when you need to retrieve a paginated list of content type definitions. use after confirming the environment id.
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).
List Languages
Tool to list languages in a kontent.ai project. use when you need to retrieve all languages for a specified environment after confirming the project id.
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 Kontent ai, 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 Kontent ai.