Prepare customer follow-up from a Notion discussion
When a customer-related discussion gets a new comment, let Notis retrieve Ascora customer records for reference.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Get Customers
Tool to retrieve a list of customers. use after authenticating with your api key.
Why this helps
Customer details can live in a separate system, making a simple discussion follow-up feel like several tasks.
- Bring customer records into view when a page discussion needs follow-up.
- Reduce manual lookups between tools.
- Keep the customer context connected to the original discussion.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ascora to Notis once, with Notion comment access enabled.
- 2Create an automation in the portal or ask Notis conversationally to build it.
- 3In one plain-language instruction, ask Notis to retrieve Ascora customers after a relevant comment on the selected Notion page and summarize possible matches for review.
- 4Choose the New Comment trigger for the specified page and select a reporting channel.
- 5Test with one real customer-related comment and inspect the results.
Questions about this workflow
Does this change Ascora customer records?
No. The available action retrieves customer records so you can review them.
Can it focus on a single discussion page?
Yes. The New Comment event can be configured for a specified Notion block or page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ascora. A trigger fires from one place; an action lands in another.
Notion triggers
Ascora actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Customer
Tool to delete a specific customer by id. use when you need to remove a customer after confirming its existence.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Quotation
Tool to create a new quotation. use when submitting a customer quote request via the ascora api.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Customer
Tool to delete a specific customer by id. use after confirming the customer exists.
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 Customers
Tool to retrieve a list of customers. use after authenticating with your api key.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Jobs
Tool to retrieve jobs. use when you need to filter and paginate job listings from ascora.
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.
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.
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 Ascora, 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 Ascora.