Give captured Notion ideas a Fibery home
Capture an idea quickly in Notion, then let Notis add it to Fibery when it is ready for consideration.
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
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
Ideas captured in the moment often stay buried because moving them into a review space takes extra effort.
- Protect fast idea capture from administrative overhead.
- Give selected ideas a searchable review home.
- Make it easier to return to promising thoughts later.
Setup
Build it in a few focused steps.
- 1Connect Notion and Fibery to Notis once.
- 2Create an automation in the portal or describe which new idea pages should enter Fibery.
- 3Write one plain-language instruction for creating the idea entity.
- 4Select the Notion Page Created trigger, optionally scoped to the idea parent page, and choose a reporting channel.
- 5Create one real idea page and check the new Fibery entry.
Questions about this workflow
Can this be limited to an idea page hierarchy?
Yes. Page Created can be scoped to new subpages under a specified parent page.
Does every page need to become an idea?
Tell Notis which pages count as ideas and when to skip a page in the instruction.
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.
Delete Custom App Endpoint
Tool to delete a specific custom app endpoint. Use after confirming the app and endpoint IDs to remove.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete File
Tool to delete a specific file. Use when you need to remove a file from Fibery by its ID.
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.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
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.
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.
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.
Get Custom Apps
Tool to list all custom apps in the Fibery workspace. Use when you need the identifiers of all custom apps.
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.