Skip to main content

Buzzsprout Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Buzzsprout location.
buzzsprout_api.png

Buzzsprout

Create a Buzzsprout Destination​

  1. Click the + icon on the Nexset that will be sent to the Buzzsprout destination, and select the Send to Destination option from the menu.

  2. Select the Buzzsprout connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Buzzsprout account, and click Next; or, create a new Buzzsprout credential for use in this flow.

  3. In Nexla, Buzzsprout destinations can be created using pre-built endpoint templates, which expedite destination setup for common Buzzsprout endpoints. Each template is designed specifically for the corresponding Buzzsprout endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Buzzsprout destinations can also be configured manually, allowing you to send data to Buzzsprout endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Buzzsprout endpoints. Each template is designed specifically for the corresponding Buzzsprout endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Create Episode

    This endpoint creates a new episode for a Buzzsprout podcast. Use it to programmatically publish episodes — for example, when audio files and metadata arrive from an upstream production system. The template issues a POST request to https://www.buzzsprout.com/api/<podcast_id>/episodes.json with each Nexset record serialized as the JSON request body.

    • Enter the podcast identifier in the Podcast ID field. This identifies the podcast under which the new episode will be created.
    • Each Nexset record is sent as the JSON body of the POST call. Use the Nexla transform layer to shape upstream attributes into the field names expected by Buzzsprout, such as title, description, and audio_url.

    For the full set of supported episode attributes, see the Buzzsprout episodes API reference.

    Update Episode

    This endpoint partially updates an existing episode using HTTP PATCH. Only fields included in the request body are modified — fields omitted from the body are preserved. Use it when an upstream record carries a delta against an existing Buzzsprout episode (for example, updating only the description or publication date).

    • Enter the podcast identifier in the Podcast ID field. This identifies the podcast that contains the episode.
    • Enter the target episode identifier in the Episode ID field. The episode ID can be obtained from the List Episodes data source endpoint or from the Buzzsprout admin UI.
    • Send only the attributes you wish to change in the request body. Any attributes not included will retain their existing values.

    Because PATCH performs a partial update, this endpoint is the safer choice when you only want to overwrite specific fields rather than the entire episode.

    Replace Episode

    This endpoint replaces an existing episode in full using HTTP PUT. All episode fields must be supplied in the request body; any field omitted will be cleared. Use it when the upstream record represents the complete, authoritative state of the episode.

    • Enter the podcast identifier in the Podcast ID field. This identifies the podcast that contains the episode.
    • Enter the target episode identifier in the Episode ID field.
    • Send the full set of episode attributes in the request body. Any attributes omitted from the payload will be cleared on the Buzzsprout side.

    Prefer the Update Episode (PATCH) endpoint when you only need to change a subset of fields — PUT will overwrite the entire episode.

    Delete Episode

    This endpoint deletes an episode by ID using HTTP DELETE. Use it to remove episodes from a Buzzsprout podcast as part of a downstream cleanup or de-publishing workflow.

    • Enter the podcast identifier in the Podcast ID field. This identifies the podcast that contains the episode.
    • Enter the target episode identifier in the Episode ID field. Records flowing through this destination must supply the episode ID via the configured field mapping.

    Episode deletion is permanent and cannot be undone. Confirm that your upstream flow only emits delete requests for episodes that should actually be removed.

Configure Manually​

Buzzsprout destinations can be manually configured to send data to any valid Buzzsprout API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Buzzsprout API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Buzzsprout API from the Method pulldown menu. The Buzzsprout episodes API supports POST (create), PATCH (partial update), PUT (full replace), and DELETE.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Buzzsprout API from the Content Format pulldown menu. Buzzsprout requires JSON — select JSON so that Nexla serializes each record as a JSON object and sends it with Content-Type: application/json.

API Endpoint URL​

  1. Enter the URL of the Buzzsprout API endpoint to which you want to send the Nexset data in the URL field. All Buzzsprout API URLs end in .json. For update/upsert operations, include the ID of the episode to be updated at the end of the URL.

    • Example for create: https://www.buzzsprout.com/api/<podcast_id>/episodes.json
    • Example for update/replace/delete: https://www.buzzsprout.com/api/<podcast_id>/episodes/<episode_id>.json

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Buzzsprout recommends setting an explicit User-Agent header on API requests — default library user agents may be blocked.

    You do not need to include any headers already present in the credentials. The Authorization: Token token=... header and Content-Type: application/json are handled automatically by Nexla.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Buzzsprout destination, select the attributes from the Exclude Attributes pulldown menu. This is useful for stripping internal identifiers or staging fields that should not be persisted to Buzzsprout.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings.

    The Buzzsprout episodes API processes one episode per request, so the pre-built endpoint templates send records individually. Only enable batching when targeting a custom Buzzsprout endpoint that explicitly accepts an array of records.

Response Webhook​

Optional

Nexla can automatically send the response received from the Buzzsprout API after each call to a new Nexla webhook data source. This is particularly useful for capturing the Buzzsprout-assigned id of newly created episodes so it can be referenced by downstream flows.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Buzzsprout API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.

  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Buzzsprout API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Buzzsprout API using the current settings.

Save & Activate the Destination​

  • Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send data to the configured Buzzsprout endpoint, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to Buzzsprout until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.