Keep organizer relationships visible with a quarterly review
Set a recurring point to revisit the people behind your events, with Notis gathering contact and relationship context for you.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Contacts
Tool to retrieve a list of contacts from evenium. use when you need to fetch and optionally filter organizer contacts.
Why this helps
Important organizer relationships can fade from view when there is no clear moment to review them.
- Create a light recurring relationship review.
- Bring organizer contacts and notes together for context.
- Reduce reliance on memory to initiate the review.
Setup
Build it in a few focused steps.
- 1Connect Notion and Evenium to Notis once in the portal.
- 2Create a scheduled automation in the portal or ask Notis conversationally.
- 3Ask Notis to retrieve Evenium organizer contacts quarterly and summarize them with the Notion relationship notes you specify.
- 4Choose a quarterly schedule and a channel for reports.
- 5Test by reviewing one real contact summary.
Questions about this workflow
Will it contact organizers?
No. It retrieves contact information for your review; it does not send messages.
Can I change the cadence?
Yes. Choose a recurring schedule that fits your review routine.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Evenium. A trigger fires from one place; an action lands in another.
Notion triggers
Evenium actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Contacts
Tool to retrieve a list of contacts from evenium. use when you need to fetch and optionally filter organizer contacts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Events
Tool to retrieve a list of events with optional filters. use after authenticating with evenium.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Logout
Tool to log out the current user and invalidate the session token. use when you need to explicitly end the current session.
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 Evenium, 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 Evenium.