Find appointment availability from a Notion comment
Ask about a time in the work already happening in Notion and have Notis check eTermin working times for you.
Trigger
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.
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
Scheduling questions interrupt focused work when you have to leave Notion, look up availability, then return with an answer.
- Reduce context-switching during scheduling conversations.
- Get current working-time information into the follow-up.
- Keep a request attached to its Notion context.
Setup
Build it in a few focused steps.
- 1Connect Notion and eTermin to Notis once through the portal.
- 2Ask Notis to check the appropriate eTermin calendar's working times when a scheduling comment requests availability, then report the result in your chosen channel.
- 3Select the Notion Comment Created trigger and choose a channel for run reports.
- 4Test with a real scheduling comment that names the calendar or service clearly.
Questions about this workflow
Does this book an appointment?
No. This workflow checks working times and reports the result so you can decide what to offer.
Can comments trigger it across the workspace?
Yes, the workspace-wide Comment Created event can be used. Reauthorize Notion if its required Read comments capability was enabled after the existing connection.
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.