Skip to content
Notis

Make feedback easier to act on

Bring new feedback into the design workspace with enough context to decide whether action is needed.

Trigger

Page Created

Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.

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

Feedback captured in a database can feel like another inbox to monitor, especially when design work is moving quickly.

  • Puts relevant new feedback where design decisions happen.
  • Adds context without requiring manual copying.
  • Helps prevent useful feedback from going stale.

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 you want in plain language.
  • 3Ask Notis to locate the related Figma file for each new feedback record and post a concise review comment with a link to the source item.
  • 4Select Notion New Page, choose a channel for run reports, and test with a real feedback record.

Questions about this workflow

Can Notis avoid posting duplicate feedback?

Ask Notis to check for an existing comment or resource referencing the same feedback before creating a new one.

Can the trigger be limited to a feedback database?

Yes. Scope the New Page trigger to the data source where feedback records are created.

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.