Connect Zendesk to Bitquery
When something happens in Zendesk, 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
Ways Notis can move work from Zendesk to Bitquery
Summarize wallet activity for every new Zendesk ticket
When a Zendesk ticket arrives, query Bitquery for the referenced wallet's recent activity and add a concise context brief for the support team.
Count transfers linked to a new Zendesk ticket
For each new ticket, count matching wallet transfers in Bitquery so support can quickly distinguish a one-off issue from repeated activity.
Find unique counterparties for every new Zendesk user
When a Zendesk user is created, use Bitquery to count unique wallet counterparties tied to the supplied address and prepare an onboarding risk signal.
Sum token movement for a Zendesk ticket
Use the wallet, token, and time range in a new Zendesk ticket to calculate total matching token movement in Bitquery.
Run a realtime Bitquery check from a webhook
Start a realtime Bitquery query whenever your monitoring system sends a webhook with a wallet, network, and query window.
Review historical wallet activity every morning
Run a scheduled Bitquery archive query to summarize prior-day wallet activity for a portfolio or operating list.
Send weekly wallet statistics to your report channel
On a weekly schedule, calculate descriptive statistics for wallet transaction values in Bitquery and summarize meaningful changes.
Track weekly transfer percentiles
Schedule Bitquery quantile calculations to reveal the median and high-end transfer ranges for selected wallets or tokens.
Filter ticket related transfers by value
When a Zendesk ticket reports suspicious activity, use Bitquery select-by-metric logic to return only transfers above the threshold in the request.
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Bitquery. A trigger fires from one place; an action lands in another.
Zendesk 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).
New User Created
Triggered when a new user is created in Zendesk.
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.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
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.
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.
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.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
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 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Zendesk and Bitquery
Connect any two apps with Notis in the middle.
Zendesk 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.