Skip to content
Notis

Auto-Initialize Team Coordination for New Data Sources

New data sources need coordination infrastructure, but manual channel creation adds friction. Notis automatically creates an Ably channel when a new Notion data source is created.

Trigger

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.

Action

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.

Why this helps

Neurodivergent founders waste energy on manual infrastructure setup. Creating data sources and then remembering to create channels involves multiple steps and decision points. Missing channel setup means teams coordinate poorly on data work.

  • New data source coordination channels are created automatically eliminating manual setup
  • Teams have real-time coordination spaces ready immediately when data sources launch
  • Reduces decision fatigue by automating infrastructure decisions
  • Ensures data-centric work has visible coordination spaces so team does not work siloed

Setup

Build it in a few focused steps.

  • 1Connect Notion and Ably to Notis.
  • 2Create the automation: 'When a new Notion data source is created, automatically create a corresponding Ably channel for team coordination on that data.'
  • 3Select trigger: 'Data Source Created' (fires when any data source is added).
  • 4Tell Notis how to name the channel: 'use the data source name, lowercase everything, replace spaces with hyphens.'
  • 5Test by creating a new data source in Notion and verifying the Ably channel appears within seconds.

Questions about this workflow

How does Notis name the channel based on the data source name?

Tell Notis your naming convention: 'prefix with datasource-' or 'use the exact name from Notion.' It applies that rule consistently.

Can I set different naming conventions for different types of data sources?

You can create multiple automations with different naming rules, or tell Notis to inspect the data source type and apply different names for different kinds of data.

What if I create a data source but do not want an Ably channel?

You can turn off the automation temporarily or filter it: 'only create channels for data sources tagged with needs-channel.'

Can I automatically populate the channel with initial context from the data source?

Yes, you can tell Notis to post an initial message with data source metadata to the new channel, e.g., 'include the data schema and purpose.'

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.