AD SPACE AVAILABLE · BRAND PARTNERS WELCOME

Configuring Auphonic Presets and Cloud Watch Folders for Automated Podcast Post-Processing and Hosting Distribution

365Finds Editorial
Indexed 11,430 Wiki articles

Put 365 Wiki to work with your AI

Copy the prompt below, paste it into the AI you already use, then ask your question.

Download full Skill

Try it with the prompt first. If you use 365 Wiki often, install the full 365Wiki Skill so you do not have to paste it again. No regular AI? Gemini or Microsoft Copilot on the web will work.

365Wiki Skill

For podcast producers managing weekly shows or multi-program networks, manual post-production is a repetitive bottleneck. Leveling voice tracks, hitting broadcast loudness standards, scrubbing background noise, rendering chapter marks, and manually uploading finished audio files to podcast hosting dashboards consume hours every week.

Auphonic eliminates this manual overhead through the combination of Production Presets, External Services, and Watch Folders. Once configured, a producer only needs to export an edited mixdown from their Digital Audio Workstation (DAW) into a designated cloud folder (such as Dropbox, Amazon S3, or SFTP). Auphonic detects the file, applies mastering algorithms, injects metadata and intro/outro audio, transcribes the episode, and pushes the finished release directly to hosting platforms like Libsyn, Podbean, Captivate, or Spreaker.

Here is the step-by-step engineering guide to configuring an end-to-end automated podcast pipeline in Auphonic.


Architecture of the Zero-Touch Pipeline

The automated Auphonic pipeline operates across three interconnected layers:

[ Local DAW Export ] 
         │
         ▼
[ Ingestion Layer: Cloud Watch Folder ] 
  (Dropbox, OneDrive, Amazon S3, SFTP)
         │  (Push Notification or 5-min Polling Check)
         ▼
[ Processing Layer: Auphonic Production Preset ]
  - Audio Restoration: Dynamic Denoiser, Voice AutoEQ / Studio Voice
  - Dynamics & Loudness: Adaptive Leveler, -16 LUFS (Stereo) / -19 LUFS (Mono)
  - Content Assembly: Intro / Outro Ducking (-18 dB), Variable Metadata Tagging
  - AI Enrichment: Whisper ASR, Shownotes & Chapters Generation
         │
         ▼
[ Distribution Layer: Outgoing External Services ]
  - Podcast Hosts: Libsyn (Quickcast / Dropbox), Podbean, Captivate, Spreaker, Acast
  - Media & Social: YouTube (Video / Audiogram), Cloud Storage Archiving
  - Optional Safety Gate: "Review before Publishing" or "Draft" Mode

Step 1: Connect Ingestion Storage and Hosting Platforms

Auphonic separates connections into Incoming Services (where raw audio is pulled from) and Outgoing Services (where finished productions are sent). Navigate to the External Services menu (/engine/services/) to connect your services before building presets.

1. Connecting Incoming Storage Services

Storage ServiceIngestion Trigger MechanismDirectory Rules & Setup Requirements
DropboxInstant (Push Notification via Webhook)Restricted to /Apps/auphonic/. Raw files dropped here process immediately upon upload completion.
OneDriveInstant (Push Notification)Personal accounts restricted to /Apps/Auphonic App/. Business accounts require full read/write permissions.
Amazon S3Periodic Polling (every 5 minutes + 2-minute byte stability check)Requires S3 Bucket Name, AWS Access Key, AWS Secret Key, and an optional S3 Key Prefix (e.g., incoming-raw/).
Generic S3 / Google Cloud StoragePeriodic Polling (5 minutes + 2-minute check)Custom S3 API endpoint (e.g., storage.googleapis.com), bucket name, and interoperability keys.
SFTP / FTPSPeriodic Polling (5 minutes + 2-minute check)Hostname, port (default 22 for SFTP), directory path, and credentials or Auphonic's public SSH key.

Note on Google Drive: While Google Drive is supported for manual file selection via the Google Picker in the web production form, native Watch Folders require direct webhook or file-system polling. For automated cloud watch folders, Dropbox, OneDrive, Amazon S3, and SFTP provide reliable automation.

2. Connecting Outgoing Podcast Hosting Platforms

Connect your target podcast distribution platform under the Podcasting / Audio / Video Services section:


Step 2: Configure the Master Production Preset

The Preset (/engine/preset/) holds the core processing logic. Every recording processed through your watch folder adopts these settings.

1. Audio Algorithms: Mastering and Normalization

2. Audio Branding: Reusable Intro and Outro Stitching

