Skip to content
Notis

Help the team find the right view

Make a new way of seeing work easier to adopt by explaining it where the related design process already lives.

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

Add a comment to a file

Posts a new comment to a figma file or branch, optionally replying to an existing root comment (replies cannot be nested); `region height` and `region width` in `client meta` must be positive if defining a comment region.

Why this helps

A useful view can go undiscovered, leaving people to rely on old habits or duplicate tracking.

  • Explains relevant new views to design collaborators.
  • Supports consistent use of the team's tracking process.
  • Reduces confusion about where to check for updates.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Figma to Notis once through the portal.
  • 2Create an automation in the portal or tell Notis what outcome you want.
  • 3Ask Notis to assess new Notion views and comment in the relevant Figma process file when the view changes how design work is tracked.
  • 4Select Notion View Created, choose a channel for run reports, and test with a view used by the design team.

Questions about this workflow

Does this trigger tell Notis the view type?

Yes. The event includes the view type and parent context, which can help Notis decide if the view matters to the design team.

Will it announce every view?

The instruction should ask Notis to comment only when a new view changes a relevant design workflow.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Figma. A trigger fires from one place; an action lands in another.

Notion triggers

Figma actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add a comment to a file

Posts a new comment to a figma file or branch, optionally replying to an existing root comment (replies cannot be nested); `region height` and `region width` in `client meta` must be positive if defining a comment region.

ActionInstant

Webhook trigger

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

TriggerInstant

Add a reaction to a comment

Posts a specified emoji reaction to an existing comment in a figma file or branch, requiring valid file key and comment id.

ActionInstant

All Page Events

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

TriggerPolling

Create a webhook

Creates a figma webhook for a `team id` to send post notifications for an `event type` to a publicly accessible https `endpoint`; an initial ping is sent unless `status` is `paused`.

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

Create dev resources

Creates and attaches multiple uniquely-urled development resources to specified figma nodes, up to 10 per node.

ActionInstant

New Comment

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

TriggerPolling

Create, modify, or delete variables

Manages variables, collections, modes, and their values in a figma file via batch create/update/delete operations; use temporary ids to link new related items in one request and ensure `variablemodevalues` match the target variable's `resolvedtype`.

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

Delete a comment

Deletes a specific comment from a figma file or branch, provided the authenticated user is the original author of the comment.

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

Delete a reaction

Deletes a specific emoji reaction from a comment in a figma file; the user must have originally created the reaction.

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

Delete a webhook

Permanently deletes an existing webhook, identified by its unique `webhook id`; this operation is irreversible.

ActionInstant

Connect any two apps with Notis in the middle.

Notion and Figma, 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 Figma.