Connect Abstract to Daffy

When something happens in Abstract, 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 Abstract to Daffy

View example

Turn a giving note into charity matches

Send an unstructured giving idea to a Notis webhook. Abstract can process the text, and Notis searches Daffy for nonprofit matches using the supplied cause ID and query.

View example

Create a gift from an approved giving request

Start from a webhook request with a confirmed nonprofit recipient and donation amount. Use Abstract to process the accompanying text and Daffy to create the gift.

View example

Keep a scheduled view of your Daffy fund balance

Run a recurring Daffy balance check and send the result to your chosen Notis report channel, so you can plan giving with current account information.

View example

Review your Daffy donation history regularly

On a recurring schedule, retrieve donation history from Daffy and have Notis summarize the returned records in your run report.

View example

Look up a Daffy gift by code

Send a known Daffy gift code to a Notis webhook and retrieve details for that specific gift in the run report.

View example

Review contributions to your Daffy fund

Schedule a recurring retrieval of contributions to your authenticated Daffy fund and summarize the returned records in a Notis report.

View example

Check nonprofit details from an EIN

Send a confirmed nine-digit EIN to a Notis webhook to retrieve the nonprofit information Daffy has for that organization.

View example

Retrieve causes for a Daffy user

Submit a valid Daffy user ID through a Notis webhook to retrieve the causes associated with that user.

View example

Retrieve your authenticated Daffy profile

Use a webhook request to retrieve the profile for the authenticated Daffy account and send the result to your selected run report channel.

Supported Triggers and Actions

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

Abstract triggers

Daffy actions

Recurring trigger

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

TriggerScheduled

Create Gift

Creates a charitable gift.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Balance

Retrieves the authenticated user's Daffy fund balance.

ActionInstant

Get Contributions

Retrieves contributions made to the authenticated user's Daffy fund.

ActionInstant

Get Donations

Retrieves donation history from the authenticated user's Daffy account.

ActionInstant

Get Gift by Code

Retrieves details of a gift by its unique code.

ActionInstant

Get Gifts

Retrieves gifts associated with the user's Daffy account.

ActionInstant

Get Non-Profit by EIN (v2)

ActionInstant

Get User Causes

Retrieves the charitable causes associated with a user's Daffy fund.

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.