Add audience context to a podcast-related project
Make aggregated audience information easier to consult when a project is considering a known show.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
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.
Why this helps
Partnership or audience research can stall when useful show context requires another round of manual lookup.
- Retrieve aggregated context for a specific known show.
- Keep audience research connected to a project decision.
- Avoid treating audience data as individual listener information.
Setup
Build it in a few focused steps.
- 1Connect Linear and Listennotes to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to retrieve audience information when an updated project includes a known podcast ID.
- 3Write one plain-language instruction asking for aggregated audience context and how it relates to the project update.
- 4Select the Linear Project Properties Updated trigger, choose a channel for reports, and test with a project containing a real podcast ID.
Questions about this workflow
Does this return individual listener data?
No. The action is described as returning aggregated audience information, not individual listener data.
What does the project need?
A known podcast identifier is required to retrieve audience information for that specific show.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Listennotes. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
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.
Issue Created Trigger
Triggered when a new issue is created.
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.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
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.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
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.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
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.
Linear 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.