Skip to content
Notis

Bring Docsbot customer questions into a Notion review

At review time, ask Notis to collect the Docsbot questions your team should consider.

Trigger

Page Properties Updated

Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.

Action

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'."

Why this helps

Reviewers may have to remember to leave their planning space and look for unanswered customer questions.

  • Makes customer questions part of a scheduled review moment.
  • Reduces reliance on someone remembering a separate manual lookup.
  • Gives reviewers a concrete question list to consider alongside Notion context.

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 the desired outcome in plain language.
  • 3Ask Notis in one instruction to list questions for the relevant Docsbot bot when a review record is updated to its ready state, and summarize them for review.
  • 4Select Page Properties Updated for the review database and choose a channel for run reports.
  • 5Test by changing one real review record to its ready state and inspect the question summary.

Questions about this workflow

Can the trigger detect the review status change?

The Notion property update trigger fires when a page property changes. Describe the ready-state condition in the instruction.

Does listing questions itself create a helpdesk ticket?

No. This action retrieves the bot's questions so Notis can prepare a review summary.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

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.

ActionInstant

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.

TriggerInstant

Get Bot Details

Tool to fetch details of a specific bot by id within a team. use after confirming valid team and bot ids.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

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'."

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.