Find the CRM account from your Notion research
Update your research in Notion and have Notis look for the corresponding Fireberry record.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Fireberry: Query Records
Tool to query records with filtering, sorting, and pagination. use when you need to retrieve specific fireberry records by module.
Why this helps
Switching between research notes and a CRM search interrupts the work of understanding an account.
- Reduce repetitive CRM searches during account research.
- Bring existing account context into the workflow.
- Keep research review focused on the customer.
Setup
Build it in a few focused steps.
- 1Connect Notion and Fireberry to Notis once through the portal.
- 2Create the automation in the portal or ask Notis in plain language.
- 3Tell Notis to query Fireberry for the account related to a changed Notion research page and report any matching record.
- 4Select Page Content Updated scoped to your research page or database, choose a report channel, and test with one real account.
Questions about this workflow
Does this update the Fireberry account?
No. This workflow queries Fireberry records and surfaces a match; its action does not modify a record.
Can it run only for a research database?
Yes. Scope Page Content Updated to the relevant Notion data source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Fireberry. A trigger fires from one place; an action lands in another.
Notion triggers
Fireberry actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a new Fireberry record
Tool to create a new record in a specified fireberry table. use when you have the table name and record data ready for insertion.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Picklist Values
Tool to retrieve all possible picklist (dropdown) values for a specific field. use when you need to load all available options for a picklist field in a record type.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Fireberry: Query Records
Tool to query records with filtering, sorting, and pagination. use when you need to retrieve specific fireberry records by module.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Fireberry, 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 Fireberry.