Connect Adyntel to Bitquery

When something happens in Adyntel, 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 Adyntel to Bitquery

View example

Check on-chain activity after a campaign launch

When a campaign launches, compare its timing with current and historical blockchain activity for the token or wallet you specify.

View example

Review competitor ads alongside wallet activity

On a recurring schedule, review Adyntel competitor ad insights and query Bitquery's real-time database for the wallet or token you provide.

View example

Research token history behind an ad insight

Send a webhook when an Adyntel insight merits research, then query Bitquery's archive database for the token's historical activity.

View example

Count token transfers during a campaign window

On a schedule, use Adyntel campaign context and a Bitquery count metric to review transfer volume for a specified token and time window.

View example

Count unique wallets around a campaign

Trigger a review by webhook and use Bitquery's distinct count metric to estimate or count unique wallets for the specified token and period.

View example

Sum token activity for campaign reviews

On a recurring schedule, combine Adyntel campaign context with Bitquery's sum metric to total a specified field across chosen dimensions.

View example

Summarize wallet activity statistics for ad research

Use an ad research webhook to request Bitquery statistics such as mean or median for a specified wallet activity variable.

View example

Track token activity distribution by quantile

Schedule a Bitquery quantile review of a specified numerical field, with Adyntel campaign context included in the report.

View example

Label overlapping metrics in a campaign query

When an ad research question needs several similarly named metrics, use Bitquery aliases to make the returned fields easier to distinguish.

Supported Triggers and Actions

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

Adyntel 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.