Find the right Appointo service from a Notion intake
Let a service request prompt a quick Appointo product lookup, with unclear matches flagged for review.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
List Products
Tool to fetch all available products. Use when browsing products with optional paging and search. Call after authenticating with Appointo API.
Why this helps
Founders can lose time searching a service catalogue every time an intake request uses different wording.
- Reduce repeated browsing of the service catalogue.
- Spot requests that do not clearly match an available service.
- Keep intake review focused on exceptions.
Setup
Build it in a few focused steps.
- 1Connect Notion and Appointo to Notis once through the portal.
- 2Create an automation in the portal or tell Notis what it should do conversationally.
- 3Write one instruction asking Notis to look up Appointo products for each new service intake and report likely matches or ambiguity without booking.
- 4Select the Notion New Page trigger and choose a channel for run reports.
- 5Test with one real intake request and verify the product result.
Questions about this workflow
Will Notis select a service when wording is unclear?
Instruct Notis to report multiple plausible matches or no match for human review instead of guessing.
Does this create a booking?
No. This workflow looks up products and reports the result. A booking requires a separate clear instruction and availability check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Appointo. A trigger fires from one place; an action lands in another.
Notion triggers
Appointo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Authenticate Appointo API Token
Tool to authenticate with the Appointo API by validating the APPOINTO-TOKEN header. Use when verifying the token before subsequent API calls.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Cancel Booking
Tool to cancel a booking or selected customers. Use when you need to revoke an entire booking or individual attendees after verifying booking details. Use after retrieving booking information.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Booking
Tool to create a new booking. Use when scheduling a customer booking after confirming appointment availability.
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 Appointment Availability
Tool to get calendar availability for a specific appointment. Use when you need to fetch available time slots for an appointment within a date range.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Appointments
Tool to list appointments. Use when fetching appointments with optional filters and pagination after confirming a valid API token.
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.
List Bookings
Tool to list bookings. Use when you need to fetch bookings filtered by status, paging, or search term.
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.
List Products
Tool to fetch all available products. Use when browsing products with optional paging and search. Call after authenticating with Appointo API.
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.
List Subscription Contracts
Tool to list subscription contracts. Use when retrieving contracts with optional search after confirming a valid API token.
Connect any two apps with Notis in the middle.
Notion and Appointo, 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 Appointo.