Start a client review with the Clockify directory ready
Create a client review page in Notion and have Notis fetch the Clockify client list as the review begins.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Get Clients
Tool to list clients in a workspace. use after obtaining a workspace id.
Why this helps
Preparing a client review often means switching tools to find the same directory information before the actual review can start.
- Surfaces Clockify's client directory at the start of a review
- Cuts down on context switching during review preparation
- Provides a repeatable start to periodic client checks
Setup
Build it in a few focused steps.
- 1Connect Notion and Clockify to Notis once through the portal.
- 2Create an automation and write a plain-language prompt asking Notis to retrieve the Clockify client list when a client review page is created.
- 3Select the Notion Page Created trigger and scope it to the client review location if applicable.
- 4Choose where run reports should arrive, then test by creating one real review page.
Questions about this workflow
Does this compare or update client records automatically?
The action retrieves the client list. Ask Notis to present it for review; the listed Clockify action does not update client records.
Can I run this only for review pages?
Use a scoped Page Created trigger if review pages have a dedicated Notion parent page or data source, and state the review-page intent in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Clockify. A trigger fires from one place; an action lands in another.
Notion triggers
Clockify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Client
Tool to add a new client to a workspace. use when you need to create a client in a specific workspace.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Webhook
Tool to create a new webhook in a workspace. use when you want to subscribe to workspace events by registering a callback url.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Client
Tool to delete a client from a workspace. use after archiving the client and confirming no associated data exists.
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.
Delete Webhook
Tool to delete a webhook from a workspace. use when you need to remove an existing webhook by its id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Filter Workspace Users
Tool to filter users in a workspace by advanced criteria. use when you need a paginated, sortable list of workspace users matching multiple filters.
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.
Find All Users On Workspace
Tool to list all users in a workspace. use when you need to retrieve workspace members after confirming the workspace id. example: "find all users on workspace 64a687e29ae1f428e7ebe303."
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.
Find User's Team Managers
Tool to get managers of a user in a workspace. use after confirming workspace and user ids are correct.
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.
Generate New Webhook Token
Tool to generate a new webhook token. use after confirming workspace and webhook ids.
Connect any two apps with Notis in the middle.
Notion and Clockify, 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 Clockify.