Skip to content
Notis

Connect a new tracker item to FreshBooks projects

A new project tracker entry can bring the available FreshBooks projects into your follow-up while the details are fresh.

Trigger

New Page

Triggers when a new page is added to a Notion database.

Action

List Projects

Tool to list all projects for a business. use after confirming the business id.

Why this helps

New work gets captured in a tracker, but the billing project lookup is often left for later.

  • Pair project capture with a billing project directory check.
  • Keep the new work's context in the automation instruction.
  • Make project setup easier to complete in one sitting.

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 projects when a new Notion tracker item is added.
  • 3Use one plain-language instruction to describe the tracker context and business, then ask for relevant projects.
  • 4Choose New Page as the trigger, choose a report channel, and test with one real tracker item.

Questions about this workflow

Will this match and update an existing FreshBooks project automatically?

It lists the available projects; verify a suitable match before taking further action.

Can it run for a specific data source?

The New Page trigger supports a data source scope.

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.

TriggerScheduled

List Businesses

Tool to list all businesses associated with the authenticated user.

ActionInstant

Webhook trigger

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

TriggerInstant

List Projects

Tool to list all projects for a business. use after confirming the business id.

ActionInstant

All Page Events

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

TriggerPolling

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

New Comment

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

TriggerPolling

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

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

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

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.