Instead of manually aligning music beds in your DAW, presets can automatically append and prepend audio assets:

3. Metadata Automation and Variable Placeholders

Leave episode-specific fields blank if your DAW exports ID3 metadata tags directly into the input audio file; Auphonic preserves and maps them automatically.

To standardize show-level metadata across episodes, use Auphonic's dynamic template variables:

4. Speech Recognition and Auto-Shownotes

5. Output Encoders and Publishing Targets


Step 3: Configure and Arm the Cloud Watch Folder

With your External Services authenticated and your Production Preset assembled, create the ingestion trigger in the Watch Folders dashboard (/watchfolder/list/).

[ Watch Folder Configuration ]
├── Display Name: Weekly Show Ingestion (Dropbox)
├── Service Account: Dropbox (/Apps/auphonic/)
├── Preset: Master Podcast Preset v2
├── File Name Filter: *.wav
└── Status: Active
  1. Display Name: Give the folder a recognizable title (e.g., Weekly Podcast - Master Ingestion).
  2. Service Account: Choose your connected cloud storage (e.g., Dropbox, OneDrive, Amazon S3).
  3. Preset: Select the Production Preset configured in Step 2.
  4. File Name Filter: Enter a Unix wildcard expression to prevent unintended files from triggering runs:
    • *.wav: Matches only uncompressed WAV exports.
    • ep_*.wav: Matches only files prefixed with ep_.
    • *.[wm][ap]3: Matches both .wav and .mp3 files.
    • Do not leave this blank if your storage directory contains DAW project backups, .DS_Store files, or temporary cache files.
  5. Activate: Save and ensure the watch folder status indicates Active.

Operational Workflow: From DAW Export to Live Distribution

Once the system is armed, the production workflow is streamlined into a single action:

  1. Export from DAW: Edit your podcast episode in your DAW (Reaper, Pro Tools, Audition, Logic). Export your master singletrack mixdown as EP42_Interview_Master.wav.
  2. Drop to Cloud Storage: Move EP42_Interview_Master.wav into your watched cloud folder (e.g., your local Dropbox folder synced to /Apps/auphonic/).
  3. Automatic Ingestion:
    • Dropbox / OneDrive: A webhook push notification alerts Auphonic immediately once your cloud client finishes uploading.
    • Amazon S3 / SFTP: Auphonic’s server detects the new file during its next 5-minute polling cycle, verifies file size stability over a 2-minute buffer, and initiates the run.
  4. Batch Processing & AI Generation: Auphonic normalizes loudness to -16 LUFS, runs dynamic denoising, layers intro/outro music beds, runs Whisper transcription, and calculates chapter markers.
  5. Direct Distribution: The mastered MP3 and episode transcript push to your host (e.g., Libsyn or Podbean). If you left "Review before Publishing" turned off and selected immediate publishing, the episode enters your RSS feed without touching a browser.

Critical Nuances, Limitations, and Best Practices

To avoid common pitfalls in automated workflows, keep these technical limitations in mind:

1. Singletrack vs. Multitrack Restriction

Watch Folders operate exclusively on singletrack productions. They cannot automatically group separate multi-mic recordings (e.g., mic1.wav, mic2.wav) into a synchronized multitrack session. If you need multitrack cross-gating and individual track leveling, bounce your multi-mic recording to a preliminary singletrack master in your DAW before dropping it into the watch folder, or trigger multitrack jobs via the Auphonic REST API or an n8n community node.

2. Polling Latency on S3 and SFTP

Producers using Amazon S3, Google Cloud Storage, or SFTP should account for a 5 to 7 minute ingestion delay. Because these protocols lack native push notifications to Auphonic, the system polls every 5 minutes and waits an additional 2 minutes to confirm that large multi-gigabyte uploads are not incomplete. If you need an emergency instant run, navigate to /watchfolder/list/ and click the Check for New Files button.

3. Production Rate Safety Limits

Auphonic enforces a default maximum productions per hour ceiling on watch folders. This safety threshold protects your account balance in case an automated script or misconfigured sync tool dumps dozens of unintended files into the directory. If this limit is breached, Auphonic pauses the queue and sends an alert email allowing you to approve or cancel pending productions.

4. Inactivity Auto-Pausing

Auphonic periodically pauses watch folders that have seen zero activity over several consecutive months. If your show takes a seasonal hiatus, log into the dashboard to verify that your watch folder is set to Active prior to uploading your season premiere.

5. Managing Staging with "Draft Status"

If your editorial process requires final human review of episode summaries, sponsor copy, or artwork before public syndication:


References