Keep private device work moving after updates
When sensitive setup details change, Notis can carry the issue context into the JumpCloud attempt and report back.
Trigger
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Action
Create System
Tool to register a new system. Use when attempting to create a system via API. Note: JumpCloud does not support system creation through its REST API. Use agent installation to enroll systems.
Why this helps
Private operational work is harder to keep in view when important changes must be checked across multiple tools.
- Use private issue changes to begin the right follow-up.
- Keep the connected user's visibility model for private team events.
- Make the system enrollment constraint hard to miss.
Setup
Build it in a few focused steps.
- 1Connect Linear and JumpCloud to Notis once and ensure the Linear account can see the private team.
- 2Create an automation named private device setup changes.
- 3Write one plain-language instruction for attempting JumpCloud system creation after a private device issue changes and reporting that enrollment needs the agent.
- 4Select the Linear Private Team Issue Properties Updated trigger and choose a channel.
- 5Test on one real private-team update.
Questions about this workflow
Who can this private trigger see?
It polls using the connected user's token, so it sees private teams available to that user.
Can the action enroll a system through REST?
No. JumpCloud does not support system creation through its REST API; agent installation enrolls systems.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Jumpcloud. A trigger fires from one place; an action lands in another.
Linear triggers
Jumpcloud actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create System
Tool to register a new system. Use when attempting to create a system via API. Note: JumpCloud does not support system creation through its REST API. Use agent installation to enroll systems.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Role
Tool to delete a specific JumpCloud role by its ID. Use when you need to remove a role after confirming the ID. Call only after ensuring the role is no longer assigned.
Comment Received Trigger
Triggered when a comment is received.
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 Jumpcloud, 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 Jumpcloud.