Resume delivery follow-up with orders in view
Update the delivery notes and pull the Goody order list into the same follow-up session.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
List All Orders
Tool to retrieve a list of all orders. Use when you need to fetch paginated order data associated with the account after authenticating.
Why this helps
Resuming delivery follow-up often means reopening several tools just to rebuild the status picture.
- Bring order data into the moment you resume follow-up.
- Reduce the mental effort of reconstructing order context.
- Keep the follow-up anchored to the Notion notes.
Setup
Build it in a few focused steps.
- 1Connect Notion and Goody to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally to refresh orders during delivery follow-up.
- 3Use one plain-language instruction asking Notis to retrieve Goody orders when the selected Notion delivery follow-up page's content changes.
- 4Select the Notion Page Content Updated trigger and choose a channel for run reports.
- 5Test with one real update to a delivery follow-up page.
Questions about this workflow
Does this update delivery status?
No. It retrieves orders so you can review them alongside the notes.
Can I scope it to a particular page?
Yes. The Page Content Updated trigger supports a page_id filter.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Goody. A trigger fires from one place; an action lands in another.
Notion triggers
Goody actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Calculate Price for Order Batch
Tool to estimate per-recipient and total price for an order batch. Use when you want to preview costs before creating the batch.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List All Active Cards
Tool to list all active digital greeting cards. Use when you need to fetch available card options before sending.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List All Active Products
Tool to list all active products. Use when you need to fetch available active products with pagination and filters.
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.
List All Order Batches
Tool to list all order batches. Use when you need to paginate through your account's order batches.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List All Orders
Tool to retrieve a list of all orders. Use when you need to fetch paginated order data associated with the account after authenticating.
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.
List All Payment Methods
Tool to list all payment methods. Use when you need to retrieve all payment methods associated with the account.
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.
List All Workspaces
Tool to list all workspaces. Use when you need to retrieve all workspaces associated with the account.
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.
Retrieve Current User
Tool to retrieve current authenticated user information. Use after authentication to fetch the current user’s account details.
Connect any two apps with Notis in the middle.
Notion and Goody, 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 Goody.