Give chargeback concerns a visible support follow-up
Capture the chargeback concern in Notion and open a Gorgias ticket for a person to review.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Ticket
Creates a new ticket in gorgias.
Why this helps
A time-sensitive concern can be recorded in a project tracker without landing in the team's customer support queue.
- Give a chargeback concern a trackable support next step.
- Keep customer context near the team handling the conversation.
- Reduce manual copying during a time-sensitive handoff.
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 what a chargeback alert should trigger.
- 3Write one plain-language instruction asking Notis to create a Gorgias review ticket from each new Notion chargeback alert.
- 4Choose New Page, select a channel for run reports, and test with one real alert.
Questions about this workflow
Does creating the ticket dispute the chargeback?
No. It creates a support ticket for a person to review and handle.
Can the automation watch a specific alert database?
Scope the New Page trigger to the relevant data source when setting up the automation.
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.