Skip to content
Notis

Support new finance views with wallet inventory

A new finance view can be a good moment to bring the Coinbase wallet list into view for the people setting it up.

Trigger

View Created

Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.

Action

List Wallets

Retrieve all wallets from coinbase via the cdp sdk.

Why this helps

Creating a helpful view is one more workflow change, and related account context can be easy to miss.

  • Prompts a wallet lookup as a finance view is introduced.
  • Keeps setup context available in the run-report channel.
  • Helps reduce context switching during process changes.

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 a finance view is created.
  • 3Select the Notion View Created trigger and describe the finance use case in the prompt.
  • 4Choose a reporting channel and test with one real finance view.

Questions about this workflow

Does it support every view type?

The trigger reports the view type. Describe the finance context in the prompt so Notis can interpret the event.

Does this action analyze the view?

No. It retrieves Coinbase wallets and places the result in the run 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.