Recheck tracking projects when your task structure changes
A small schema change can affect how work is organized. Ask Notis to bring the active DeskTime project list into view.
Trigger
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.
Action
Get Projects List
Tool to retrieve all active projects for the company, including related tasks. use when you need projects overview after authentication.
Why this helps
Changing a task database can leave project tracking conventions out of sync with the way work is now organized.
- Create a review cue when the structure of work changes.
- Bring the active DeskTime project list into the follow-up.
- Avoid relying on memory to revisit tracking conventions.
Setup
Build it in a few focused steps.
- 1Connect Notion and DeskTime to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally to set one up.
- 3In one instruction, ask Notis to retrieve the active DeskTime project list and summarize it for review when the relevant Notion schema changes.
- 4Select the Notion Data Source Schema Updated trigger and choose where run reports should go.
- 5Test with a real schema update or confirm the intended data source scope before relying on it.
Questions about this workflow
Does this create or change DeskTime projects?
No. This workflow retrieves the active project list for review; the available action does not edit existing projects.
Why use a schema trigger?
It signals a structural change, such as adding, removing, or renaming a column, which can warrant reviewing tracking conventions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Desktime. A trigger fires from one place; an action lands in another.
Notion triggers
Desktime actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Project with Optional Task
Tool to create a new project with an optional initial task. use when you need to set up a new desktime project programmatically.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account Details
Tool to retrieve detailed information about the authenticated user's company account. use after confirming the api key is valid to fetch company name, work settings, account timezone, and timestamp.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get All Company Employees
Tool to list all employees in the company, including their roles and statuses. use after confirming valid credentials to fetch the organization’s roster.
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.
Get Employee Data
Tool to fetch data for all employees within the company. use after verifying the api key is valid.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Employee Projects
Tool to retrieve information about projects assigned to employees, including project names, durations, and statuses. use when you need to fetch per-employee project tracking data for a specific date.
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.
Get Employee Projects and Apps
Tool to retrieve an employee's tracked projects and application usage. use when you need combined project/app time data for a given employee and date (defaults to current user and today). example: "get projects and apps for employee 711867 on 2025-07-28."
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.
Get Projects List
Tool to retrieve all active projects for the company, including related tasks. use when you need projects overview after authentication.
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.
Ping DeskTime API
Tool to check the api's availability and confirm the service is operational. use when you need to verify that the desktime api is reachable and responsive.
Connect any two apps with Notis in the middle.
Notion and Desktime, 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 Desktime.