Move confirmed newsletter signups into Goodbits
Record a confirmed signup in Notion and let Notis add that person to Goodbits.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Create Subscriber
Tool to add a new subscriber to the newsletter. Use after confirming user opt-in.
Why this helps
Copying an opted-in contact by hand creates delay and another chance to miss a newsletter signup.
- Move confirmed signups into your newsletter tool promptly.
- Reduce repetitive subscriber entry.
- Keep consent as part of the decision to add a contact.
Setup
Build it in a few focused steps.
- 1Connect Notion and Goodbits to Notis once in the portal.
- 2Create an automation through the portal or ask Notis in plain language.
- 3In one instruction, ask Notis to create a Goodbits subscriber only for a contact whose Notion record confirms newsletter opt-in.
- 4Choose Page Properties Updated and a channel for run reports.
- 5Test with one real, consented signup and verify its status in Goodbits.
Questions about this workflow
Can this add contacts who have not opted in?
The instruction should require a clear, recorded confirmation of opt-in before creating a subscriber.
What triggers the workflow?
A Notion page property update triggers it; describe the eligible signup record in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Goodbits. A trigger fires from one place; an action lands in another.
Notion triggers
Goodbits actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Link
Tool to create a content link in Goodbits Content Library. Use when you have an article URL and optional metadata ready.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Subscriber
Tool to add a new subscriber to the newsletter. Use after confirming user opt-in.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Subscriber
Tool to mark a subscriber as deleted. Use when you need to prevent future emails being sent to a subscriber.
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 Newsletter Info
Tool to fetch newsletter identifier and name. Use after authenticating with your API token.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Update Subscriber Status
Tool to update subscriber status. Use when you need to change an existing subscriber’s subscription status by email. Example: "Update the status of john@example.com to unsubscribed"
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Goodbits, 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 Goodbits.