Monitor Your Team Coordination Channels for Health
Silent coordination channels indicate team siloing or disengagement. Notis checks Ably channel health hourly and alerts you when occupancy drops unexpectedly.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Channel Details
This tool retrieves metadata and details for a specific channel in ably. it returns a channeldetails object containing information about the channel's status, occupancy, and other metadata. the endpoint provides visibility into channel activity, including metrics such as connections, presence, publishers, and subscribers, and requires appropriate permissions.
Why this helps
Neurodivergent leaders lack visibility into whether team coordination infrastructure is actually being used. Channels go silent without leaders realizing. Team siloing creates invisible coordination gaps until problems surface.
- Channel health is monitored automatically so you know which channels are active versus silent
- Identifies coordination gaps early when occupancy drops unexpectedly
- Helps leaders understand if channels are being used as intended
- Alerts you to dead channels that can be archived or revived
Setup
Build it in a few focused steps.
- 1Connect Notion and Ably to Notis.
- 2Create the automation: 'Every hour, check the occupancy and connection metrics for all my Ably channels and post a health summary.'
- 3Select trigger: 'Scheduled (hourly).'
- 4Notis queries channel details (occupancy, subscribers, publishers) for all channels.
- 5Test by running manually and reviewing the health summary; adjust to show metrics you care about (total occupancy, channels with zero members, etc.).
Questions about this workflow
What metrics are included in the health check?
By default: occupancy (member count) per channel. Customize it: 'include subscriber and publisher counts' or 'flag channels with unexpected drops in activity.'
How often should I check channel health?
Hourly is reasonable for active teams. You can adjust to 'every 6 hours' for less frequent monitoring or 'every 30 minutes' for teams that coordinate heavily.
Can I get alerts when a channel becomes inactive?
Yes, tell Notis 'flag any channel that drops below 2 members' or 'alert if a typically-busy channel goes silent for 30+ minutes.'
Does this help identify unused channels to archive?
Yes, track trends over time: 'channels with zero occupancy for 7 days are candidates for archiving' or 'show me slowest-growing channels.'
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ably. A trigger fires from one place; an action lands in another.
Notion triggers
Ably actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Query Batch Presence
This tool enables querying the presence states of multiple channels in a single api request. the api retrieves the member presence details of the specified channels in parallel.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Query Batch Presence History
This tool enables querying presence history for multiple channels in a single api request. it uses the get endpoint at https://rest.ably.io/presence to retrieve the member presence history details of the specified channels in parallel.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Ably Channel
Creates a new channel or retrieves an existing channel in ably. this tool allows you to programmatically create and initialize channels for real-time messaging. since ably creates channels implicitly when first used, this action publishes an empty initialization message to create/activate the channel.
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.
Delete Channel Subscription
This tool allows you to unsubscribe devices or clients from push notifications for specific channels. the operation is asynchronous, so immediate requests after deletion may briefly still return the subscription.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Channel Details
This tool retrieves metadata and details for a specific channel in ably. it returns a channeldetails object containing information about the channel's status, occupancy, and other metadata. the endpoint provides visibility into channel activity, including metrics such as connections, presence, publishers, and subscribers, and requires appropriate permissions.
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 Channel History
This tool retrieves the message history for a specified ably channel. it uses the get /channels/{channelid}/messages endpoint to return a paginated list of messages in chronological order, subject to parameters such as 'channelid', 'limit', 'direction', 'start', and 'end'. the tool is useful for auditing, recovering missed messages, analyzing channel activity, and debugging message flows. authentication is required via basic or token authentication.
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 Channel Presence History
This tool retrieves the history of presence messages for a specified channel in ably. it allows you to query presence events on a channel within a given time period.
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 Ably Service Time
This tool retrieves the current server time from ably's service in milliseconds since the epoch. it is particularly useful for time synchronization and generating valid tokenrequest timestamps to prevent replay attacks. the endpoint supports multiple content types, handles http errors, network issues, and is a fundamental tool for ensuring accurate timing in ably applications.
Connect any two apps with Notis in the middle.
Notion and Ably, 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 Ably.