Reflect scope changes in proposal sections
When the agreed scope changes in Notion, let Notis update the section that explains that work in the proposal.
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
Update Proposal Section
Tool to update a proposal section. use when you need to modify the name or content of an existing section after verifying its existence.
Why this helps
A proposal can keep describing the original scope after the working record has changed.
- Keep the proposal description closer to the current scope.
- Reduce the need to remember a separate proposal-editing task.
- Specify the relevant scope changes and section in one prompt.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bidsketch to Notis once through the portal.
- 2Create an automation that updates the related proposal section after a relevant scope change.
- 3Select Page Properties Updated for the scope database and explain how Notis should recognize a material change and locate the section.
- 4Choose a reporting channel, then test with one scope update and its proposal.
Questions about this workflow
Can it react to every property change?
The trigger detects property updates. Use the prompt to say which scope changes are material enough to update a section.
What if the section cannot be identified?
Tell Notis in the prompt to report the issue for review when it cannot confidently identify the section.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bidsketch. A trigger fires from one place; an action lands in another.
Notion triggers
Bidsketch actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Client
Tool to create a client. use when adding a new client record to bidsketch.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Client
Tool to delete a client and all their proposals. use when you want to permanently remove a client and its associated proposals from your account.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Fee
Tool to delete a fee. use when a saved fee is no longer needed. use after confirming this fee isn't referenced in any live proposals.
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 Proposal
Tool to delete a proposal and all its content. use after confirming the proposal id to prevent accidental deletions.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Proposal Fee
Tool to delete a proposal fee. use when you need to remove an existing fee before finalizing or sending a proposal.
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 Proposal Section
Tool to delete a proposal section. use when you need to remove a section from a proposal after verifying its id.
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 Section
Tool to delete a section. use when you need to permanently remove a saved section after confirming its id.
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.
Delete Webhook
Tool to delete a webhook. use after obtaining the webhook id to remove it.
Connect any two apps with Notis in the middle.
Notion and Bidsketch, 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 Bidsketch.