Confirm JumpCloud role cleanup with a Telegram tap
Add a deliberate confirmation step to role cleanup so an accidental mention does not trigger removal.
Trigger
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Action
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.
Why this helps
Access cleanup can be risky when a casual message is mistaken for a final decision.
- Separate a proposed cleanup from a confirmed decision.
- Keep role ID and assignment checks ahead of deletion.
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 handle confirmed role cleanup button taps.
- 3In one plain-language instruction, require the tapped confirmation, a verified role ID, and confirmation that the role is unassigned before deletion.
- 4Select Callback Query Received as the trigger and choose the run report channel.
- 5Test with one real confirmation button and verify the role details before acting.
Questions about this workflow
What does a callback query represent?
It is received when a user taps an inline keyboard button attached to one of the bot's Telegram messages.
Is a button tap enough to delete a role?
No. The instruction should also require a verified JumpCloud role ID and confirmation that the role is no longer assigned.
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.