Connect ActiveTrail to Bitquery

When something happens in ActiveTrail, Notis takes the next step in Bitquery. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from ActiveTrail to Bitquery

View example

Check Wallet Activity for an ActiveTrail Campaign

Use a webhook to check recent wallet activity related to a campaign before its next send.

View example

Get a Scheduled Token Transfer Brief

Run a combined historical and current token transfer query on a schedule and review the result alongside campaign plans.

View example

Count Unique Wallets Behind a Campaign Signal

Start with a webhook and count distinct wallets in a relevant Bitquery dataset for campaign research.

View example

Review Daily Token Transfer Volume

Schedule a Bitquery sum of token transfer values to get a concise volume signal for campaign research.

View example

Summarize Wallet Activity Statistics

Trigger a Bitquery statistical summary when campaign research needs a quick view of wallet activity values.

View example

Check Historical Chain Activity for Campaign Context

Run a scheduled archive query to review full historical blockchain data relevant to campaign research.

View example

Count Transactions for a Campaign Signal

Use a webhook to count matching on-chain records and quickly size a campaign research signal.

View example

Track Token Transfer Value Ranges

Schedule a Bitquery quantile calculation to see the distribution of token transfer values for campaign research.

View example

Compare Multiple Campaign Signal Metrics

Use GraphQL aliases to return clearly named metrics together when a webhook starts campaign research.

Supported Triggers and Actions

Notis builds workflows that link ActiveTrail to Bitquery. A trigger fires from one place; an action lands in another.

ActiveTrail triggers

Bitquery actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Archive Database Query

Queries historical blockchain data from an archive database.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Combined Database Query

Queries real-time and historical blockchain data across supported networks.

ActionInstant

Conditional Metrics Snippet

Generates a metric snippet with conditional logic.

ActionInstant

Database Selection

Selects the database for a GraphQL request.

ActionInstant

Early Access Program Query

Queries real-time blockchain data through an early access program.

ActionInstant

Network Selection

Selects the blockchain network for a query.

ActionInstant

Options Query

Retrieves available GraphQL dataset options.

ActionInstant

Price Asymmetry Metric

Generates a PriceAsymmetry filter snippet for GraphQL queries.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.