Give new Notion intake structures customer context
A new data source can trigger a customer lookup that supports thoughtful intake setup.
Trigger
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.
Action
Get Customers
Tool to retrieve a list of customers. use after authenticating with your api key.
Why this helps
Creating a new table or data source adds setup work that is easy to leave disconnected from customer records.
- Prompt customer context at the point a new data source appears.
- Reduce forgotten setup checks across separate tools.
- Give the person maintaining intake a useful record overview.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ascora to Notis once in the portal.
- 2Create the automation there or ask Notis to set it up conversationally.
- 3In one instruction, ask Notis to retrieve Ascora customers when a Notion data source is created and summarize the records for intake planning.
- 4Select the Data Source Created trigger and choose a run-report channel.
- 5Test by creating one suitable data source and reviewing the summary.
Questions about this workflow
Does a template that creates several data sources run more than once?
It can fire once per data source instantiated by the template, so describe in the instruction how Notis should handle each event.
Will this add customers to Notion?
No. The available action retrieves Ascora customers and can report a summary.
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.