Capture device setup needs when a member joins
Give new teammates a clear device setup next step without turning onboarding into another checklist chase.
Trigger
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
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
New members can join the team chat before anyone captures their device setup needs.
- Notice the join event and capture a setup follow-up.
- Make the system enrollment requirement clear in the run report.
Setup
Build it in a few focused steps.
- 1Connect Telegram and JumpCloud to Notis once in the portal.
- 2Create an automation in the portal, or ask Notis to capture device setup follow-up for new group members.
- 3Use one plain-language instruction to summarize available device details and attempt system creation only with the note that agent installation is required for enrollment.
- 4Select New Chat Member as the trigger and choose a channel for run reports.
- 5Test with one real new member event and verify the report avoids claiming a device is enrolled.
Questions about this workflow
Does a member join event include device information?
Not necessarily. The instruction should use only details available in the event and request missing setup information through the appropriate onboarding process.
Does this create a JumpCloud device?
No. The REST API does not support system creation; agent installation is needed to enroll a device.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to Jumpcloud. A trigger fires from one place; an action lands in another.
Telegram 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.
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Connect any two apps with Notis in the middle.
Telegram 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.