Check available Bitquery data for document-linked tokens
Before planning a token analysis, have Notis check which Bitquery query fields and arguments are available for the networks named in your documents.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Options Query
Fetches root query fields and arguments from the selected Bitquery environment's schema.
Why this helps
A token address in a form or invoice does not tell you which Bitquery dataset and query options are available for the intended network.
- Surface available Bitquery query fields and arguments before designing a deeper analysis.
- Keep token and network details from selected Algodocs documents with the discovery report.
- Call out missing network context that prevents useful schema discovery.
Setup
Build it in a few focused steps.
- 1Connect Algodocs and Bitquery once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for token query discovery.
- 3In one instruction, ask Notis to read token and network details from the relevant accessible Algodocs documents and use Bitquery schema introspection to summarize available query options.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real document containing a token identifier and its network.
Questions about this workflow
Does this workflow analyze token transfers?
No. It discovers available query fields and arguments to help plan a later query. Use an appropriate Bitquery query action for activity analysis.
What happens if the document does not name a network?
The report should flag the missing network. Schema options depend on the target network, so Notis should not guess one.
Can this create a custom Bitquery dataset?
No. It checks available schema options and reports them; it does not create datasets or guarantee that a particular field exists.
When this happens · Trigger
Do this · Action
Fetches root query fields and arguments from the selected Bitquery environment's schema.
Supported Triggers and Actions
Notis builds workflows that link Algodocs to Bitquery. A trigger fires from one place; an action lands in another.
Algodocs triggers
Bitquery actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive Database Query
Queries historical blockchain data through Bitquery's GraphQL API; coverage varies by chain.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Combined Database Query
Queries real-time and historical blockchain data across supported networks.
Conditional Metrics Snippet
Generates a conditional GraphQL metric snippet for embedding in a query.
Database Selection
Generates a GraphQL selection fragment for archive, real-time, or combined data.
Early Access Program Query
Submits a query to Bitquery for real-time blockchain data.
Network Selection
Generates a GraphQL selection fragment for a supported blockchain network.
Options Query
Fetches root query fields and arguments from the selected Bitquery environment's schema.
Price Asymmetry Metric
Generates a PriceAsymmetry filter snippet for GraphQL queries.
Connect any two apps with Notis in the middle.
Algodocs and Bitquery, or any other combination from 1,600+ 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.