Start new Notion intake with customer context
Creating a new intake database can prompt Notis to retrieve customer records for reference.
Trigger
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.
Action
Get Customers
Tool to retrieve a list of customers. use after authenticating with your api key.
Why this helps
Setting up a new workflow from scratch can mean forgetting the customer context already available elsewhere.
- Bring existing customer context into new intake planning.
- Reduce manual searching during workflow setup.
- Make a new database easier to connect to ongoing customer work.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ascora to Notis once.
- 2Create an automation in the portal or ask Notis in plain language to create it.
- 3Tell Notis to retrieve Ascora customers after a new Notion database is created and provide a concise reference summary.
- 4Pick the Database Created trigger and choose where run reports should appear.
- 5Test by creating a suitable database and reviewing the customer summary.
Questions about this workflow
Does this trigger when I add a data source to an existing database?
No. This trigger is for creation of a database container; adding a data source to an existing database is a different event.
Does the workflow change customer records?
No. Its Ascora action retrieves customer records for reference.
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.