Keep callback requests moving into GoDial
When Notion records that someone wants a call back, prepare their GoDial contact for follow-through.
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
Add GoDial Contact
Tool to add a new contact in GoDial CRM. Use when you need to create contacts programmatically.
Why this helps
Callback promises are easy to forget when they live in one note while calling happens somewhere else.
- Give callback requests a clear route into calling.
- Reduce reliance on remembering a separate follow-up list.
- Make the request details available from the original Notion record.
Setup
Build it in a few focused steps.
- 1Connect Notion and Godial to Notis once.
- 2Create an automation from the portal or tell Notis what callback requests should do.
- 3Use one plain-language instruction asking Notis to add a GoDial contact when a Notion record is marked as a callback request.
- 4Select Page Properties Updated for the callback tracker, choose where run reports should go, and test with one real request.
Questions about this workflow
Does this place a call automatically?
No. It adds a contact in GoDial so the callback can enter your calling process.
What starts the workflow?
A Notion properties update, such as marking a record as a callback request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Godial. A trigger fires from one place; an action lands in another.
Notion triggers
Godial actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add GoDial Contact
Tool to add a new contact in GoDial CRM. Use when you need to create contacts programmatically.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Retrieve GoDial Accounts
Tool to retrieve all accounts in the authenticated GoDial account. Use after obtaining access token to fetch available accounts. Supports optional pagination.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Retrieve GoDial External Lists
Tool to retrieve all lists in the authenticated GoDial account. Use when you need to enumerate lists for selecting a target list ID after configuring your External API access token.
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.
Remove GoDial Account
Tool to remove a GoDial account. Use when an account needs to be permanently deleted.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Godial, 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 Godial.