Review Daffy causes when you organize a giving view
Create a view for your giving work and have Notis retrieve Daffy causes so the priorities behind the view stay close at hand.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
Get User Causes
Tool to retrieve a list of causes for a specified user. use after confirming the user id is valid.
Why this helps
Organizing a new view can make work feel tidier without prompting a check that the underlying priorities still fit.
- Pair workspace organization with a priorities check.
- Make existing causes easier to revisit.
- Keep a lightweight review attached to a planning change.
Setup
Build it in a few focused steps.
- 1Connect Notion and Daffy to Notis once in the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Write one prompt asking Notis to retrieve Daffy causes when a giving-related view is created and return a short review reminder.
- 4Choose View Created and select a channel for run reports.
- 5Test by creating one real view for giving work and review the report.
Questions about this workflow
Will any new view trigger this?
The trigger is workspace-wide, so the prompt should have Notis proceed only when the view context indicates giving work.
Can this change my Daffy causes?
No. It retrieves them for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Daffy. A trigger fires from one place; an action lands in another.
Notion triggers
Daffy actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Gift
Tool to create a new charitable gift. use when you have recipient details and amount ready.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Balance
Tool to retrieve the authenticated user's fund balance. use after authenticating to confirm account funds.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Contributions
Tool to retrieve list of contributions to the authenticated user's fund. use when needing to paginate through contribution history.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Get Donations
Tool to retrieve a list of donations for the authenticated user. use after authentication to fetch donation history.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Gift by Code
Tool to retrieve details of a specific gift by its unique code. use after obtaining the gift code.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Get Gifts
Tool to retrieve a list of gifts. use when you need to page or filter gifts.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Get Non-Profit by EIN
Tool to retrieve information about a non-profit organization by ein. use after confirming the correct nine-digit ein.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Get User Causes
Tool to retrieve a list of causes for a specified user. use after confirming the user id is valid.
Connect any two apps with Notis in the middle.
Notion and Daffy, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Daffy.