Refresh availability when plans change
When a planning page changes, have Notis check eTermin working times so you do not have to remember a separate availability lookup.
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 Working Times
Tool to retrieve working times for a specific calendar. Use when confirming available time slots before booking appointments.
Why this helps
Revised plans often make old availability checks stale, but repeating them manually is easy to forget.
- Refresh availability after meaningful plan edits.
- Avoid relying on outdated scheduling information.
- Keep follow-up lightweight with run reports.
Setup
Build it in a few focused steps.
- 1Connect Notion and eTermin to Notis once through the portal.
- 2Ask Notis to check the relevant eTermin calendar's working times when the planning page content changes and summarize the result.
- 3Select the Notion Page Content Updated trigger, scoped to the planning page if appropriate.
- 4Choose a channel for run reports and test with a real planning update.
Questions about this workflow
Will every page edit trigger a check?
The trigger can be scoped to a specific page or data source where supported, which helps keep the automation relevant.
Does it place a booking?
No. It retrieves working times and reports them for you to use.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Etermin. A trigger fires from one place; an action lands in another.
Notion triggers
Etermin actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Contact
Tool to create a new contact in eTermin. Use when you need to add a contact before scheduling appointments.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create eTermin Resource
Tool to create a new resource. Use when you need to create any eTermin resource (contact, vouchers, resource, appointment).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create User
Tool to create a new user. Use when you need to add users to eTermin after collecting their details.
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.
Create Voucher
Tool to create a new voucher in eTermin. Use when you need to add a voucher after defining its details.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Webhook
Tool to create a new webhook in eTermin. Attempts multiple candidate endpoints since webhook creation is undocumented. Returns a helpful message if UI-only.
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.
Delete Appointment
Tool to delete an appointment. Use when you need to remove an existing appointment by its identifier. Confirm the appointment exists before invoking.
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.
Delete calendar
Tool to delete a calendar. Use when removing an existing calendar by its identifier.
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.
Delete Contact
Tool to delete a contact. Use when you need to remove a contact by its ID after confirming it exists.
Connect any two apps with Notis in the middle.
Notion and Etermin, 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 Etermin.