Skip to content
Notis

Keep new hire device enrollment moving

Capture device setup requests where the team already tracks onboarding, then make the JumpCloud enrollment path easier to follow.

Trigger

Issue Created Trigger

Triggered when a new issue is 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

Device setup can stall when a founder has to copy requests between tools and remember that system enrollment requires the JumpCloud agent.

  • Keep device requests tied to the onboarding work item.
  • Reduce manual handoffs during a busy hiring week.
  • Make the agent-based enrollment requirement clear when the API attempt cannot create the system.

Setup

Build it in a few focused steps.

  • 1Connect Linear and JumpCloud to Notis once in the portal.
  • 2Open Automations, choose New Automation, and name it for new hire device enrollment.
  • 3Write one prompt asking Notis to use a new onboarding issue to attempt JumpCloud system creation and report that agent installation is needed if the API cannot enroll it.
  • 4Select the Linear Issue Created trigger and choose a channel for run reports.
  • 5Test with one real onboarding issue and confirm the report explains the enrollment outcome.

Questions about this workflow

Does this create and enroll the device automatically?

No. JumpCloud does not support system creation through its REST API. The action can attempt creation, but enrolling a system requires installing the JumpCloud agent.

Which Linear issues should start the workflow?

Use the prompt to describe the onboarding request context in plain language. Notis interprets the instruction from each new issue.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

Comment Received Trigger

Triggered when a comment is received.

TriggerInstant

Issue Created Trigger

Triggered when a new issue is created.

TriggerInstant

Issue Updated Trigger

Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.

TriggerInstant

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).

TriggerPolling

Private Team Issue Created

Fires when a new issue appears in a private Linear team (polled with the connected user's token).

TriggerPolling

Private Team Issue Properties Updated

Fires when properties on an issue change in a private Linear team (polled with the connected user's token).

TriggerPolling

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.