Skip to content
Notis

Turn receipt records into expense entries

A new purchase record in Notion can prompt Notis to create its matching expense in Brex.

Trigger

New Page

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

Action

Create Expense

Create a new expense.

Why this helps

Receipts collected during a busy day can be forgotten when expense entry is postponed until later.

  • Move expense capture closer to receipt collection.
  • Reduce end-of-week memory work.
  • Keep purchase documentation connected to finance processing.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Brex to Notis once through the portal.
  • 2Create an automation asking Notis to create a Brex expense for each new receipt record in the selected Notion database.
  • 3Select the Notion New Page trigger for the receipt database.
  • 4Choose a channel for run reports.
  • 5Test with one real receipt record and check the created expense.

Questions about this workflow

Can this use a dedicated receipt database?

Yes. Select the New Page trigger for that database and describe receipt records in the prompt.

Will it handle a receipt that is updated later?

This workflow starts on a new page. A separate properties-update workflow can handle later changes if needed.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Brex. A trigger fires from one place; an action lands in another.

Notion triggers

Brex actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Budget

Create a new budget for departments or projects.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Card

Create a new card and assign it to a user.

ActionInstant

All Page Events

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

TriggerPolling

Create Department

Create a new department.

ActionInstant

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

Create Expense

Create a new expense.

ActionInstant

New Comment

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

TriggerPolling

Create Location

Create a new location.

ActionInstant

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

Create Job Title

Create a new job title.

ActionInstant

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

Create User

Create a new user in the brex account.

ActionInstant

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

Create Vendor Card

Create a new vendor card.

ActionInstant

Connect any two apps with Notis in the middle.

Notion and Brex, 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 Brex.