Auto-Generate Metric Field Aliases for Complex Queries
Automatically generate GraphQL aliases when creating blockchain analysis issues, eliminating manual field renaming and disambiguation errors.
When something happens in Linear, 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
Triggers when a new comment is received.
Do this · Action
Queries historical blockchain data through Bitquery's GraphQL API; coverage varies by chain.
Automatically generate GraphQL aliases when creating blockchain analysis issues, eliminating manual field renaming and disambiguation errors.
Automatically query Bitquery's archive database for historical token balances when you create a Linear issue about token analysis.
When you comment asking for pool data, Notis instantly queries Bitquery's combined database for liquidity pool details and trading pairs.
When issue priority changes, automatically apply conditional filters to blockchain metrics, showing only data relevant to the priority level.
When you create an issue about wallet analysis, Notis automatically counts unique wallets interacting with your token or contract.
When you update an issue with contract details, Notis automatically counts how many times the contract is being called.
When you create a project, Notis determines whether to use archive or real-time Bitquery databases based on your project needs.
When you create an issue about testnet or early-access chains, Notis pulls data from Bitquery's early-access program.
When you update an issue (e.g., assign it to someone), Notis streams real-time mempool pending transactions for monitoring.
Notis builds workflows that link Linear to Bitquery. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Queries historical blockchain data through Bitquery's GraphQL API; coverage varies by chain.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Queries real-time and historical blockchain data across supported networks.
Triggers when a new comment is received.
Generates a conditional GraphQL metric snippet for embedding in a query.
Triggers when a new issue is created.
Generates a GraphQL selection fragment for archive, real-time, or combined data.
Triggers when an issue is updated, such as when its labels or status change.
Submits a query to Bitquery for real-time blockchain data.
Triggers when a comment is posted on an issue in a private team.
Generates a GraphQL selection fragment for a supported blockchain network.
Triggers when an issue appears in a private team.
Fetches root query fields and arguments from the selected Bitquery environment's schema.
Triggers when an issue's properties change in a private team.
Generates a PriceAsymmetry filter snippet for GraphQL queries.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
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:
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.
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Linear and Bitquery, or any other combination from 1,500+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Bitquery.