Connect Notion to Botsonic
When something happens in Notion, Notis takes the next step in Botsonic. 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 Botsonic
Add approved Notion guides to Botsonic
When a new knowledge article is added to Notion, upload its published URL to the Botsonic bot for training.
Refresh Botsonic when a Notion guide changes
When a Notion page's body content changes, send its URL to Botsonic for training so revisions can reach the chatbot.
Update a Botsonic starter question from a Notion revision
When a Notion page's properties change, ask Notis to update the corresponding Botsonic starter question using its confirmed identifier.
Review Botsonic conversations when Notion feedback arrives
When a new Notion comment captures customer feedback, retrieve Botsonic conversations to help investigate the issue.
Check Botsonic FAQs when a Notion question is raised
When a question is added to a specified Notion page or block, retrieve Botsonic FAQs to check whether the bot already covers it.
Remove a retired source from Botsonic after a Notion page update
When a designated Notion page is updated to retire a source, ask Notis to remove the corresponding Botsonic data after confirming its identifier.
Delete a Botsonic file after a Notion retirement page is created
When a Notion retirement request page is created, remove the specified Botsonic uploaded file only after confirming its file ID.
Remove a retired Botsonic starter question from a Notion task
When a subpage is added under a designated Notion page, remove the corresponding retired starter question after confirming its identifier.
Review Botsonic assets after a Notion knowledge schema change
When a Notion data source schema changes, retrieve Botsonic data for an inventory review before updating dependent knowledge workflows.
Supported Triggers and Actions
Notis builds workflows that link Notion to Botsonic. A trigger fires from one place; an action lands in another.
Notion triggers
Botsonic actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bulk Upload Bot URLs
Tool to bulk upload urls for bot training. use when you need to upsert multiple document urls into a bot in one request.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Bot Data
Tool to delete specific bot data using its id. use when you need to remove outdated or irrelevant data after confirming the data identifier.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Starter Question
Tool to delete a specific starter question by its unique identifier. use after confirming the id of the starter question you want to remove.
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.
Delete Uploaded File
Tool to delete a specific uploaded file by its id. use when you need to remove a file from the bot's data repository after confirming the file id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get All Bot Data
Tool to retrieve all data associated with the bot, including files and resources. use when you need a comprehensive export of bot assets for backup or inspection.
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.
Get All Bots
Tool to retrieve all bots associated with the account. use when you need to list existing bots after authentication.
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.
Get All Conversations
Tool to retrieve all conversations related to the bot. use after authentication when you need a paginated list of conversation threads for review or analytics.
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 All FAQs
Tool to retrieve all frequently asked questions associated with the bot. use after authenticating the bot and when you need to list or manage its faq entries.
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 Botsonic
Connect any two apps with Notis in the middle.
Notion and Botsonic, 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 Botsonic.