Connect Jira to Daffy

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

View example

Find charities from Jira requests

Turn a Jira issue requesting charity research into a Daffy nonprofit search, then summarize relevant matches for the team.

View example

Create Daffy gifts from approved Jira requests

When a Jira giving request is updated to an approved state, use its recipient and amount to create a Daffy gift and report the result.

View example

Verify nonprofit EINs from Jira

Check a nine-digit EIN in Daffy when a new Jira issue includes one, then summarize the nonprofit details for review.

View example

Check Daffy fund balance on request

Send a Notis webhook request to retrieve the authenticated Daffy fund balance and return a short report.

View example

Review Daffy donation history on a schedule

On a schedule, retrieve Daffy donation history and summarize recent activity for a lightweight giving review.

View example

Review Daffy gifts after Jira updates

When a Jira issue about giving is updated, retrieve Daffy gifts and summarize relevant gift records for follow-up.

Supported Triggers and Actions

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

Jira triggers

Daffy actions

Recurring trigger

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

TriggerScheduled

Create Gift

Tool to create a new charitable gift. use when you have recipient details and amount ready.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Balance

Tool to retrieve the authenticated user's fund balance. use after authenticating to confirm account funds.

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

Get Contributions

Tool to retrieve list of contributions to the authenticated user's fund. use when needing to paginate through contribution history.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Get Donations

Tool to retrieve a list of donations for the authenticated user. use after authentication to fetch donation history.

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

Get Gift by Code

Tool to retrieve details of a specific gift by its unique code. use after obtaining the gift code.

ActionInstant

Get Gifts

Tool to retrieve a list of gifts. use when you need to page or filter gifts.

ActionInstant

Get Non-Profit by EIN

Tool to retrieve information about a non-profit organization by ein. use after confirming the correct nine-digit ein.

ActionInstant

Get User Causes

Tool to retrieve a list of causes for a specified user. use after confirming the user id is valid.

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.