Select the right data coverage for each query
Tell Notis whether the request needs live, historical, or combined coverage, and get the query aimed at the appropriate database.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Choosing the wrong data coverage can return stale results or leave history out of an otherwise useful analysis.
- Match a query to live, historical, or combined coverage.
- Make data freshness and coverage requirements explicit.
- Reduce mistakes caused by selecting the wrong database.
Setup
Build it in a few focused steps.
- 1Connect Bitquery once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Describe the query need and whether it requires archive, realtime, or combined data.
- 4Pick a webhook trigger and choose where run reports go.
- 5Test with one real request and verify the selected coverage fits the question.
Questions about this workflow
Can this action decide which database is best?
The instruction should state whether the need is live, historical, or combined. Notis can use that requirement to select the database.
What does combined mean?
The combined database merges archive and realtime databases.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Hubspot to Bitquery. A trigger fires from one place; an action lands in another.
Hubspot 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).
Contact Created Trigger
Contact Created Trigger
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.
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
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.
Hubspot 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.