Keep Flowise tool metadata in step with issue changes
A tool name or description change can slip through when it is recorded in one place. Connect that request to a focused Flowise metadata update.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Update Tool By ID
Tool to update a specific tool by its ID. Use when you need to modify existing tool metadata after retrieval. Call after confirming the fields you want to change.
Why this helps
Tool metadata can become inconsistent with the latest documented requirements when the update depends on manual follow-through.
- Carry documented changes into Flowise metadata.
- Reduce small but distracting maintenance tasks.
- Keep tool information easier to understand.
Setup
Build it in a few focused steps.
- 1Connect Linear and Flowiseai to Notis once through the portal.
- 2Create an automation using the portal or a conversational request to Notis.
- 3Use one prompt asking Notis to identify a documented Flowise tool metadata change, retrieve the matching tool, and update its metadata as described.
- 4Select the Linear Issue Updated trigger and choose a channel for run reports.
- 5Test with an issue update that describes one specific metadata change.
Questions about this workflow
Does this change tool behavior?
This action updates tool metadata. The prompt should describe only the metadata change intended.
What helps identify the correct tool?
Include a clear name or identifier in the issue context and describe the matching approach in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Flowiseai. A trigger fires from one place; an action lands in another.
Linear triggers
Flowiseai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clone Chatflow
Tool to clone an existing chatflow. Use when you need to duplicate a chatflow by its ID.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Chatflow
Tool to create a new chatflow in FlowiseAI. Use when you need to programmatically set up chatflows with custom configuration. Call after preparing the chatflow parameters.
Comment Received Trigger
Triggered when a comment is received.
Delete Chatflow
Tool to delete a chatflow by its ID. Use after confirming the chatflow ID is correct.
Issue Created Trigger
Triggered when a new issue is created.
Delete Chat Messages
Tool to delete chat messages for a specific chatflow. Use when you need to remove messages based on optional filters. Use after confirming the chatflow ID.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Delete Tool By ID
Tool to delete a specific FlowiseAI tool by ID. Use after confirming the tool ID is correct.
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).
Export Chatflow
Tool to export a chatflow by its ID. Use after confirming the chatflow exists.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Get All Chatflows
Tool to retrieve all chatflows. Use when you need to list existing chatflows after authentication.
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 Single Chatflow
Tool to retrieve a chatflow by its ID. Use when you have a chatflow ID and need its full details.
Connect any two apps with Notis in the middle.
Linear and Flowiseai, 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 Flowiseai.