Carry Notion support comments into Gorgias follow-up
When a comment calls for customer follow-up, let Notis turn the discussion into a Gorgias ticket.
Trigger
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.
Action
Create Ticket
Creates a new ticket in gorgias.
Why this helps
A follow-up request in a comment can be easy to miss when the conversation moves on.
- Turn a discussion into a trackable support task.
- Preserve the comment's context for follow-up.
- Reduce the need to revisit pages to find open asks.
Setup
Build it in a few focused steps.
- 1Connect Notion and Gorgias to Notis once through the portal.
- 2Create an automation in the portal or tell Notis the outcome you want in a conversation.
- 3Use one plain-language instruction asking Notis to create a Gorgias ticket when a Notion comment requests customer follow-up.
- 4Pick Comment Created as the trigger, choose where run reports should go, and test with one real comment.
Questions about this workflow
Will the workflow run for comments anywhere?
Comment Created can be scoped to a page, or left workspace-wide for pages the integration can access.
What if the comment is only an internal note?
State in the prompt that only comments requesting customer follow-up should create tickets.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gorgias. A trigger fires from one place; an action lands in another.
Notion triggers
Gorgias actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Ticket Tags
Adds tags to a ticket in gorgias.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Account Setting
Creates a new account setting in gorgias.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Customer
Creates a new customer in gorgias.
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.
Create Team
Creates a new team in gorgias.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Ticket
Creates a new ticket in gorgias.
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 Customer
Deletes a specific customer from gorgias.
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 Customer Field Value
Deletes a specific field value for a customer in gorgias.
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 Customers
Deletes multiple customers from gorgias.
Connect any two apps with Notis in the middle.
Notion and Gorgias, 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 Gorgias.