Skip to content
Notis

Keep finance planning and wallet context together

When a finance page changes, prompt a fresh Coinbase wallet inventory and have the report ready in your chosen channel.

Trigger

All Page Events

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

Action

List Wallets

Retrieve all wallets from coinbase via the cdp sdk.

Why this helps

Planning updates and account context can drift apart when they are maintained in different places.

  • Pairs workspace page activity with a wallet inventory lookup.
  • Keeps a fresh report available during active planning.
  • Makes the finance context easier to regain after switching tasks.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Coinbase to Notis once in the portal.
  • 2Create an automation with a plain-language instruction to retrieve Coinbase wallets when finance planning pages change.
  • 3Select the Notion All Page Events trigger and describe the finance context in the prompt.
  • 4Choose a channel for run reports and test with a real finance page update.

Questions about this workflow

Will every page update trigger the lookup?

All Page Events can trigger for pages across the accessible workspace. Describe the finance context in your prompt to guide Notis.

Can this identify wallet balances?

The listed action retrieves wallets. The workflow should not be treated as a balance or valuation report.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

Coinbase actions

Recurring trigger

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

TriggerScheduled

List Wallets

Retrieve all wallets from coinbase via the cdp sdk.

ActionInstant

Webhook trigger

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

TriggerInstant

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 Coinbase, 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 Coinbase.