Give Notion decisions a trackable next step
Turn the next action from a project decision into work that is ready to track in Everhour.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Create Task
Tool to create a new task in a project. use when you need to quickly add a task under a specific project id. example: "create a task named 'write tests' in project proj 123456".
Why this helps
A decision can feel complete while its follow-up remains buried in notes.
- Connect decisions to actionable tracked work.
- Reduce reliance on memory after planning.
- Make follow-through easier to locate.
Setup
Build it in a few focused steps.
- 1Connect Notion and Everhour to Notis once in the portal.
- 2Create an automation in the portal or tell Notis how to handle decision updates.
- 3Use one instruction asking Notis to create an Everhour task when a decision page gains a clear next action.
- 4Choose the Notion Page Content Updated trigger for the decisions page and a reporting channel.
- 5Test with a real decision update and check the resulting task.
Questions about this workflow
What counts as a clear next action?
Describe the kind of commitment that should become a task in the automation prompt.
Can this watch a single decision page?
Yes. Scope Page Content Updated to that page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Everhour. A trigger fires from one place; an action lands in another.
Notion triggers
Everhour actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Client
Tool to create a new client in everhour. use when you need to add a client before tracking time or assigning it to projects.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete a client
Tool to delete a client. use when you need to permanently remove a client from everhour after confirming the client id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Clients
Tool to list all clients. use when you need an overview of workspace clients.
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.
List Expenses
Tool to retrieve all expenses. use when you need to review expense records across your workspace.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Client by ID
Tool to retrieve a specific client by id. use when you need detailed client information after obtaining the client's id.
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 Project
Tool to retrieve a specific project. use after you have the project id if you need its details.
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 Section
Tool to retrieve a specific section. use when you need detailed section data by its id.
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.
Get Authenticated User Profile
Tool to retrieve profile information of the authenticated user. use after providing api key to fetch current user's profile details.
Connect any two apps with Notis in the middle.
Notion and Everhour, 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 Everhour.