Handle JumpCloud role removal requests from Telegram
Make access cleanup requests easier to review before a role is removed.
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
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
A quick chat request can lack the details needed to safely identify and retire an access role.
- Keep the request and its reason together for review.
- Require role ID verification and an assignment check before 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 review role removal requests posted to Telegram.
- 3Give Notis one plain-language instruction to identify the requested role, verify its ID and check that it is no longer assigned before attempting deletion.
- 4Select New Message Received as the trigger and choose a channel for run reports.
- 5Test with a real cleanup request and verify the role ID and assignment status before relying on the action.
Questions about this workflow
Will the automation delete any role mentioned casually?
The instruction should require an explicit removal request, verified role ID, and confirmation that the role is no longer assigned. Deletion should happen only after those checks.
Can it remove a role that is still assigned?
No. The JumpCloud action is intended only for a role confirmed to be unassigned.
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.