Keep proposal volume visible as your pipeline changes
Update your Notion pipeline and get a proposal count to help you understand the current workload.
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
Get Proposal Count
Tool to retrieve the total count of proposals. use when you need to know how many proposals exist.
Why this helps
A busy pipeline can feel harder to manage when proposal volume is not easy to see at a glance.
- Make proposal volume visible after a pipeline update.
- Support simpler workload and capacity conversations.
- Avoid manually counting records across views.
Setup
Build it in a few focused steps.
- 1Connect Notion and Better Proposals to Notis once through the portal.
- 2Create an automation in the portal or ask Notis for a proposal count after a pipeline record changes.
- 3Use one instruction describing how you want the count framed for planning.
- 4Choose Page Properties Updated for the pipeline data source and select a reporting channel.
- 5Test by updating one real pipeline record and reviewing the count report.
Questions about this workflow
Does the count show proposal status breakdowns?
Get Proposal Count retrieves a total count. Use another available list action when you need status-specific records.
Will unrelated property updates trigger it?
The selected event triggers on page property updates in the scoped data source. Describe the relevant context in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Better proposals. A trigger fires from one place; an action lands in another.
Notion triggers
Better proposals actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get All Document Types
Tool to retrieve a paginated list of all document types. use when you need to display or select a document type id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Company
Tool to create a new company. use after confirming the company does not already exist.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Document Type
Tool to create a new document type. use after confirming the desired type name does not already exist.
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.
Create Proposal Cover
Tool to create a new proposal cover design. use when you need a custom cover design before sending out a proposal. use after finalizing cover settings.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get All Companies
Tool to retrieve a paginated list of all companies. use when listing available companies for display or selection.
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 Currencies
Tool to retrieve a paginated list of all currencies. use when listing available currency options before selection.
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 Document Types
Tool to retrieve a paginated list of all document types. use when you need to display or select a document type 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.
Get All Proposals
Tool to retrieve a paginated list of all proposals. use when you need to fetch proposals list after validating credentials.
Connect any two apps with Notis in the middle.
Notion and Better proposals, 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 Better proposals.