Connect new Notion views to a Discord server review
Create a Notion view and have Notis retrieve your Discord servers as context for the workspace setup.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
List my guilds
Lists the current user's guilds, returning partial data for each; primarily used for displaying server lists or verifying memberships.
Why this helps
A new view can support a process that spans tools, but the related Discord context may be out of sight.
- Make server context available when a new operational view is added.
- Keep workspace setup checks attached to the view creation event.
- Avoid a separate server-list lookup.
Setup
Build it in a few focused steps.
- 1Connect Notion and Discord to Notis once through the portal.
- 2Create an automation in the portal or tell Notis to retrieve your Discord server list when a new view is created.
- 3Select the Notion View Created trigger.
- 4Choose a run-report channel and test by creating one real view.
Questions about this workflow
Does the trigger include view type?
Yes. The event includes the view type and its parent so downstream instructions can use that context.
What does the Discord action do?
It lists guilds available to the authenticated Discord user.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Discord. A trigger fires from one place; an action lands in another.
Notion triggers
Discord actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Invite
Tool to retrieve information about a specific invite code. use when you need to get details about a guild or channel associated with an invite.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get my guild member
Retrieves the guild member object for the currently authenticated user within a specified guild, provided they are a member of that guild.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get my OAuth2 authorization
Retrieves current oauth2 authorization details for the application, including app info, scopes, token expiration, and user data (contingent on scopes like 'identify').
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 my user
Fetches comprehensive profile information for the currently authenticated discord user, including email if the 'email' scope is granted.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Retrieve user connections
Retrieves a list of the authenticated user's connected third-party accounts on discord.
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 my guilds
Lists the current user's guilds, returning partial data for each; primarily used for displaying server lists or verifying memberships.
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 Discord, 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 Discord.