Skip to content
Notis

Keep customer feedback visible on Gorgias tickets

When feedback in Notion points to a customer follow-up, add a tag to the related 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

Add Ticket Tags

Adds tags to a ticket in gorgias.

Why this helps

Feedback can be captured in notes but lose visibility in the system where the support conversation lives.

  • Connect feedback to its support conversation.
  • Make feedback follow-up easier to find.
  • Avoid manually relabeling tickets after review.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Gorgias to Notis once through the portal.
  • 2Create a new automation in the portal or ask Notis for the feedback-tagging workflow.
  • 3In one instruction, ask Notis to tag the related Gorgias ticket when a Notion comment records actionable customer feedback.
  • 4Select Comment Created, choose a channel for run reports, and test with one real feedback comment.

Questions about this workflow

Will a tag be added for every comment?

State in the prompt that the tag should be added only when the comment records actionable customer feedback.

Can comments be scoped to a feedback page?

Yes. Configure the comment trigger with the relevant page scope if the feedback is collected in a specific location.

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.

TriggerScheduled

Add Ticket Tags

Adds tags to a ticket in gorgias.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Account Setting

Creates a new account setting in gorgias.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Create Customer

Creates a new customer in gorgias.

ActionInstant

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.

TriggerInstant

Create Team

Creates a new team in gorgias.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Create Ticket

Creates a new ticket in gorgias.

ActionInstant

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.

TriggerInstant

Delete Customer

Deletes a specific customer from gorgias.

ActionInstant

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.

TriggerInstant

Delete Customer Field Value

Deletes a specific field value for a customer in gorgias.

ActionInstant

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.

TriggerInstant

Delete Customers

Deletes multiple customers from gorgias.

ActionInstant

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.