Give replacement devices a clear enrollment path
When a replacement request changes, let Notis carry the context into JumpCloud and report the practical next step.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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
A replacement laptop can be approved in Linear but still go unenrolled when system registration is left as a separate memory task.
- Keep the latest replacement request attached to its operational follow-up.
- Reduce the mental load of remembering another enrollment handoff.
- Expose the agent installation requirement in the run report.
Setup
Build it in a few focused steps.
- 1Connect Linear and JumpCloud to Notis once.
- 2In the portal, create an automation named replacement laptop enrollment.
- 3Describe in one plain-language prompt how an updated replacement issue should trigger a JumpCloud system creation attempt and what to report if the API cannot create it.
- 4Choose the Linear Issue Updated trigger and a channel for run reports.
- 5Test on one real replacement issue update and review the result.
Questions about this workflow
Will changing an issue install the JumpCloud agent?
No. The action is a system creation attempt, while actual system enrollment requires installing the JumpCloud agent.
Can the prompt explain which changes matter?
Yes. Describe the relevant replacement request context in the prompt; there are no field-mapping screens.
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.