Make Discord event access easier to prepare
For event records that need a Discord gathering space, Notis can create an invite to the chosen channel so organizers have an access link ready to include.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create channel invite
Creates a new invite for the specified discord channel, provided the bot has 'create instant invite' permission for that channel.
Why this helps
Event setup often spans a planning page and Discord, making it easy to forget to create or share the community invite.
- Reduce an extra manual step in event preparation.
- Make it easier to include Discord access in event information.
- Help organizers keep plans and community access connected.
Setup
Build it in a few focused steps.
- 1Connect Notion and Discordbot to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to create a Discord invite for each relevant Notion event record.
- 3Describe the event access outcome in one plain-language instruction.
- 4Select the Notion New Page trigger for the event data source and choose a channel for run reports.
- 5Test with one real event record and verify the invite targets the intended channel.
Questions about this workflow
What permission is needed to create an invite?
The bot needs create instant invite permission for the selected Discord channel.
Can I use a specific channel?
Yes. Describe the intended channel in the instruction so Notis uses the appropriate destination.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Discordbot. A trigger fires from one place; an action lands in another.
Notion triggers
Discordbot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add recipient to group channel
Adds a user to a discord group direct message (dm) channel.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Update guild member information
Adds a user (who is not already a member) to a guild using their `access token` (which must have `guilds.join` scope), optionally setting nickname, roles, mute/deaf status, or flags.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Assign role to guild member
Assigns a role to a guild member, provided the bot has 'manage roles' permission in the guild and the role to be assigned is hierarchically lower than the bot's highest role.
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.
Add reaction to message
Adds an emoji reaction from the authenticated user/bot to a specific message in a discord channel; does not return information about existing reactions.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Add or update thread member
Adds a user to a specific, unarchived thread; the user must have access to the thread's parent channel, and for private threads, the bot must already be a member.
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.
Modify guild ban settings
Permanently bans a user from a discord guild, optionally deleting their recent messages (specify deletion period in seconds or days, not both).
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.
Bulk ban users in guild with message deletion option
Bans up to 200 users from a discord guild, optionally deleting their recent messages; the bot must have 'ban members' permission in the guild, and this action is irreversible.
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.
Bulk delete messages in channel
Atomically bulk deletes messages in a discord channel for moderation or maintenance; deletion may not be instantaneous and messages are unrecoverable.
Connect any two apps with Notis in the middle.
Notion and Discordbot, 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 Discordbot.