Keep Freshdesk tickets current with Notion
Update the support page you already use and let Notis reflect the change in its related Freshdesk ticket.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Update Ticket
Updates an existing ticket in freshdesk.
Why this helps
Support context often changes as a founder investigates, but updating the ticket can get pushed aside.
- Keep ticket context current as investigations develop.
- Avoid revisiting the same issue to make a second update.
- Give support conversations the latest useful information.
Setup
Build it in a few focused steps.
- 1Connect Notion and Freshdesk to Notis once in the portal.
- 2Create an automation through the portal or a plain-language request to Notis.
- 3Describe in one prompt how page content changes should update the related Freshdesk ticket.
- 4Select Page Updated for the specified Notion page and choose a run-report channel.
- 5Test with one real context update and verify the ticket reflects it.
Questions about this workflow
What does Page Updated detect?
It triggers when a block within the specified Notion page is updated.
Can I prevent irrelevant edits from changing the ticket?
Describe the relevant updates in the prompt and test the behavior on your chosen page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Freshdesk. A trigger fires from one place; an action lands in another.
Notion triggers
Freshdesk actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Ticket
Creates a new ticket in freshdesk.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Ticket
Deletes an existing ticket in freshdesk.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Tickets
Retrieves a list of tickets from freshdesk.
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 All Tickets
Lists all tickets in freshdesk.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Reply to Ticket
Replies to an existing ticket in freshdesk.
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.
Update Ticket
Updates an existing ticket in freshdesk.
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.
View Ticket
Views an existing ticket in freshdesk.
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 Freshdesk, 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 Freshdesk.