Bring Event Context to Planning Discussions
A comment can surface a decision or open question. Let Notis check the Humanitix event list and summarize what may connect to the discussion.
Trigger
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.
Action
Get Events
Tool to retrieve a paginated list of events from your humanitix account. use when you need to page through your events after confirming api key validity.
Why this helps
Useful event decisions can get buried in comments, while the person responsible still has to switch tools to verify the listing context.
- Connect a discussion moment with existing event information.
- Make follow-up easier to resume after a conversation.
- Reduce manual lookups during collaborative planning.
Setup
Build it in a few focused steps.
- 1Connect Notion and Humanitix to Notis once through the portal.
- 2Create an automation in the portal, or ask Notis conversationally for this workflow.
- 3Write one instruction asking Notis to retrieve Humanitix events and summarize any likely context relevant to a new event-planning comment.
- 4Select the Notion Comment Created trigger and choose a channel for run reports.
- 5Test by adding a real comment to an event planning page.
Questions about this workflow
Does Notis read comments automatically?
Comment events require the Notion integration's Read comments capability and may require reauthorization after enabling it.
Can it understand the whole discussion?
It can use the available comment and page context to frame a concise event-list review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Humanitix. A trigger fires from one place; an action lands in another.
Notion triggers
Humanitix actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Event
Tool to retrieve detailed information about a specific event. use when you have the eventid and need full metadata.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Events
Tool to retrieve a paginated list of events from your humanitix account. use when you need to page through your events after confirming api key validity.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Tags
Tool to get all tags associated with your humanitix account. use when you need to list or paginate through tags after setting up your api key.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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 Humanitix, 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 Humanitix.