Connect a New Notion Sales View to Callpage Widget Setup
When a new sales view is created, let Notis prompt an update to the Callpage widget configuration that supports the workflow.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
Update Widget
Tool to update an existing widget. use when you need to change widget url, description, settings, language, or enabled state.
Why this helps
A new sales process view can introduce setup work in another tool that is easy to leave unfinished.
- Keep widget setup aligned with a new sales workflow.
- Reduce the number of setup details to remember across tools.
- Use a workspace change as a cue to revisit the right widget.
Setup
Build it in a few focused steps.
- 1Connect Notion and Callpage to Notis once through the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Use one plain-language instruction to explain which new sales view should prompt a Callpage widget update and the intended change.
- 4Select Notion's View Created trigger and choose a run-report channel.
- 5Test by creating one relevant view and confirming the intended widget is unambiguous.
Questions about this workflow
What can Update Widget change?
It can change a widget's URL, description, settings, language, or enabled state.
Will every new view update a widget?
Describe which sales views matter in the instruction and make the intended widget clear.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Callpage. A trigger fires from one place; an action lands in another.
Notion triggers
Callpage actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get All Managers
Tool to retrieve a list of managers for a specific widget with pagination. use when you need to page through all managers assigned to a widget after confirming its id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get All SMS Messages
Tool to retrieve all sms messages for a widget. use when you need to fetch both default and custom sms templates after confirming the widget exists.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get All Users
Tool to retrieve a list of all users with pagination. use when you need to page through all users in your callpage account to synchronize or audit user records.
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 All Widgets
Tool to retrieve a list of widgets with pagination. use when you need to page through all widgets after api authentication.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get API Root
Tool to get the root api greeting. use to verify connectivity and retrieve the initial api greeting after setting the api key.
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 Manager Status Statistics
Tool to retrieve statistical data about manager statuses. use when you need summary counts of enabled and disabled managers for a specific widget.
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 SMS Statistics
Tool to retrieve statistical data about sms messages. use when you need summary counts of sms messages for a given widget.
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 Widget
Tool to retrieve details of a specific widget by id. use when you have a widget id and need its complete configuration.
Connect any two apps with Notis in the middle.
Notion and Callpage, 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 Callpage.