Review your Countdown collections when research notes change
When a research page gets updated, have Notis check the available collections so you can keep your eBay research activity in view.
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 Collections
Tool to list all collections for the authenticated account. Use when you need to retrieve paginated collections with filtering, sorting, and timing constraints.
Why this helps
Collection activity can become hard to track when research plans shift across scattered notes.
- Retrieve the current collection list when research context changes.
- Keep collection review connected to the notes that prompted it.
- Reduce the need to switch tools just to check what collections exist.
Setup
Build it in a few focused steps.
- 1Connect Notion and Countdown api to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally for this workflow.
- 3In one plain-language instruction, ask Notis to retrieve the Countdown collections when the relevant research page content changes.
- 4Pick the Notion Page Content Updated trigger, choose a channel for run reports, and test with one real page edit.
Questions about this workflow
Does this start a collection?
No. It lists the collections available to the connected Countdown api account.
Can I limit it to a research page?
Describe the intended page in the plain-language automation prompt and select the matching Notion page trigger scope when setting it up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Countdown api. A trigger fires from one place; an action lands in another.
Notion triggers
Countdown api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clear Collection Requests
Tool to clear all requests from a specified collection. Use when you need to remove all queued requests for an idle collection.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a new collection
Tool to create a new collection. Use when you need to batch and orchestrate multiple requests on a schedule.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Collection
Tool to retrieve details for a single collection by ID. Use when you need collection metadata and counts for a given collection ID.
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 Collections
Tool to list all collections for the authenticated account. Use when you need to retrieve paginated collections with filtering, sorting, and timing constraints.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Start Collection
Tool to start processing a collection's queued requests. Use after creating or pausing a collection to initiate its queued requests.
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.
Update an existing collection
Tool to update an existing collection. Use when you need to modify collection settings before scheduling runs.
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.
eBay Autocomplete
Tool to fetch eBay autocomplete suggestions. Use when needing search-term-based suggestions from Countdown API.
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.
Create Destination
Tool to create a destination. Use when you need to set up a new destination for results or notifications.
Connect any two apps with Notis in the middle.
Notion and Countdown api, 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 Countdown api.