Count unique wallets behind token activity
Get a distinct-wallet count for a token question without manually tallying addresses.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Repeated addresses make manual wallet counts slow and prone to mistakes, especially when a chat question arrives mid-task.
- Count unique values instead of tallying repeated records.
- Keep token, chain, and requested period explicit in the query request.
- Return a compact count that is easy to share in chat.
Setup
Build it in a few focused steps.
- 1Connect 2chat and Bitquery once in the Notis portal.
- 2Create an automation in Notis and give it a clear name.
- 3Tell Notis to use a count distinct metric for the wallet field in matching token activity data, using the requested network and period.
- 4Choose the Notis webhook trigger and configure the request to include the token question.
- 5Choose a report channel, then test with one real token and network.
Questions about this workflow
What information should the request include?
Name the blockchain network, token or relevant dataset, and time period. If the query cannot identify the relevant data, Notis should ask for clarification.
Is this an exact count?
The listed action is a count distinct metric. The actual result depends on the query and data returned.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 2chat to Bitquery. A trigger fires from one place; an action lands in another.
2chat 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.
2chat 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.