Pair status changes with a call activity check
When a follow-up status changes in Notion, have Notis surface Dialmycalls calls for a quick review.
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 Calls
Tool to list all call broadcasts on the account. use when you need to retrieve or manage call records with optional filters like name, type, status, dates, pagination, and sorting.
Why this helps
A status can move forward without a quick check that related call activity is understood.
- Make related call activity easier to inspect
- Add a review cue to status changes
- Reduce the effort of rebuilding context
Setup
Build it in a few focused steps.
- 1Connect Notion and Dialmycalls to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Give one instruction to list Dialmycalls calls and summarize relevant records when the designated follow-up status changes.
- 4Choose the Notion Page Properties Updated trigger and scope it to the follow-up data source.
- 5Choose a channel for run reports and test with one real status change.
Questions about this workflow
Can the workflow update the Notion status based on a call?
No. It responds to a Notion update by listing Dialmycalls call records for review.
Can I limit it to a particular status change?
Describe the relevant status change in the instruction and scope the trigger to the relevant data source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Dialmycalls. A trigger fires from one place; an action lands in another.
Notion triggers
Dialmycalls actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Access Account
Tool to add a new access (sub) account. use when you need to delegate dialing capabilities to another user after setting up your master account.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Contact
Tool to add a contact to your contact list. use when you need to store a new contact's phone (and optional name, email, or group) before sending messages.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Add Group
Tool to add a new contact group. use after deciding the group name to organize recipients into groups.
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 Access Account
Tool to delete an access (sub) account by id. use when removing a sub account after deprovisioning.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Caller ID
Tool to delete a caller id. use when you need to permanently remove an existing caller id no longer in use.
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 Contact
Tool to delete a contact by id. use when you need to permanently remove a contact from your list.
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 Group
Tool to delete a contact group by id. use when you need to remove an existing contact group 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 Recording
Tool to delete a recording by id. use when you need to permanently remove a custom recording after confirming its recording id.
Connect any two apps with Notis in the middle.
Notion and Dialmycalls, 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 Dialmycalls.