Recheck checkout settings as your tracking structure changes
When your process tracking changes, bring current Gift Up checkout settings into the review.
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
Get Checkout Settings
Tool to retrieve the current checkout settings. Use when you need to display or audit your checkout configuration.
Why this helps
A structural change to a workflow can leave related operating assumptions unchecked.
- Retrieves checkout settings after a schema update.
- Creates a prompt to review Gift Up configuration when tracking changes.
Setup
Build it in a few focused steps.
- 1Connect Notion and Gift Up to Notis once.
- 2Create an automation in the portal or describe it to Notis.
- 3Ask in one instruction for Gift Up checkout settings when the relevant Notion data source schema changes.
- 4Choose Data Source Schema Updated and select a channel for reports.
- 5Test with one real schema update.
Questions about this workflow
Does a schema change modify Gift Up settings?
No. The workflow retrieves the current settings for review.
What schema changes trigger it?
The Notion event fires on column additions, removals, or renames and includes updated property details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gift up. A trigger fires from one place; an action lands in another.
Notion triggers
Gift up actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Checkout Settings
Tool to retrieve the current checkout settings. Use when you need to display or audit your checkout configuration.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Company Details
Tool to retrieve company details. Use when you need to fetch the current company associated with the API key.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Gift Cards
Tool to list gift cards. Use when you need to retrieve gift cards with optional filters.
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 Item Groups
Tool to list item groups. Use when you need to retrieve all item groups for filtering items by group.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Items
Tool to list items. Use when you need to retrieve all items available for sale, optional filter by groupId.
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.
List Locations
Tool to list all locations. Use when you need to retrieve all locations associated with the account.
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.
List Report Transactions
Tool to list report transactions with optional filters. Use after setting desired filters to retrieve transactions report.
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 GiftUp Users
Tool to list all users. Use when you need to retrieve all users who have access to your Gift Up! account.
Connect any two apps with Notis in the middle.
Notion and Gift up, 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 Gift up.