Review several known episodes in one research pass
When your research page is ready, retrieve details for its known episode references together to make comparison easier.
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
Post episodes by ids
The listennotestest episodes post endpoint allows users to retrieve metadata for multiple podcast episodes in a single request. this post endpoint accepts a list of episode ids and returns detailed information about each specified episode. it's particularly useful for bulk retrieval of episode data, reducing the number of api calls needed when working with multiple episodes. the endpoint should be used when you need to fetch information about specific, known episodes rather than searching or browsing. keep in mind that this endpoint is focused on retrieval only and does not support creating, updating, or deleting episode data.
Why this helps
Checking episode references one by one adds repetitive steps when a research page covers multiple shows or examples.
- Retrieve multiple known episode records together.
- Reduce repetitive lookups during comparisons.
- Keep episode details close to the research that prompted them.
Setup
Build it in a few focused steps.
- 1Connect Notion and Listennotes to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to fetch multiple episodes from updated research pages.
- 3Write one plain-language instruction asking Notis to use the known episode IDs recorded on the page and retrieve their metadata together.
- 4Choose the Notion Page Content Updated trigger for the research page or database.
- 5Test with a page containing two or more valid episode IDs.
Questions about this workflow
Does this search for episodes?
No. It retrieves metadata for episode IDs already known to you.
Why batch the IDs?
The action is intended to retrieve multiple specified episode records in one request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Listennotes. A trigger fires from one place; an action lands in another.
Notion triggers
Listennotes actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Post episodes by ids
The listennotestest episodes post endpoint allows users to retrieve metadata for multiple podcast episodes in a single request. this post endpoint accepts a list of episode ids and returns detailed information about each specified episode. it's particularly useful for bulk retrieval of episode data, reducing the number of api calls needed when working with multiple episodes. the endpoint should be used when you need to fetch information about specific, known episodes rather than searching or browsing. keep in mind that this endpoint is focused on retrieval only and does not support creating, updating, or deleting episode data.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create podcast via form data
The listennotestest podcasts post endpoint allows users to retrieve information about multiple podcasts using various identifiers such as listen notes ids, rss feed urls, apple podcasts ids, or spotify ids. it can optionally fetch the latest episodes for the specified podcasts. this endpoint is useful for bulk podcast data retrieval and for staying updated on recent episodes across multiple shows. it's particularly valuable for applications that need to sync or update podcast information from different platforms. the endpoint has a limit of returning up to 15 latest episodes per request, so for comprehensive episode history, multiple calls may be necessary.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Retrieve curated podcast by id
Retrieves detailed information about a specific curated podcast using its unique identifier. this endpoint allows users to access comprehensive data about a carefully selected podcast collection, including its contents, curator information, and associated metadata. it's particularly useful for applications that want to display or analyze curated podcast lists. the endpoint should be used when detailed information about a known curated podcast is required, but it won't provide a list of all available curated podcasts or allow modifications to the curated content.
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.
Fetch best podcasts list
The getbestpodcasts endpoint retrieves a curated list of the best podcasts from the listen notes platform. it allows users to access a collection of top-rated or popular podcasts, which can be filtered by genre, region, and content rating. this endpoint is useful for discovering high-quality podcast content, creating recommendation systems, or populating podcast directories. the results are paginated for efficient data retrieval and can be customized to exclude explicit content if required. while it provides a valuable overview of top podcasts, it may not include real-time updates or notifications about new episodes or changes in podcast rankings.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Retrieve genre list
The getgenres endpoint retrieves a comprehensive list of available genres within the listennotestest platform. this endpoint is designed to provide users with up-to-date information on content categories, which can be used for filtering, organizing, or subscribing to specific types of content. it's particularly useful for applications that need to populate genre-based dropdown menus, create content recommendation systems, or set up genre-specific notification preferences. the endpoint does not require any input parameters, making it simple to use for fetching the entire genre catalog. however, users should be aware that the response may contain a large amount of data, depending on the number of genres available in the system.
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.
Get playlists
Retrieves a list of playlists from the listen notes platform. this endpoint allows users to fetch all available playlists associated with their account or publicly accessible playlists. it should be used when you need to display a collection of playlists, such as in a user's library or for browsing purposes. the endpoint returns basic information about each playlist, which may include the playlist name, creator, number of episodes, and other relevant metadata. note that this endpoint likely returns a limited number of playlists per request, and pagination might be necessary for retrieving large collections. it does not provide detailed information about the episodes within each playlist; separate api calls would be required to fetch that level of detail.
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.
Listen to just listen endpoint
The 'just listen' endpoint is a basic listener or health check mechanism for the listennotestest app. it allows users to verify the availability and responsiveness of the service without requiring any input parameters. this endpoint should be used for monitoring the status of the listennotestest service or as a simple ping to ensure the api is operational. it's important to note that this endpoint likely doesn't provide any specific data about podcasts or user accounts. the response is expected to be minimal, possibly just confirming that the service is up and running. while useful for basic health checks, it should not be relied upon for any complex operations or data retrieval within the listennotestest ecosystem.
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 podcast audience by id
Retrieves audience information for a specific podcast identified by its unique id. this endpoint allows users to access demographic data, listening statistics, or other audience-related metrics for a particular podcast. it's useful for podcast creators, marketers, or analysts who want to understand their audience better or track the performance of their content. the tool returns aggregated data about the podcast's listeners, which may include but is not limited to age groups, geographic distribution, listening habits, or engagement metrics. it should be used when detailed audience insights for a specific podcast are needed. note that this endpoint does not provide real-time listener counts or individual listener data to protect user privacy.
Connect any two apps with Notis in the middle.
Notion and Listennotes, 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 Listennotes.