Turn a delivery plan into a proposal section
When your delivery plan is ready in Notion, have Notis add a clear section to the matching Bidsketch proposal.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Create Proposal Section
Tool to create a proposal section. use after confirming a proposal exists to add a new opening or closing section.
Why this helps
A delivery approach may be planned in detail but omitted from the client-facing proposal.
- Carry prepared delivery context into the client proposal.
- Avoid rewriting the same approach in multiple places.
- Choose a clear readiness signal in the prompt.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bidsketch to Notis once through the portal.
- 2Create an automation that creates a proposal section from a delivery plan marked ready to share.
- 3Choose Page Content Updated scoped to the plan page or parent and explain the readiness condition, proposal match, and section purpose.
- 4Choose a channel for run reports, then test with one prepared delivery plan.
Questions about this workflow
Can it create a section before the plan is ready?
Use the prompt to require a clear ready-to-share signal before Notis creates the section.
Does the action send the proposal?
No. This workflow creates a proposal section. Sending proposals is not among the listed actions.
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.