Connect Acculynx to Bitquery

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

View example

Check wallet activity when an AccuLynx job needs attention

Use an AccuLynx webhook to start a real-time Bitquery check of a wallet tied to a job, then summarize relevant activity.

View example

Review historical blockchain activity for AccuLynx projects

On a schedule, query Bitquery archive data for a supplied project wallet and receive a concise historical review.

View example

Combine live and historical chain data for a project question

Start a combined Bitquery query from a webhook when a project question needs both historical and up-to-the-second data.

View example

Count wallet transactions for a scheduled project pulse

Run a scheduled Bitquery record count for a specified wallet and summarize the result as a simple project pulse.

View example

Count distinct wallet counterparties for a project check

When an external project signal arrives, use Bitquery to count distinct values for the queried wallet activity and explain the result.

View example

Sum token transfer values for a scheduled review

Use a scheduled Bitquery sum metric to total a selected transfer field for a specified wallet and period.

View example

Summarize token activity with selected statistics

Start a Bitquery statistics metric from an external webhook and summarize selected numerical activity for a project wallet.

View example

Track wallet activity distribution with quantiles

Schedule a Bitquery quantile calculation to understand the distribution of a numerical blockchain field for a supplied wallet query.

View example

Make multi-metric wallet results easier to read

Use GraphQL aliases when a webhook-started Bitquery query returns multiple metrics with identical field names.

Supported Triggers and Actions

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

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