Connect Notion to NocoDB
When something happens in Notion, Notis takes the next step in NocoDB. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to NocoDB
Review NocoDB schema after a Notion structure change
When a Notion data source changes columns, retrieve the related NocoDB table schema so you can review whether its structure still supports the workflow.
Check the matching NocoDB table when a database is created
When a Notion database container is created, retrieve the intended NocoDB table schema as a setup reference for the new workflow.
Surface the NocoDB schema for a new Notion data source
When a Notion data source is created, retrieve the corresponding NocoDB table schema so its structure is available during setup.
Check NocoDB sort settings when a Notion view is added
When a Notion view is created, retrieve the relevant NocoDB sort metadata to support a deliberate review of how related information is ordered.
Review grouped NocoDB records when a Notion item is added
When a new page is added to a Notion database, retrieve grouped data from the related public NocoDB view to support a quick comparison.
Bring a page attachment into NocoDB after content changes
When a Notion page body changes, ask Notis to identify a relevant remote attachment URL and upload it to the intended NocoDB storage.
Escalate a technical issue raised in a Notion comment
When a Notion comment reports a technical issue in a connected workflow, submit a structured error report to NocoDB for investigation.
Escalate a defect comment from a tracked Notion page
When a comment is added to a specified Notion page or block and reports a defect, send a NocoDB error report with the available context.
Review NocoDB ordering after a Notion property change
When a Notion page property changes, retrieve the related NocoDB sort metadata to check whether the companion view still supports the intended workflow.
Supported Triggers and Actions
Notis builds workflows that link Notion to NocoDB. A trigger fires from one place; an action lands in another.
Notion triggers
NocoDB actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get User Info
Tool to get authenticated user information including email, name, roles, and profile details. Use when you need to verify user authentication or retrieve the current user's profile information.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Forgot Password
Tool to initiate password reset process by sending a reset email to the user. Use when a user has forgotten their password and needs to receive a password reset link via email.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Sign Out User
Tool to sign out the authenticated user and clear their refresh token from the database and cookie. Use when you need to invalidate a user's authentication session and log them out of the NocoDB application.
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 Sort Metadata
Tool to retrieve sort configuration by ID from NocoDB. Use when you need to get details about how data is ordered in a specific view.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Update View Column
Tool to update a column configuration in a view. Use when you need to change column visibility, order, or width in a specific view.
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.
Delete View
Tool to delete a view from a NocoDB table. Use when you need to permanently remove a view. This action cannot be undone.
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.
Delete Table View Row
Tool to delete a specific row from a table view in NocoDB. Use when you need to remove a single record from a view.
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.
Get Integration Info
Tool to retrieve metadata for a specific NocoDB integration by type and subtype. Use when you need to get integration configuration schema, display information, or available capabilities for an integration.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and NocoDB
Connect any two apps with Notis in the middle.
Notion and NocoDB, 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 NocoDB.