Turn project discussions into follow-up contacts
Capture a contact mentioned in a project page comment without leaving the discussion behind in Notion.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
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.
Why this helps
A name and number shared in a project discussion can be easy to forget when returning to the task later.
- Keep discussion follow-ups from becoming memory tasks
- Capture contact details near the context
- Reduce repeated searches through project comments
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.
- 3Write one instruction to add a person to Dialmycalls when a new comment on the project page contains usable contact details.
- 4Choose the Notion New Comment trigger and specify the page or block.
- 5Choose a channel for run reports and test with one real project comment.
Questions about this workflow
How is this different from workspace-wide comment capture?
The New Comment trigger is for a specified Notion block or page, making it suitable for a focused project discussion.
Will it add every commenter?
The instruction should tell Notis to add only people whose contact details are relevant to the stated follow-up.
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.