Act on role retirement announcements carefully
Turn policy updates into a clear cleanup step with checks before role deletion.
Trigger
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
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 policy changes announced to a team can be missed or acted on before assignments are reviewed.
- Bring role retirement announcements into a consistent review flow.
- Check assignments before removing the obsolete role.
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 retirement notices in your channel.
- 3Write one plain-language instruction requiring a role ID and confirmation it is no longer assigned before deletion.
- 4Select New Channel Post as the trigger and choose a channel for reports.
- 5Test with a real retirement notice and verify that the role is not assigned before allowing deletion.
Questions about this workflow
Can an announcement alone authorize deletion?
Use an instruction that requires a verified role ID and an assignment check. JumpCloud roles should be deleted only after confirming they are no longer assigned.
What channel configuration is needed?
The Telegram bot must be an administrator in the channel.
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.