Give journal reflections a gentle structure
When writing feels open-ended, a few relevant prompts can help. Notis can check your Exist attribute metadata and offer optional questions alongside a journal edit.
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
Get User Attributes
Tool to retrieve a paged list of the user's attributes without values. use when you need metadata on available attributes for filtering or selection.
Why this helps
Open-ended journaling can take more energy than you have available for reflection.
- Get a few prompts tied to available attributes.
- Reduce the effort of deciding what to reflect on.
- Keep the questions optional and concise.
Setup
Build it in a few focused steps.
- 1Connect Notion and Exist to Notis once in the portal.
- 2Create an automation in Automations or describe it to Notis in plain language.
- 3Ask Notis to review relevant Exist attribute metadata after journal content changes and suggest up to three optional prompts.
- 4Select Notion's Page Content Updated trigger for your journal page and choose a run-report channel.
- 5Edit one journal entry to test.
Questions about this workflow
Does the automation analyze the journal text inside Exist?
No. The available Exist action retrieves attribute metadata; it does not send journal content to Exist.
Can the prompts stay low-pressure?
Yes. Ask for optional questions and specify a small number in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Exist. A trigger fires from one place; an action lands in another.
Notion triggers
Exist actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get User Profile
Tool to retrieve the authenticated user's profile details and preferences. use after authentication to inspect account settings and status.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Exist OAuth2 Authorize
Tool to initiate the oauth2 authorization flow for user consent. use when you need an authorization code before exchanging for an access token.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Exist OAuth2 Authorize
Tool to initiate the oauth2 authorization flow for user consent. use when you need to obtain an authorization code before exchanging for an access token.
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 Attribute Templates
Tool to retrieve a paged list of supported attribute templates. use when you need to browse available templates before creating or updating data.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Correlations
Tool to retrieve a paginated list of recent correlations. use when exploring relationships between your tracked attributes, optionally filtering by strength or attribute.
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 User Attributes
Tool to retrieve a paged list of the user's attributes without values. use when you need metadata on available attributes for filtering or selection.
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 User Profile
Tool to retrieve the authenticated user's profile details and preferences. use after authentication to inspect account settings and status.
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 Exist, 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 Exist.