Connect Jira to Docnify

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

View example

Update a Docnify signer from a Jira issue

Use a new Jira issue containing a Docnify document ID and corrected signer details to update that recipient in Docnify.

View example

Add a signer to a Docnify document from Jira

When a Jira issue requests a signer, use its Docnify document ID and recipient details to add the recipient.

View example

Resend a Docnify signing request after a Jira update

Use a Jira issue update that signals a follow-up is needed to resend the identified Docnify document for signing.

View example

Check Docnify document details when Jira changes

When a Jira issue is updated, fetch the Docnify document it references so Notis can report its current state and metadata.

View example

Review Docnify templates when a Jira project opens

When a Jira project is added, list available Docnify templates and report them for review as the project sets up its document process.

View example

Review Docnify documents for a Jira request

Use a new Jira document request to list Docnify documents and report the current inventory for review.

Supported Triggers and Actions

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

Jira triggers

Docnify actions

Recurring trigger

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

TriggerScheduled

Add Document Recipient

Tool to add a recipient to a document. Use after confirming the document's ID. Optionally specify signing order and authentication options.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Document Fields

Tool to create one or more fields on a document. Use after fetching a document to add fields before sending.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Delete Document

Tool to delete a specific document by its ID. Use when you have confirmed the document should be permanently removed.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Delete Document Field

Tool to delete a field from a document. Use when you need to remove a specific field from an existing document.

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Delete document recipient

Tool to remove a recipient from a document. Use after verifying document and recipient IDs to revoke access.

ActionInstant

Get Document

Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.

ActionInstant

Get Template

Tool to fetch a specific template by its ID. Use to view a template's details and metadata.

ActionInstant

List Documents

Tool to list documents in the Docnify account.

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.