AzuraCast icon

AzuraCast

Interact with AzuraCast Web API

Actions263

Station Podcast → Run Episode Art

AI-generated

Summary

Triggers the Run Episode Art endpoint to upload artwork for a podcast episode.

Inputs

  • path__postpodcastepisodeart__episode_id (required) — Identifies the episode for this action. Path parameter: {episode_id} Choose a name from the list, or specify an ID using an expression.
  • path__postpodcastepisodeart__podcast_id (required) — Identifies the podcast for this action. Path parameter: {podcast_id} Choose a name from the list, or specify an ID using an expression.
  • path__postpodcastepisodeart__station_id (required) — Identifies the station for this action. Path parameter: {station_id} Choose a name from the list, or specify an ID using an expression.
  • multipart_binary_property__postpodcastepisodeart — Name of the input data field that contains the upload file
  • multipart_file_field_name__postpodcastepisodeart — Multipart form-data field name for the uploaded file
  • sendAdditionalHeaders — Whether to include extra HTTP headers in this request
  • additionalHeaders — Provide additional HTTP headers as a JSON object, for example {"X-Trace-ID":"abc123"}
  • bodyModeOverride — Auto uses the built-in fields for this action. Override only when you need to send the request body manually.
  • manualJsonBody — Manual request body as JSON. Used only when Body Mode Override is set to JSON.
  • manualRawBody — Manual request body as plain text. Used only when Body Mode Override is set to Raw.
  • manualInputDataFieldName — Input binary property name to read when sending binary or multipart payloads manually
  • manualMultipartFileFieldName — Multipart file field name expected by the endpoint when using manual multipart mode
  • manualMultipartFields — Additional multipart form fields as JSON when using manual multipart mode
  • responseFormat — Choose how n8n should parse the response returned by AzuraCast
  • binaryOutputProperty — Binary output property name used when Response Format is set to Binary
  • returnFullResponse — Whether to return the full HTTP response, including headers and status code
  • wrapResponseData — Whether to keep the response body in a single output item. Disable to split array responses into multiple items.

Output shape

The HTTP response body, parsed according to Response Format (binary, JSON, or text); if Return Full Response is enabled the full response including headers is returned.

Response parsing depends on Response Format; wrapResponseData controls whether array results are split into multiple items.

Examples

Example 1: Upload episode art using default multipart fields

Select episode_id, podcast_id, station_id from list; leave file field as 'file' and data field as 'data'; set Response Format to Binary; returnFullResponse false; wrapResponseData true.

Example 2: Manually send JSON body with custom headers

Set bodyModeOverride to json, provide manualJsonBody; enable sendAdditionalHeaders true and add X-Trace-ID; keep default Response Format json.

Example 3: Use binary mode with custom field names

Set bodyModeOverride multipart, set manualBinaryBodyProperty to 'data', manualMultipartFileFieldName to 'artwork', set Response Format binary, wrapResponseData false.

Links

Discussion