Keep private device requests visible
A private team can track sensitive device work in Linear and still give the founder a concise enrollment follow-up.
Trigger
Private Team Issue Created
Fires when a new issue appears 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
Sensitive requests are easy to lose in private team workflows when provisioning steps require checking another service.
- Bring private-team request context into the provisioning attempt.
- Keep run reports in the channel that suits the team.
- Make the separate agent enrollment step explicit.
Setup
Build it in a few focused steps.
- 1Connect Linear and JumpCloud to Notis once, with access to the relevant private team.
- 2Create a portal automation named private team device enrollment.
- 3Write one instruction asking Notis to attempt JumpCloud system creation for a new private-team device request and explain the agent requirement in its report.
- 4Select the Linear Private Team Issue Created trigger and choose a reporting channel.
- 5Test with one real private-team request.
Questions about this workflow
Can the trigger see private team issues?
The private-team trigger polls with the connected user's Linear token, so visibility follows that user's access.
Will JumpCloud create a system from the issue?
The action can attempt it, but JumpCloud does not support system creation via REST API. Agent installation is needed to enroll a system.
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.