Make an ongoing check request stick
If a comment asks to watch for changes, Notis can carry that follow-up into monitoring configuration on the related Kadoa workflow.
Trigger
Comment Received Trigger
Triggered when a comment is received.
Action
Configure Workflow Monitoring
Tool to configure monitoring for a workflow to detect data changes by updating workflow metadata. Use after creating or selecting the workflow.
Why this helps
Requests for ongoing checks often depend on someone remembering to revisit Kadoa later.
- Convert a follow-up request into a monitoring setup action.
- Reduce the mental load of tracking a separate tool task.
- Keep the request linked to its source discussion.
Setup
Build it in a few focused steps.
- 1Connect Linear and Kadoa to Notis once through the portal.
- 2Create an automation through the portal or by asking Notis conversationally.
- 3Write one instruction for configuring monitoring when a comment explicitly requests ongoing change detection for a related workflow.
- 4Select the Linear Comment Received trigger and choose the channel for run reports.
- 5Test with a real comment that names the workflow and change to watch.
Questions about this workflow
Can monitoring be configured without an existing workflow?
This action updates monitoring for a workflow, so an appropriate Kadoa workflow must already exist.
What should the comment contain?
Include the request to monitor, the target workflow context, and the kind of change that matters.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Kadoa. A trigger fires from one place; an action lands in another.
Linear triggers
Kadoa actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Notification Channel
Tool to create a notification channel for alerts delivery.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Enable Data Validation
Tool to enable data validation on a specified workflow. Use after creating or updating a workflow to enforce its validation rules.
Comment Received Trigger
Triggered when a comment is received.
Fetch workflow configuration
Tool to fetch an advanced workflow’s configuration details. Use when you have a workflow ID and need its steps and metadata.
Issue Created Trigger
Triggered when a new issue is created.
Get all locations
Tool to retrieve a list of all available locations. Use when you need to know supported locations before performing location-dependent operations. Use after authenticating with your API key.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get Crawled Page Content
Tool to retrieve content of a crawled page. Use when you need the HTML or Markdown of a page from a specific crawling session.
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).
Get Crawled Pages
Tool to list pages crawled during a session. Use when you need to paginate through results after starting a crawl session.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Get Crawl Status
Tool to fetch current status of a crawling session. Use when you need to check progress of a crawl by its session ID.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Get Notification Event Types
Tool to retrieve supported notification event types. Use when you need to enumerate available notification triggers.
Connect any two apps with Notis in the middle.
Linear and Kadoa, 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 Kadoa.