See Available Event Tags While Planning
Start planning with a clear view of the tags already available in Humanitix, so useful organizing labels are easier to spot and remember.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
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.
Why this helps
Finding the right existing tag can interrupt planning and add another small decision to an already busy workflow.
- Surface existing tags as a planning aid.
- Avoid creating an unnecessary duplicate label by mistake.
- Keep organizational context close to the event planning moment.
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.
- 3Give Notis one instruction to retrieve Humanitix tags when a new event planning record appears and summarize labels that may be relevant.
- 4Select the Notion New Page trigger for the event database and choose a reporting channel.
- 5Test with one real planning record and review the returned tags.
Questions about this workflow
Does this apply tags to an event?
No. Get Tags lists account tags; it does not assign or create them.
Can I use tags to decide how to organize a plan?
Yes. The summary can make existing labels easier to consider while planning.
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.