Confirm device setup follow-up with a Telegram tap
Turn a deliberate confirmation into a tidy device setup handoff, with the real enrollment step spelled out.
Trigger
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
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
Founders can lose track of whether a device setup suggestion was actually approved for follow-up.
- Distinguish confirmed device follow-up from casual discussion.
- Pass along setup context while stating the agent requirement.
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 confirmed device setup requests.
- 3Write one plain-language instruction to summarize the confirmed device and attempt system creation only while noting that installing the agent is required for enrollment.
- 4Select Callback Query Received as the trigger and choose a reporting channel.
- 5Test with a real button tap and ensure the report does not claim the device is enrolled.
Questions about this workflow
Will the tap enroll the system in JumpCloud?
No. System creation through the JumpCloud REST API is unsupported. Agent installation is required to enroll a system.
What starts this workflow?
A tap on an inline keyboard button attached to a bot message in Telegram.
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.