Give every new Notion database a clear purpose
A database is easier to use when its purpose is clear. Get a draft statement and a few questions to shape it thoughtfully.
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
Create Chat Completion
Tool to create a chat completion using DeepSeek models (deepseek-chat or deepseek-reasoner). Use when you need to generate AI responses to chat conversations. Supports streaming, tool/function calling, and various parameters to control generation behavior (temperature, max_tokens, etc.).
Why this helps
Databases created in the moment can lack a shared purpose and become harder to maintain.
- Clarify intended use while the database is new.
- Create language to share with collaborators.
- Surface decisions worth making before adding lots of data.
Setup
Build it in a few focused steps.
- 1Connect Notion and DeepSeek to Notis once in the portal.
- 2Create an automation in the portal or describe the purpose-drafting outcome to Notis.
- 3Ask DeepSeek in one instruction for a concise purpose statement and a few clarifying questions based on available database context.
- 4Choose the Notion Database Created trigger and select where run reports should appear.
- 5Test by creating a database container and reviewing the draft for accuracy.
Questions about this workflow
Does this fire for a new data source inside an existing database?
No. Database Created fires for the container creation event. Use Data Source Created for a new data source added to an existing database.
Will it populate a database description?
The listed DeepSeek action creates a model response; this workflow does not imply that it writes the response into Notion.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to DeepSeek. A trigger fires from one place; an action lands in another.
Notion triggers
DeepSeek actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Anthropic Message
Tool to create a model response using DeepSeek's Anthropic-compatible API format with support for system prompts, tool calling, streaming, and thinking mode. Use when you need to generate chat completions using the Anthropic Messages API format. Requires base_url='https://api.deepseek.com/anthropic' or metadata base_url ending with '/anthropic'. Supports extended thinking, function calling with tools, and streaming responses. Note: Images and documents are not supported in content blocks.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Chat Completion
Tool to create a chat completion using DeepSeek models (deepseek-chat or deepseek-reasoner). Use when you need to generate AI responses to chat conversations. Supports streaming, tool/function calling, and various parameters to control generation behavior (temperature, max_tokens, etc.).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get User Balance
Tool to get user's current account balance including granted and topped-up balances with detailed breakdown by currency (CNY or USD). Use when you need to check if the user has sufficient balance for API calls or to view detailed balance information.
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.
List Models
Tool to list currently available DeepSeek models and provides basic information about each one such as the owner and availability. Use when you need to discover which models are available for API calls.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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 DeepSeek, 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 DeepSeek.