Use the right Bitquery database for each review
Make data freshness and historical coverage an explicit part of every scheduled query.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
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.
Why this helps
Reports become unreliable when a query uses the wrong balance of freshness and historical depth.
- Match data source to the decision
- Reduce stale or incomplete reports
- Document query assumptions clearly
Setup
Build it in a few focused steps.
- 1Connect 21risk and Bitquery in Notis once.
- 2Create an automation named Scheduled database mode review.
- 3Tell Notis the review goal and instruct it to select archive, realtime, or combined Bitquery data, then explain the choice in the report.
- 4Choose a recurring cron trigger and a report channel.
- 5Test with one historical and one live-oriented example.
Questions about this workflow
Can the database choice change by run?
Yes. State the decision rule, such as historical investigations use archive and current monitoring uses realtime.
What if both are needed?
Ask Notis to use the combined database and describe the required time span.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 21risk to Bitquery. A trigger fires from one place; an action lands in another.
21risk 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).
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.
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.
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.
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.
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.
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.
21risk 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.