Check for existing Docsbot bots when a support initiative starts
See which Docsbot bots already exist before setting up another support resource.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
List Team Bots
Tool to list all bots for a given team. use after confirming the team id to retrieve all associated bots for that team.
Why this helps
Founders can lose time recreating a resource that may already be available in another workspace.
- Promotes reuse by showing existing bots at initiative kickoff.
- Reduces the time spent searching Docsbot manually.
- Gives the initiative owner a clear starting point for the next decision.
Setup
Build it in a few focused steps.
- 1Connect Notion and Docsbot ai to Notis once in the portal.
- 2Create an automation in the portal or tell Notis what result you need.
- 3Ask Notis in one instruction to list the bots in the relevant Docsbot team when a new support initiative is added to Notion.
- 4Select New Page for the support initiative database and choose a channel for run reports.
- 5Test with one real initiative record and verify that the bot inventory is useful.
Questions about this workflow
Does this make a new bot?
No. It lists bots in the selected team to help the owner reuse an existing resource.
How should the automation know which team to check?
State the relevant team context in the plain-language instruction and available Notion records.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Docsbot ai. A trigger fires from one place; an action lands in another.
Notion triggers
Docsbot ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Bot
Tool to create a new bot within a team. use when you have a valid team id and want to provision a new bot.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Bot
Tool to delete a specific bot by its id. use after confirming the bot id is correct to permanently remove a bot from the system.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Generate Conversation Ticket
Tool to generate a structured support ticket from a chat agent conversation. use when you need to convert an existing conversation into a ready-to-submit helpdesk ticket.
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 Bot Details
Tool to fetch details of a specific bot by id within a team. use after confirming valid team and bot ids.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Team Details
Tool to fetch details of a specific team by its id. use when you need full team info including members and settings after confirming the team id.
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.
List Team Bots
Tool to list all bots for a given team. use after confirming the team id to retrieve all associated bots for that team.
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.
List Questions
Tool to list all questions asked of a specific bot. use after confirming the bot's identifier. example: "list questions for bot abc123 with status 'unanswered'."
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.
List Bot Sources
Tool to list all sources for a specific bot. use when you need to retrieve paginated source lists after confirming the bot's identifier.
Connect any two apps with Notis in the middle.
Notion and Docsbot ai, 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 Docsbot ai.