Review donation history when your Notion tracker changes
When your giving tracker structure changes, have Notis retrieve Daffy donation history to help you assess what the updated review needs.
Trigger
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.
Action
Get Donations
Tool to retrieve a list of donations for the authenticated user. use after authentication to fetch donation history.
Why this helps
A tracker redesign can leave useful history checks out of a founder's updated routine.
- Turn structural changes into a process-review prompt.
- Keep donation history visible while updating your tracker.
- Reduce the chance that a new workflow loses an old check.
Setup
Build it in a few focused steps.
- 1Connect Notion and Daffy to Notis once in the portal.
- 2Create an automation through the portal or by asking Notis conversationally.
- 3Use one prompt asking Notis to retrieve Daffy donation history after the selected data source schema changes and provide a brief review reminder.
- 4Choose Data Source Schema Updated for the donation tracker and select a channel for run reports.
- 5Test after a planned schema change and check the report.
Questions about this workflow
Does this run for every row update?
No. It uses the schema-updated event, which is meant for structural changes such as adding or renaming columns.
Does the workflow update my tracker?
No. It retrieves history and offers a review prompt; it does not change the Notion schema.
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.