--- title: "Bambuser Integration" description: "Bambuser powers live video shopping with hosted and recorded broadcasts. Agents list and update broadcasts, create clips, tag archives, fetch download links, sign player URLs, and pick up new broadcasts on a polling schedule." url: https://flowrunner.ai/integrations/bambuser date_modified: 2026-09-04T19:38:13-07:00 --- # Bambuser [Media & Video](https://flowrunner.ai/integrations/category/media-video) Bambuser powers live video shopping with hosted and recorded broadcasts. Agents list and update broadcasts, create clips, tag archives, fetch download links, sign player URLs, and pick up new broadcasts on a polling schedule. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 trigger · 16 actions · API key · available [Bambuser website](https://bambuser.com/) · [Platform Documentation](https://bambuser.com/docs) · Capability data verified 2026-08-28 1. A live shopping show finishes and the recording lands on the Bambuser account 2. Get Broadcast reads the title, the host, and the running length 3. Agent matches the show's run of show against the product list to place each product's moment 4. Add Tag marks each product moment with its start and end second inside the recording 5. Create Clip cuts each tagged moment out into its own broadcast 6. The merchandising channel gets the clip list with signed player links 7. A merchandiser picks which clips go live on product pages and whether the master recording is retired ## What This Integration Enables Bambuser is built for teams that treat a live broadcast as inventory rather than as an event. The show ends, but the recording still contains the moment a product was demonstrated, the moment a question was answered well, and the moment a discount was announced. FlowRunner agents work on that recording: listing and reading broadcasts, cutting timed sections into new broadcasts with Create Clip, tagging moments with a start and an end second, pulling download links for the finished files, and signing player URLs for embedding. The tagging surface is the part worth planning around. Because List Broadcasts filters on tags, tagging the second a product appears is what turns a growing archive into an index a [connectors](https://flowrunner.ai/concepts/connectors) driven workflow can query later. None of that requires a person to sit through the recording, which is exactly the kind of work FlowRunner exists to take off a team's plate while leaving the merchandising calls with the merchandisers. ### Without FlowRunner **Recordings go nowhere**: A show that took a week to produce is watched live and then sits in an archive nobody searches **Clipping is a person's afternoon**: Someone scrubs a ninety minute recording to find the four minutes about one product **The archive has no index**: Broadcasts are listed by date and title, so finding "the one where we demoed the winter jacket" means opening them ### With FlowRunner **Every show becomes a set of assets**: Product moments are cut into their own broadcasts as soon as the recording lands **Clipping happens on arrival**: The agent places the timestamps and cuts the clips, and a merchandiser reviews a list instead of a timeline **The archive is queryable**: Tagged moments turn the back catalog into something a workflow can filter on by product, campaign, or host ## Use Case Scenarios ### The show becomes product page assets A live shopping broadcast ends. On the next poll the agent reads the finished recording, matches the run of show against the product list held in [Airtable](https://flowrunner.ai/integrations/airtable), and calls Add Tag once per product with the seconds that product was on screen. Create Clip then cuts each tagged span into its own broadcast. Get Player URL signs a permanent embed link for each clip, and the agent writes those links back against the matching products in [Shopify](https://flowrunner.ai/integrations/shopify). The merchandiser sees a row per product with a clip attached instead of a link to a ninety minute video. ### An archive that answers questions Marketing wants every moment the spring collection was shown, across eleven broadcasts and four hosts. Because earlier runs tagged those moments, List Broadcasts with a tag filter returns them directly, and the agent assembles the list with Get Broadcast, pulls files with Get Download Link, and posts the result into [Slack](https://flowrunner.ai/integrations/slack) with the durations totaled. The same query drives a monthly digest into [Google Sheets](https://flowrunner.ai/integrations/google-sheets) so the team can see which products actually got airtime against which ones the plan said would. ### Retiring the source without losing the clips Storage cleanup is where an archive workflow becomes dangerous. The agent finds broadcasts older than the retention rule, checks that every clip cut from each one is readable, and assembles the evidence: the master's length, the clips derived from it, and whether any clip is still returning as unavailable. It then stops. Delete Broadcast is permanent, and a clip that is still processing is indistinguishable from a clip that failed, so the agent does not guess which one it is looking at. ## Human-in-Loop Highlight Bambuser answers a not found response for a freshly created clip until processing finishes, which is the vendor's own way of saying "wait". That is fine while a workflow is only waiting. It is not fine when the next step is Delete Broadcast on the master, because the agent cannot tell an unfinished clip from a broken one, and the master is the only source either could be cut from again. So the archive agent stops and posts to the media owner: "Broadcast 41f2 from March 3 is past retention. Four clips were cut from it. Three are readable. One has answered not found for 40 minutes, which means either still processing or failed. Delete the master, or hold it?" The owner answers. The cleanup runs at machine speed on everything else in the queue, and the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step exists only where a permanent delete meets an ambiguous signal. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 16 actions ### Broadcasts 6 - **List Broadcasts** Lists broadcasts on the account with cursor paging, filtered by author, creation date range, title text, or tags. The query behind archive reporting and every tag driven lookup. - **Get Broadcast** Retrieves one broadcast by id. Also the readiness check for a clip, since a clip that is still processing is not yet retrievable. - **Update Broadcast** Updates a broadcast's stored fields. Bambuser publishes no reference for this route, so the connector passes the body through rather than pretending to know its full contract. - **Delete Broadcast** Permanently removes a broadcast. The operation this page's human gate exists for. - **Create Clip** Cuts a section of an existing broadcast, given a start and an end in seconds, into a brand new broadcast. The end must be later than the start, and the connector checks that before spending a request. - **Get Download Link** Returns a link to the recorded file so a workflow can hand it to storage, an editor, or a captioning step. ### Tags 2 - **Add Tag** Attaches a tag to a broadcast, optionally with a start and end position so it marks a moment rather than the whole recording. This is what makes an archive searchable later. - **Remove Tag** Removes a tag from a broadcast. Called without a specific tag id it clears every tag on that broadcast, so cleanup workflows name the tag explicitly. ### Images 3 - **List Images** Lists images on the account with the same filter set as broadcasts. - **Get Image** Retrieves one image by id, including its metadata. - **Delete Image** Permanently removes an image. ### Applications 4 - **List Applications** Lists the applications configured on the account. Another route Bambuser has not published a reference for, shipped as read only inventory. - **Get Application** Retrieves one application by id. - **Create Application** Creates an application with a pass through body, since the vendor documents no schema for it. - **Delete Application** Permanently removes an application. ### Player 1 - **Get Player URL** Builds a signed playback link locally rather than calling the API, using the account's separate signing key pair. Left without a time to live it produces a permanent link suitable for an embed; given a number of seconds it produces one that expires. ## Triggers 1 triggers ### Event Triggers 1 - **On New Broadcast** Fires when a broadcast appears on the account, which covers a live show finishing as well as a clip created through the API. It can be narrowed to one author or one tag. Bambuser publishes no webhook routes, so this trigger polls, and its first pass records the existing library and emits nothing so a new flow does not fire once per historical recording. ## Frequently Asked Questions ### What can FlowRunner do with Bambuser? FlowRunner agents can run List Broadcasts, Get Broadcast, and Delete Broadcast in Bambuser, plus 13 more actions. ### Does connecting Bambuser to FlowRunner require OAuth? No. Bambuser connects to FlowRunner with an API key, no OAuth flow required. ### Can Bambuser trigger a FlowRunner workflow automatically? Yes. Bambuser supports 1 trigger that can start a FlowRunner workflow automatically. **Work at Bambuser?** This integration exposes Bambuser to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/bambuser. Site index: https://flowrunner.ai/llms.txt