Capture device enrollment requests from Telegram
Keep device setup requests in one conversation and make the next enrollment step easy to track.
Trigger
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.
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 requests buried in chat can leave founders unsure which systems still need setup.
- Capture the request without switching tools to rewrite it.
- Keep the agent installation requirement visible before enrollment.
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 enrollment requests from Telegram.
- 3Use one plain-language instruction to summarize the request and attempt system creation only when appropriate, noting that the JumpCloud agent must be installed to enroll the system.
- 4Select New Message Received as the trigger and choose where Notis should report runs.
- 5Test with one real device request and check the run report for the agent installation caveat.
Questions about this workflow
Does this automation enroll a device by itself?
No. JumpCloud does not support system creation through its REST API. The action is an attempt to register a system; enroll the device by installing the JumpCloud agent.
What Telegram messages can start it?
A new message the bot receives in a private chat, group, or supergroup. For every group message, disable Privacy Mode for the bot in BotFather.
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.