Broadcast New Views to Your Team
You create a new Notion report view to help the team track project status, but nobody knows it exists. They keep using the old view. Notis announces new views on WhatsApp with a description and link, so people see what you built and use it.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
Create Contact
Tool to create a new contact in your 2chat account. use after gathering and verifying first name and at least one contact detail (email, phone, or address).
Why this helps
New views/reports built but team doesn't know they exist; effort wasted on unused tools.
- Announce new views instantly so teams find them
- Reduce wasted effort on unused reports
- Drive adoption of useful new databases
- Celebrate wins on shared channels
Setup
Build it in a few focused steps.
- 1Connect Notion and 2chat.
- 2Create automation: 'When a new view is created in any of my databases, send a WhatsApp to my team channel announcing the view name, type, and what it's used for.'
- 3Select trigger: View Created from Notion.
- 4Set notification channel.
- 5Test by creating a new view (e.g., a board view or timeline) in Notion and checking the team WhatsApp.
Questions about this workflow
How does Notis know what a view is for?
Include a description in the Notion view, or tell Notis the context (e.g., 'This is a status dashboard for Q4 projects').
Can I announce only certain view types?
Yes. Filter to announce only board views, timeline views, or calendar views if others are less important.
What if views are created just for testing?
Tell Notis to check for a 'Keep Private' or 'Do Not Share' tag in the view name to skip announcements.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to 2chat. A trigger fires from one place; an action lands in another.
Notion triggers
2chat actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Contact
Tool to create a new contact in your 2chat account. use after gathering and verifying first name and at least one contact detail (email, phone, or address).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get API Usage Info
Tool to retrieve current api usage and account information. use when you need to monitor your remaining quotas before sending more requests.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Contacts
Tool to list all contacts in your 2chat account. use when you need to retrieve your contact list after confirming your account connection.
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.
List Webhook Subscriptions
Tool to list all configured webhook subscriptions. use when you need to audit or review your active whatsapp webhook subscriptions.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Test API Key
Tool to validate your api key and retrieve account info. use when confirming credentials before performing other operations.
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 2chat, 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 2chat.