Podcast Data Extractor (Taddy API)

Interact with the Taddy Podcast API
Join our community

Actions4

Overview

The node "Podcast Data Extractor (Taddy API)" enables interaction with the Taddy Podcast API to search for podcasts and episodes, retrieve detailed podcast information, get episode transcripts, and check transcript credit availability. It is useful for workflows that require podcast discovery, metadata extraction, or transcript retrieval for further processing such as content analysis, archiving, or enrichment.

A common scenario is searching for podcasts related to a specific topic (e.g., technology), filtering results by genre or language, and then extracting episode transcripts for text analysis or summarization. Another use case is monitoring transcript credit usage or fetching well-known podcasts guaranteed to be available.

Properties

Name Meaning
Search Query The search term used to find podcasts or episodes (e.g., "technology"). Required for the "Search Podcasts" operation.
Max Results Maximum number of results to return. Applies client-side to limit the number of podcasts or episodes returned in search or episode listing operations.
Advanced Options A collection of optional filters and settings for the "Search Podcasts" operation:
- Content Types: Filter by types such as Comic Series, Creators, Podcast Episodes, Podcast Series.
- Genres: Filter by podcast genres like Arts, Business, Comedy, etc.
- Languages: Filter by languages such as English, Spanish, French, etc.
- Match Strategy: How strictly to match search terms (All Terms, Exact Phrase, Most Terms).
- Published After Date: Only include content published after this date.
- Require Transcript: Return only episodes with transcripts.
- Sort By: Sort results by Exactness or Popularity.
Podcast UUID Unique identifier of a podcast, required for operations "Get Podcast Episodes" and "Get Podcast by UUID".
Episode UUID Unique identifier of an episode, required for the "Get Episode Transcript" operation.

Output

The output JSON structure varies depending on the selected operation:

  • Search Podcasts: Returns search metadata including searchId, arrays of podcastSeries and podcastEpisodes objects, counts of total found and returned items, and echoes input parameters.

    • Each podcast series includes fields like uuid, name, description, imageUrl, rssUrl, itunesId, language, totalEpisodesCount, popularityRank, itunesInfo (with artwork URL), and genres.
    • Each podcast episode includes uuid, name, subtitle, description, audioUrl, imageUrl, datePublished, transcript, and nested podcast series info.

  • Get Known Podcasts: Returns an array of well-known podcast series with basic metadata.

  • Get Podcast by UUID: Returns detailed information about a single podcast series including author, website, genres, and iTunes info.

  • Get Podcast Episodes: Returns episodes of a specified podcast with details such as uuid, name, description, audioUrl, duration, episodeNumber, seasonNumber, transcriptUrls, imageUrl, and fileType.

  • Get Episode Transcript: Returns the transcript text of a specified episode as an array of segments and concatenated full text.

  • Check API Credits: Returns the remaining transcript credits available.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Taddy Podcast API.
  • Uses GraphQL queries sent via HTTP POST requests to the Taddy API endpoint.
  • Requires network access to https://api.taddy.org.
  • No additional external dependencies beyond standard n8n helpers and HTTP request capabilities.

Troubleshooting

  • Missing Required Parameters: Operations like "Search Podcasts", "Get Podcast Episodes", "Get Podcast by UUID", and "Get Episode Transcript" require specific parameters (search query, podcast UUID, episode UUID). Omitting these will cause errors.
  • API Errors: If the Taddy API returns errors (e.g., bad requests due to invalid queries or arguments), the node attempts a fallback request mode but may still fail. Error messages include HTTP status codes and response bodies for diagnosis.
  • Credit Limits: Running out of transcript credits will prevent transcript retrieval operations from succeeding.
  • Empty Results: Searches with very restrictive filters or rare terms may return no results.
  • Date Format: The "Published After Date" filter must be provided in a valid datetime format; otherwise, it may be ignored or cause errors.

To resolve issues:

  • Ensure all required inputs are provided.
  • Check API credentials and network connectivity.
  • Adjust search filters to broaden results if none are returned.
  • Monitor transcript credit usage with the "Check API Credits" operation.

Links and References

Discussion