Turn onboarding notes into a device enrollment handoff
When a new hire's Notion onboarding record appears, ask JumpCloud to register their system and report whether agent installation is needed.
Trigger
New Page
Triggers when a new page is added to a Notion database.
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
New hire setup gets split across onboarding notes and device administration, making it easy to forget the enrollment handoff.
- Starts the enrollment request from the onboarding item already being maintained.
- Surfaces the API limitation that a device must be enrolled through agent installation.
- Keeps the next action and run result in one place.
Setup
Build it in a few focused steps.
- 1Connect Notion and JumpCloud to Notis once through the portal.
- 2Create an automation in the portal, or ask Notis conversationally to start device enrollment from a new onboarding item.
- 3Use a plain-language instruction to attempt system registration and report that agent installation is required if the API cannot create it.
- 4Select the Notion New Page trigger and choose a channel for run reports.
- 5Test with one real onboarding page and confirm the enrollment handoff is clear.
Questions about this workflow
Does this automation install the JumpCloud agent?
No. The Create System API action cannot create a system. Agent installation is required to enroll a device; this workflow can surface that requirement and report the attempted handoff.
Which Notion event starts it?
A new page is added to a Notion database.
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.