Connect Notion to Fibery
When something happens in Notion, Notis takes the next step in Fibery. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Fibery
Turn Notion tasks into Fibery work
Create a Fibery task when a new task page appears in Notion, so commitments move into the workspace where you track delivery.
Keep Fibery task status aligned
When task properties change in Notion, ask Notis to update the related Fibery entity so progress does not lag behind your latest decision.
Turn Notion comments into Fibery follow-up
Use a new Notion comment as a cue for Notis to create a Fibery follow-up when discussion contains a decision or action worth tracking.
Refresh Fibery project context from Notion
When a project brief's body changes in Notion, prompt Notis to update the matching Fibery project context so important decisions travel with the work.
Move selected Notion ideas into Fibery
When a new idea page is created in Notion, let Notis create a Fibery item for ideas you want to consider without interrupting your capture flow.
Create Fibery follow-up from meeting notes
When a meeting notes subpage appears under a Notion meeting hub, ask Notis to create a Fibery follow-up entity from its agreed next steps.
Update Fibery from a decision comment
Use a comment on a specified Notion page to cue Notis to update the linked Fibery entity when a decision changes the working plan.
Record Notion database changes in Fibery
When a Notion data source schema changes, create a Fibery review item so structural changes that affect a workflow do not go unnoticed.
Log new Notion views for workspace review
When someone creates a Notion view, record a Fibery review item so the team can decide whether it changes how work is found or handled.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and Fibery
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.