Get historical token transfer context when an investigation begins
A new investigation page can ask Bitquery for archive data, so past token movements are easier to review in context.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Archive Database Query
Tool to query the archive database. use when you need full historical blockchain data (delayed by tens of minutes to hours).
Why this helps
Historical movement research can become a separate project that stalls the original investigation.
- Makes historical data retrieval part of the investigation kickoff.
- Uses the archive database for full historical blockchain data.
- Keeps the query summary close to the investigation brief.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bitquery to Notis once.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Write one prompt asking Bitquery to query archive token transfers relevant to each new investigation page and summarize the findings.
- 4Select the Notion Page Created trigger, scoped to the investigations parent page, and choose a run-report channel.
- 5Test with a real investigation page and an appropriately scoped token or wallet.
Questions about this workflow
Why choose the archive database?
Use it when the investigation needs full historical blockchain data; results may be delayed by tens of minutes to hours.
Can this run for every page in Notion?
You can scope the page-created trigger to the investigations parent page so unrelated pages do not start the workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bitquery. A trigger fires from one place; an action lands in another.
Notion triggers
Bitquery actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Aliases Metric
Tool to use graphql aliases to rename fields in the response for clarity and disambiguation. use when you need to query multiple metrics with identical field names in one call.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Archive Database Query
Tool to query the archive database. use when you need full historical blockchain data (delayed by tens of minutes to hours).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Combined Database Query
Tool to query the combined database, which merges archive and real-time databases. use when you need both historical and up-to-the-second blockchain data in one request.
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.
Conditional Metrics Snippet
Tool to generate a graphql metric snippet with conditional logic. use when you need to apply filters directly on metric calculations via the `if` attribute.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Count Distinct Metric
Tool to use the count distinct metric to aggregate unique values for a field. use when you need to count the number of unique occurrences in a dataset.
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.
Count Metric
Tool to use the count metric to aggregate the number of records matching a graphql query. use when you need simple record counts.
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.
Database Selection
Tool to select the database (archive, realtime, combined) to query at the top level of a graphql request. use after determining whether you need live, historical, or combined blockchain data.
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.
Early Access Program Query
Tool to access streaming data across various blockchain networks for evaluation purposes. use when querying chains not available via the v2 endpoint; limited to real-time data only.
Connect any two apps with Notis in the middle.
Notion and Bitquery, 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 Bitquery.