Keep trusted sender details close to changing customer records
When a customer or operations record changes, make it easier to review the Helpdesk trusted-email list before acting on a communication issue.
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 Trusted Emails
Tool to retrieve a list of trusted email addresses or domains. Use when managing your spam whitelist after authenticating.
Why this helps
Allowlist details are easy to overlook when customer information and account settings are spread across tools.
- Retrieve trusted email addresses and domains after a Notion property update.
- Keep sender-reference information close to the changed record.
- Make communication review more efficient.
Setup
Build it in a few focused steps.
- 1Connect Notion and Helpdesk to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to list Helpdesk trusted emails when relevant Notion page properties change.
- 3Pick the Notion Page Properties Updated trigger and select a run-report channel.
- 4Test with one real property update and review the trusted sender list.
Questions about this workflow
Does the workflow add a trusted address?
No. The selected action retrieves the current trusted list.
Can it be scoped to a data source?
Yes. The trigger can be scoped to one data source, page, or parent page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Helpdesk. A trigger fires from one place; an action lands in another.
Notion triggers
Helpdesk actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Agents
Tool to list agents. Use when you need to retrieve all agents on the account.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Canned Responses
Tool to list canned responses. Use when you need to retrieve all predefined reply templates for tickets.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Contacts
Tool to list contacts. Use when you need to retrieve contacts with optional filters and pagination.
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.
List Custom Fields
Tool to list all custom fields defined in the account. Use when you need to view or manage custom fields. Only callable after authentication.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Email Domains
Tool to list email domains configured for the account. Use when you need to retrieve all configured email domains after authenticating.
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.
List Licenses
Tool to list all licenses for an account. Use when you need to retrieve license configurations.
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.
List Reply Addresses
Tool to retrieve reply addresses. Use when you need to fetch all configured reply email addresses.
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.
List Rules
Tool to retrieve a list of rules configured in the account. Use after authentication when you need an overview of all automation rules.
Connect any two apps with Notis in the middle.
Notion and Helpdesk, 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 Helpdesk.