Connect new client pages to billing context
A new subpage under your client hub can prompt Notis to surface available FreshBooks businesses.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
List Businesses
Tool to list all businesses associated with the authenticated user.
Why this helps
Client work split across subpages can make it harder to remember which billing workspace is relevant.
- Make billing context available as client materials expand.
- Use the parent client page as the organizational cue.
- Keep a lightweight account lookup out of your memory stack.
Setup
Build it in a few focused steps.
- 1Connect Notion and FreshBooks to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to list FreshBooks businesses when a new subpage is added beneath a client hub.
- 3Write one plain-language instruction asking for businesses relevant to the parent client context.
- 4Choose Page Added to Page as the trigger and set the client hub parent, choose a report channel, and test with one real subpage.
Questions about this workflow
Does this fire for any page in the workspace?
This trigger is for a new subpage under the specified parent Notion page.
Can the action create a client in FreshBooks?
No. This workflow lists available FreshBooks businesses only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Freshbooks. A trigger fires from one place; an action lands in another.
Notion triggers
Freshbooks actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Businesses
Tool to list all businesses associated with the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Projects
Tool to list all projects for a business. use after confirming the business id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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 Freshbooks, 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 Freshbooks.