Move a reviewed batch of Notion resources into chatbot training
When your publishing process is ready, send a webhook and have Notis upload the approved Notion URLs to Botsonic in one batch.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
A collection of approved resources can stall at the final step if someone has to upload every URL by hand.
- Handle multiple approved resource URLs in one training request.
- Reduce repetitive end-of-publishing tasks.
- Keep the handoff tied to an explicit ready signal.
Setup
Build it in a few focused steps.
- 1Connect Notion and Botsonic to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to upload an approved batch of Notion URLs when your publishing process sends a webhook.
- 3Write one plain-language instruction to bulk upload the approved URLs to the intended Botsonic bot for training.
- 4Choose the incoming webhook trigger and run-report channel, then test with one real approved batch.
Questions about this workflow
Does the webhook automatically gather URLs from Notion?
The workflow instruction should specify the approved URLs supplied by your webhook or available to Notis from the connected tools.
Can this handle several URLs at once?
Yes. Bulk Upload Bot URLs is intended to upload multiple document URLs in one request.
When this happens · Trigger
Do this · Action
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.
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.