Skip to content
Notis

Carry actionable Notion comments into Fibery

When a comment contains a decision or next step, let Notis turn it into a Fibery follow-up that is easier to revisit.

Trigger

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.

Action

Create Entity

Tool to create a new Fibery entity. Use when you have prepared all necessary field values and need to persist a new record. Example: Create a 'Project/Task' with title and assignee.

Why this helps

Useful decisions buried in page discussions can disappear before anyone turns them into trackable work.

  • Give actionable comments a durable place in Fibery.
  • Reduce repeated rereading of long page discussions.
  • Help turn decisions into visible next steps.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Fibery to Notis once, and ensure Notion comment access is enabled.
  • 2Create an automation in the portal or tell Notis which comments deserve follow-up.
  • 3Write one instruction describing when a comment should become a Fibery item.
  • 4Choose the Notion Comment Created trigger and a channel for run reports.
  • 5Add one test comment with a clear next step and inspect the resulting Fibery entity.

Questions about this workflow

What permissions do comment triggers need?

The Notion integration needs the Read comments capability. If it was authorized before that capability was enabled, reconnect it.

Will every comment become a follow-up?

Your instruction can ask Notis to create an item only when the comment contains a meaningful action or decision.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

Fibery actions

Recurring trigger

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

TriggerScheduled

Delete Custom App Endpoint

Tool to delete a specific custom app endpoint. Use after confirming the app and endpoint IDs to remove.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete Entity

Tool to delete a specific Fibery entity by its ID. Use when you have verified the entity exists and have its GUID. Deletion is irreversible.

ActionInstant

All Page Events

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

TriggerPolling

Delete File

Tool to delete a specific file. Use when you need to remove a file from Fibery by its ID.

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

Execute GraphQL Query

Tool to execute GraphQL queries or mutations against a Fibery space. Use when you need to fetch or modify Fibery data via the GraphQL API.

ActionInstant

New Comment

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

TriggerPolling

Authenticate (validate token via API call)

Tool to validate existing Fibery personal API token by performing a real API call. If the call succeeds, returns the token value extracted from the Authorization header. Use the returned token in the `Authorization: Token <value>` header for further calls.

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 App Information

Tool to retrieve application information. Use when you need the version, name, description, authentication methods, and available data sources before further operations.

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 Custom App Endpoints

Tool to list custom app endpoints. Use when you need the available custom endpoints for a given app before invoking them.

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 Custom Apps

Tool to list all custom apps in the Fibery workspace. Use when you need the identifiers of all custom apps.

ActionInstant

Connect any two apps with Notis in the middle.

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