How do I call PodClaw from a Dify workflow?

Add an HTTP Request node to your Dify workflow. Set the method to POST, the URL to https://podclaw.io/api/shows/{show_id}/episodes, add an Authorization header with your Bearer token, and set the body to a JSON object with title, audio_url, and status fields.

Can Dify workflows publish podcast episodes from LLM output?

Yes. Use an LLM node to generate the episode title and description, then connect its output variables to the body of an HTTP Request node that calls PodClaw. The workflow runs end-to-end: LLM writes the content, HTTP node publishes it.

Does PodClaw work with Dify's chatflow and workflow modes?

Yes. PodClaw works in both Dify workflow mode (automated pipelines) and chatflow mode (conversational agents). In chatflow mode, a user message triggers the workflow; in workflow mode, you can set a scheduled trigger or webhook to run it automatically.

How to Automate Podcast Publishing with Dify + PodClaw

How It Works

Dify's HTTP Request node lets you call any REST API from within a workflow. The integration with PodClaw takes four steps:

Step 1

Get API key

Create a free PodClaw account and copy your API key from the dashboard.

Step 2

Create a show

POST to /api/shows once to set up your podcast. Save the returned show_id.

Step 3

Add HTTP node

Drop an HTTP Request node into your Dify workflow and configure it with the settings below.

Step 4

Connect & run

Wire your LLM output variables into the node body. Run the workflow — episode goes live.

HTTP Request Node Configuration

In your Dify workflow editor, add an HTTP Request node and configure it as follows to publish an episode:

config — Dify HTTP Request Node

Method:  POST
URL:     https://podclaw.io/api/shows/{{show_id}}/episodes

Headers:
  Authorization: Bearer pc_your_api_key_here
  Content-Type:  application/json

Body (JSON):
{
  "title":       "{{llm_output.title}}",
  "description": "{{llm_output.description}}",
  "audio_url":   "{{audio_url}}",
  "status":      "published"
}

Replace pc_your_api_key_here with your actual key and {{show_id}} with the ID from your PodClaw show. The double-brace variables reference Dify's upstream node outputs.

Full Workflow Example

A complete AI podcast workflow in Dify looks like this:

Start node — accepts a topic or transcript as the workflow input
LLM node — generates an episode title, description, and script from the input
HTTP Request node (TTS) — sends the script to ElevenLabs or OpenAI TTS, gets back an audio URL
HTTP Request node (PodClaw) — publishes the episode with the audio URL and LLM-generated metadata
Answer node — returns the episode URL to the user or webhook caller

Extracting the Episode URL from the Response

The PodClaw API returns JSON. Use Dify's variable extraction to pull body.url from the HTTP node response and pass it to the next node or return it as the final answer:

json — PodClaw API response

{
  "id": "ep_abc123",
  "url": "https://podclaw.io/episodes/ep_abc123",
  "title": "Weekly AI Digest — Episode 14",
  "status": "published",
  "rss_updated": true
}

Tip: Store your PodClaw API key as a Dify Environment Variable (Settings → Environment Variables) so it doesn't appear in plain text in your workflow nodes. Reference it as {{env.PODCLAW_API_KEY}} in the Authorization header.

What PodClaw handles automatically

Once your Dify workflow triggers the publish call, PodClaw takes it from there:

RSS feed updated immediately with the new episode GUID — Apple Podcasts and Spotify pick it up within hours
Permanent shareable episode page created at the returned URL
Download analytics tracked from first play, available via the analytics API
Optional webhook fires when Apple or Spotify confirms indexing

Dify Podcast Hosting API: Automate Episode Publishing with HTTP Request Nodes