Bring retention context to the weekly review
Let the scheduled run gather retention data so your weekly review can start with interpretation, not setup.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Island Retention
Tool to retrieve day-over-day retention metrics for a Fortnite island. Use when analyzing retention performance by day (only supported for day interval).
Why this helps
A recurring review loses momentum when basic evidence gathering is left until the meeting begins.
- Make recurring review preparation more dependable.
- Reduce last-minute context switching.
- Keep attention on decisions and follow-up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Epic games to Notis once in the portal.
- 2Create an automation telling Notis to retrieve day-over-day retention for the island in your review notes.
- 3Choose a weekly schedule and a channel for run reports.
- 4Test with a real island code and confirm the day interval is suitable.
Questions about this workflow
Why specify day-over-day?
The retention action supports day interval metrics, so the instruction should request that supported interval.
Will it write a report into Notion?
The action retrieves the metric. Choose a run-report channel in the automation setup to review the result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Epic games. A trigger fires from one place; an action lands in another.
Notion triggers
Epic games actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Preset Metadata Key
Tool to delete a metadata key-value pair associated with a Remote Control Preset. Use after confirming you have the correct preset name and metadata key.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Island Metadata
Tool to fetch metadata for a specific Fortnite island by its code. Use when you have an island code and need detailed island information.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Island Average Minutes per Player
Tool to retrieve average minutes per unique player for a given island code and interval. Use when you need daily or more granular (hour/minute) player engagement metrics. Hourly/minute intervals may not be available.
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 Island Favorites Metrics
Tool to fetch how many times an island was added to favorites over a time interval. Use when analyzing island popularity trends.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Island Metrics by Interval
Tool to retrieve usage metrics for a Fortnite island aggregated by interval. Use when analyzing island usage over time buckets.
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.
Get Island Minutes Played
Tool to retrieve total minutes played on an island during a given interval. Use after obtaining the island code to analyze player engagement metrics.
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.
Get Island Peak CCU
Tool to retrieve peak concurrent users for an island. Use when you need to monitor the highest concurrent users over a specific interval.
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.
Get Island Plays
Tool to retrieve the number of plays (session starts) for a Fortnite island. Use when you need play metrics for a specific island and time interval.
Connect any two apps with Notis in the middle.
Notion and Epic games, 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 Epic games.