Connect Jira to Documenso

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

View example

Start a signature request from a new Jira issue

Turn a newly created Jira issue into a Documenso document from a signing template, with the right recipient and details described in your instruction.

View example

Keep a Documenso recipient aligned with Jira updates

When an existing Jira issue changes, update the corresponding Documenso recipient details when the issue provides a clear correction.

View example

Send a prepared Documenso document when Jira work begins

Use a new Jira issue as the cue to distribute a matching prepared Documenso document to its pending recipients for signing.

View example

Reflect Jira changes in Documenso document details

When a Jira issue changes, update properties on its related Documenso document using the details and update conditions you describe.

Supported Triggers and Actions

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

Jira triggers

Documenso actions

Recurring trigger

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

TriggerScheduled

Create Embedding Presign Token V2 Beta

Tool to create a presign token for embedded authoring sessions. Use when initializing or renewing an embed session token.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete Document Fields

Tool to delete one or more fields from a document. Use when you have confirmed the field IDs to remove. Supports single-field and batch deletion.

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 Template

Tool to delete a template by ID.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Distribute Document V2

Tool to distribute a document for signing. Use when you need to send a document to all or specific pending recipients.

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

Download Signed Document

Tool to download a signed document file. Use when you need to retrieve the finalized PDF after a document has been signed.

ActionInstant

Duplicate Document V2

Tool to duplicate a document. Use when you need to create an exact copy of an existing document. Ensure the source document ID is valid before calling.

ActionInstant

Find Documents V2

Tool to find documents. Use when retrieving a paginated list of documents for operations requiring a document ID.

ActionInstant

Get Template

Tool to fetch a template by ID.

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.