Move hardware requests toward enrollment
Let a new hardware issue start the JumpCloud follow-up, with a clear report about what system enrollment still needs.
Trigger
Public Team Issue Created
Fires when a new issue is created in a Linear *public* team. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_CREATED`.
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
Hardware requests can sit between issue tracking and device management while a founder tries to remember the next action.
- Start provisioning follow-up as soon as a request is logged.
- Keep the request's context with its Linear issue.
- Show that the JumpCloud agent is required for enrollment.
Setup
Build it in a few focused steps.
- 1Connect Linear and JumpCloud to Notis once.
- 2Create an automation in the portal named public team hardware follow-up.
- 3Ask Notis in one prompt to attempt JumpCloud system creation for each new public-team hardware request and report the agent enrollment requirement.
- 4Pick the Linear Public Team Issue Created trigger and select a run-report channel.
- 5Test with one real hardware request.
Questions about this workflow
Does public-team mean everyone can see the resulting system?
The trigger covers issues in public Linear teams; access and visibility in JumpCloud remain governed by JumpCloud.
Can the API action complete enrollment?
No. JumpCloud does not support system creation through its REST API. Systems are enrolled through agent installation.
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.