Turn Notion tracking changes into a ticket review
A changed tracking schema can prompt a bounded look at active Freshservice work.
Trigger
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.
Action
List Freshservice Tickets
Tool to list all tickets in Freshservice with optional filtering and pagination. Use when you need to retrieve ticket IDs or search for tickets. By default only tickets created within the past 30 days are returned; use updated_since for older tickets.
Why this helps
When a database structure changes, existing tickets may not reflect the new tracking expectations, and reviewing them can get deferred.
- Create a timely review cue when tracking requirements shift.
- Focus attention on existing service work.
- Reduce the chance that process changes leave open tickets behind.
Setup
Build it in a few focused steps.
- 1Connect Notion and Freshservice to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to review tickets after a tracking schema change.
- 3Use one plain-language instruction to list relevant Freshservice tickets for review when the schema changes.
- 4Select the Notion Data Source Schema Updated trigger and choose where to receive run reports.
- 5Test with a real schema change and inspect the returned ticket list.
Questions about this workflow
Does this automatically update tickets?
This workflow lists Freshservice tickets as review candidates; it does not make bulk changes.
Can it identify a particular kind of schema change?
The Notion event includes updated property details; describe the change of interest in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Freshservice. A trigger fires from one place; an action lands in another.
Notion triggers
Freshservice actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bulk Update Tickets
Tool to bulk update multiple Freshservice tickets by sequential update calls. Use when you need to update fields across many tickets in absence of a native bulk API.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Service Request
Create a service request for a catalog item in Freshservice using the v2 API. The catalog item display_id can be found in Admin > Service Catalog by clicking on an item and checking the URL (e.g., /service_catalog/items/1 means display_id=1).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Ticket
Tool to create a new ticket. Use when you need to log an incident or service request.
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 Release
Tool to delete a release from Freshservice. Use when you need to permanently remove a release from the system. This action is irreversible — the release cannot be recovered once deleted.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Solution Article
Tool to delete a solution article from the knowledge base by its ID. This action is irreversible — the article cannot be recovered once deleted. Use this action when you need to permanently remove a solution article from Freshservice.
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 Solution Category
Tool to delete a solution category in Freshservice. Use this action when you need to remove a solution category that is no longer needed. This action is irreversible — the category cannot be recovered once deleted.
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 Problem Form Fields by Workspace
Tool to list problem form fields. Use when you need to retrieve the form fields available for problems in a specific workspace.
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 Release Form Fields
Tool to list release form fields metadata. Use when you need to fetch release field definitions before building or validating release forms.
Connect any two apps with Notis in the middle.
Notion and Freshservice, 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 Freshservice.