See the full wallet picture from a matched research file
Bring long-range context and current wallet activity together when a Drive research file matches your query.
Trigger
New File Matching Query
Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.
Action
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.
Why this helps
Separate historical and current checks leave founders stitching together the wallet story by hand.
- Brings recent and historical activity into one query flow.
- Starts only when a new file meets the saved Drive query.
- Reduces manual reconciliation between separate data windows.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Bitquery once in the Notis portal.
- 2Create an automation in the portal or by telling Notis in plain language.
- 3In one instruction, ask Notis to use the matched file's wallet, chain, and period to query combined Bitquery data and summarize historical plus current activity.
- 4Pick the Google Drive New File Matching Query trigger and choose where run reports go.
- 5Test with one real file that matches the configured Drive query and includes the query inputs.
Questions about this workflow
Does a matched file guarantee it contains a wallet and chain?
No. The file matching trigger identifies files based on the provided Drive query. The wallet and chain still need to be in the file or supplied in the instruction.
Why use the combined database?
Use it when one request needs historical and up-to-the-second data together.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Bitquery. A trigger fires from one place; an action lands in another.
Google Drive 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).
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
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.
File Created
Triggers when a new file is created in Google Drive.
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.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
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.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
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.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
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.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
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.
Google Drive 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.