Review directory fields when your Notion structure changes
When your Notion structure changes, a quick reference to Brilliant Directories user fields can help you review the related onboarding process without searching from scratch.
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 User Fields
This tool fetches all available fields from the users data table in your brilliant directories website. it provides a detailed list of available fields for user operations including creation, updating, and retrieval.
Why this helps
Schema changes can leave setup notes stale, making it harder to remember whether the directory side still supports the intended process.
- Refresh the directory user-field reference when Notion's structure changes.
- Make integration maintenance easier to resume.
- Spot details to review before changing an onboarding process.
Setup
Build it in a few focused steps.
- 1Connect Notion and Brilliant Directories to Notis once through the portal.
- 2In Automations, choose New Automation and name it for your schema review routine.
- 3Write one prompt asking Notis to retrieve Brilliant Directories user fields when a Notion data source schema changes and summarize relevant details for review.
- 4Select the Notion Data Source Schema Updated trigger and choose a channel for run reports.
- 5Test by making a planned schema change and reviewing the returned field summary.
Questions about this workflow
Does the lookup prove that both schemas match?
No. It provides current directory user-field metadata for your review; describe any comparison you want in the prompt.
Can this run for any Notion data source?
The provided trigger fires for schema updates in the workspace the integration can access. Use the prompt to keep the returned summary focused.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Brilliant directories. A trigger fires from one place; an action lands in another.
Notion triggers
Brilliant directories actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create User
This tool creates a new user record in the brilliant directories website database. it supports creating new users with essential details such as email, password, subscriptionid and optional parameters including name, company, contact details, and address information.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete User
This tool deletes an existing user record from the brilliant directories website database. it allows for the complete removal of a user record and, optionally, the deletion of the member's uploaded images.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Data Categories
This tool fetches all data categories in a brilliant directories website. data categories are distinct from top categories and represent the various types of data organization within the system.
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.
Get Lead Fields
This tool retrieves all available fields in the leads table from a brilliant directories website. it returns a json object containing a list of fields and their associated metadata (field name, field type, field label, whether the field is required, and if it is a system field) that can be used to understand the structure and metadata of lead-related fields.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Reviews Fields
This tool retrieves all the available fields in the users reviews table from a brilliant directories website. it is a standalone tool that requires only authentication and provides a comprehensive list of review information such as review text, rating, timestamp, user identification fields, and any custom configured fields in the reviews system.
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.
Get User Fields
This tool fetches all available fields from the users data table in your brilliant directories website. it provides a detailed list of available fields for user operations including creation, updating, and retrieval.
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.
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 Brilliant directories, 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 Brilliant directories.