Turn role removal approval into a clear action
When a comment records approval to retire a role, have Notis verify the role is no longer assigned before deleting it.
Trigger
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
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
Role cleanup can stall between an approval note and the admin action, leaving unnecessary access structures around.
- Connects an approval discussion to its administrative follow-up.
- Requires a clear role ID and confirmation it is no longer assigned.
- Provides a run report for a sensitive cleanup action.
Setup
Build it in a few focused steps.
- 1Connect Notion and JumpCloud to Notis once through the portal.
- 2Create the automation in the portal or tell Notis to handle explicit role-removal approvals posted as comments.
- 3Use one plain-language instruction to identify the approved role, verify it is no longer assigned, and delete it only when both conditions are clear.
- 4Select Comment Created and choose a channel for run reports.
- 5Test with one real approval comment and a role confirmed to be unassigned.
Questions about this workflow
Will it delete a role from any comment?
The instruction should require an explicit approval and a clear role identifier. If either is missing, it should report that it needs review.
What must be checked before deletion?
Confirm that the role is no longer assigned, then use its specific JumpCloud role ID.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Jumpcloud. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion 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.