Turn Notion grocery comments into shopping lists
A grocery request in a Notion comment can become a list you can review, instead of another detail to remember later.
Trigger
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.
Action
Create Shopping List Page
Create a shopping list page on instacart + return shareable url. attempts prod first then falls back to dev; errors from prod bubble up if both fail.
Why this helps
Useful requests can disappear inside page discussions before anyone turns them into a practical list.
- Turn a written request into a shareable list.
- Reduce the need to revisit comment threads to remember what was requested.
- Keep a clear link between the discussion and the resulting list.
Setup
Build it in a few focused steps.
- 1Connect Notion and Instacart to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally for this workflow.
- 3Use one plain-language instruction to create a list only for comments that make a grocery request clear.
- 4Choose the Notion Comment Created trigger and a channel for run reports.
- 5Test with one comment that names specific groceries and review the resulting list.
Questions about this workflow
Can this listen for comments across my workspace?
The trigger can fire for comments the integration can access. The prompt should describe which comments count as grocery requests.
What if a comment is vague?
Write the instruction to create a list only when the request contains enough detail to identify the groceries.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Instacart. A trigger fires from one place; an action lands in another.
Notion triggers
Instacart actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Recipe Page
Create a recipe page on instacart + return shareable url. attempts prod first then falls back to dev; errors from prod bubble up if both fail.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Shopping List Page
Create a shopping list page on instacart + return shareable url. attempts prod first then falls back to dev; errors from prod bubble up if both fail.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Nearby Retailers
Get nearby retailers by postal code + country code. attempts prod first then falls back to dev; errors from prod bubble up if both fail.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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 Instacart, 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 Instacart.