Choose the right blockchain database after unsubscribes
Close the loop with a deliberate data source choice before final account review.
Trigger
Unsubscribe Trigger
Triggered when a subscriber unsubscribes from Mailchimp
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
Offboarding checks can use the wrong data source and produce incomplete conclusions.
- Standardize offboarding research
- Choose archive, realtime, or combined data intentionally
- Reduce incomplete reviews
Setup
Build it in a few focused steps.
- 1Connect Mailchimp and Bitquery once in the Notis portal.
- 2Create an automation named Unsubscribe database check.
- 3Describe when to use archive, realtime, or combined data for the offboarding review.
- 4Pick the Mailchimp Unsubscribe Trigger and choose where reports should go.
- 5Test with one real unsubscribe event.
Questions about this workflow
Can Notis choose the database automatically?
Yes. State the decision rule in your instruction, or ask Notis to explain which database it selected.
Does this query blockchain data by itself?
Database selection prepares the query context. Include a query or review outcome in the instruction for a complete result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Mailchimp to Bitquery. A trigger fires from one place; an action lands in another.
Mailchimp 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).
Campaign Trigger
Triggered when a campaign is sent or experiences an event in Mailchimp
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.
Profile Update Trigger
Triggered when a subscriber's profile is updated in Mailchimp
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.
Subscribe Trigger
Triggered when a subscriber subscribes to Mailchimp
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.
Unsubscribe Trigger
Triggered when a subscriber unsubscribes from Mailchimp
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.
Mailchimp 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.