Connect Blocknative to Jira

When something happens in Blocknative, Notis takes the next step in Jira. 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 Blocknative to Jira

View example

Create Jira tickets for high-risk pending transactions

Turn Blocknative mempool alerts into Jira issues so your team can investigate transactions that may need attention.

View example

Turn a scheduled mempool review into Jira follow-ups

On a schedule, review Blocknative data supplied to Notis and create Jira follow-up issues for transactions that meet your criteria.

View example

Add transaction status updates to Jira issues

Send Blocknative transaction status changes to a Notis webhook and append the supplied update to its Jira issue.

View example

Update Jira issues with reported gas fee changes

When a Blocknative webhook reports a relevant gas fee change, update the matching Jira issue with the supplied details.

View example

Assign transaction investigations in Jira

Use a Blocknative webhook report to assign the matching Jira issue to a person or leave it unassigned based on your instruction.

View example

Link related transaction investigations in Jira

When supplied Blocknative data identifies related transactions, link their Jira issues to give the investigation a shared trail.

View example

Find stale transaction investigations for review

On a schedule, search Jira for transaction investigation issues that may need follow-up, using criteria you define and available data.

View example

Transition Jira investigations when transactions resolve

Use a Blocknative webhook status report to transition the related Jira issue when your stated resolution criteria are met.

View example

Triage the transaction investigation backlog

Schedule a review of available Blocknative context and Jira transaction issues, then use Jira search to surface work matching your triage rules.

Supported Triggers and Actions

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

Blocknative triggers

Jira actions

Recurring trigger

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

TriggerScheduled

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

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.