Turn a Notion webhook request into a Givebutter subscription
Capture the setup request in Notion and ask Notis to create the Givebutter webhook once its endpoint is ready.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Webhook
Tool to create a new webhook subscription. use when you need to receive real-time notifications programmatically after confirming your endpoint can validate givebutter's signing secret.
Why this helps
Webhook setup can linger in a task database after the team has already prepared the endpoint and needed event details.
- Start webhook setup from the team's existing request process.
- Reduce manual re-entry of reviewed setup details.
- Make the request easier to hand off and track.
Setup
Build it in a few focused steps.
- 1Connect Notion and Givebutter to Notis once in the portal.
- 2Confirm the endpoint can validate Givebutter's signing secret before using Create Webhook.
- 3Create an automation in the portal or ask Notis to create a Givebutter webhook when a ready setup request is added to Notion, describing the request in one plain-language instruction.
- 4Select New Page for the webhook request database, choose a report channel, and test with one approved request.
Questions about this workflow
What must be ready before creating a webhook?
The endpoint should be ready to validate Givebutter's signing secret, and the request should contain the necessary setup details.
Does this create a subscription immediately?
The selected action creates a webhook subscription when the automation runs. Use it only for requests that are ready for setup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Givebutter. A trigger fires from one place; an action lands in another.
Notion triggers
Givebutter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive Contact
Tool to archive a contact by their id. use after ensuring the contact has no associated data (e.g., no transactions or communications). example: "archive contact abc123".
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Campaign
Tool to create a new campaign. use when you have title, description, goal, and type ready, after confirming your givebutter account is authenticated.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Webhook
Tool to create a new webhook subscription. use when you need to receive real-time notifications programmatically after confirming your endpoint can validate givebutter's signing secret.
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.
Delete Campaign
Tool to delete a campaign by its id. use after confirming the campaign has no funds raised. example: "delete campaign abc123".
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Contact
Tool to delete a contact by their id. use after confirming the contact has no associated data (e.g., no transactions or communications). example: "delete contact abc123".
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.
Delete Fund
Tool to delete a fund by its id. use when you need to remove a fund after confirming it exists. example: "delete fund fund abc123".
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.
Delete Webhook
Tool to delete a webhook by its id. use when you need to remove an obsolete webhook after confirming no further events are needed. example: "delete webhook abc123".
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 Fund
Tool to retrieve details of a specific fund by its id. use after confirming the fund id is valid.
Connect any two apps with Notis in the middle.
Notion and Givebutter, 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 Givebutter.