Cut Webinar Clips With an AI Agent, Livestorm and OpusClip

The short answer: if you run two webinars a month on Livestorm and the clips never get cut because nobody has two spare hours, give the finding to an agent and keep the choice with a person. An n8n workflow sends each recording to OpusClip, an agent ranks the clips by the audience questions they answer, and a person decides what posts. OpusClip Pro costs $29 a month on monthly billing for 300 credits (pricing page), at 1 credit per source minute (credits article); n8n Starter is $24 a month billed monthly, or free as the self-hosted Community Edition (n8n pricing), checked on 26 October 2026 for both. For example, two 55-minute recordings use 2 x 55 = 110 credits, and reading a shortlist of 10 clips of up to 90 seconds takes at most 2 x 10 x 1.5 = 30 minutes a month, against 110 minutes of watching to find the moments yourself.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

The useful part of a webinar is rarely the slides. It is the ten minutes where the speaker answers what the audience typed, because those are the questions your buyers ask. Livestorm leaves the question sidebar out of the recording (replay article), but its API returns every question with a flag for whether it was answered out loud (questions endpoint). That list is the agent's brief. The per-tool screens are in how to use OpusClip and how to use Livestorm.

Before you build:

1. The credit sum, against the API cap. OpusClip's API comes with Pro, in beta, capped at 900 credits of API video a month per workspace, with a 10-credit minimum per project (limitations). For example, four 55-minute webinars a month are 4 x 55 = 220 credits: inside Pro's 300 and the cap.
2. API access on the Livestorm workspace you already pay for. Livestorm opens its public API on request to support, and each token carries scopes: events read for recordings and questions, webhooks write for the trigger (token guide).
3. A brand template, and an n8n instance on HTTPS. Set the default template in OpusClip first, because an API project uses it when none is named (create project). Livestorm posts webhooks only to a valid HTTPS URL (webhooks).
4. A number from before. For your last three webinars, note the hours it took to get clips posted and the on-demand registrations that came from social links, which Livestorm records from UTM parameters on its registration page (source tracking).

From the last slide to a shortlist

1. Trigger: the session ends. Subscribe a webhook to session.ended and point it at an n8n Webhook node (Livestorm webhooks, Webhook node). A subscription covers every session in the workspace, internal demos included, so the next node is an If that keeps only the events you want clipped. Reply with a 2xx straight away: after five failed retries Livestorm switches the subscription off and tells you by email.
2. Fetch the recording and the questions. A Wait node set to a time interval spaces the first request from the session's end (Wait node). Then two HTTP Request nodes: GET /sessions/{id}/recordings with url_expires_in[seconds] at 3600, the shortest it accepts, since the MP4 link is temporary (recordings endpoint), and GET /sessions/{id}/questions. An empty recordings list means the file is not there yet; loop back to the Wait.
3. Hand the file to OpusClip. Livestorm is not among the platforms OpusClip imports from by link, and its URL expires, so upload the file: POST /api/upload-links, open a resumable session, PUT the bytes, then create the project with the returned upload ID as videoUrl (upload guide). In curationPref, set model to ClipAnything, clipDurations to [[0, 90]], a range that skips the welcome and the housekeeping, and a customPrompt such as "clips in which a speaker answers something an attendee typed". Under conclusionActions, add a WEBHOOK whose URL is {{$execution.resumeUrl}}, then a Wait node set to On Webhook Call (create project). The run sleeps until OpusClip calls back. OpusClip signs each call (webhook security), and because the next node reads the clips with your own key and ignores the payload, a forged call can only wake the run early.
4. The agent reads, ranks and files. GET /api/exportable-clips returns each clip's title, its transcript as text, durationMs and the timeRanges it was cut from (get clips). Both lists go into an AI Agent node, wired to whichever chat model you use (AI Agent node). Its instructions: match each clip to the audience question it answers, or to none; flag a clip that starts or stops mid-sentence; list every price, date, customer name and roadmap promise spoken in it; pick up to ten. n8n will not run an agent without a tool, so give it one with a narrow job: an HTTP Request tool for POST /api/collection-contents, which files a clip into a collection named after the webinar (collection contents). A Slack node sends the owner the shortlist, the question behind each clip and the flags (Slack node).
5. A person chooses. The owner opens the collection under My projects, Collections (collections article) and plays every clip to the end with the sound on. Three checks are theirs alone: a customer named on stage agreed to be quoted, a price said in the session is still the price, and a roadmap date is one the product team will stand behind. Clips that fail leave the collection. The ranking suggests; a person decides what goes out under the brand.
6. The output, and where it lands. The kept clips are scheduled from OpusClip's calendar, each linking to an on-demand event you create from the replay so registrations keep coming (replay article), with UTM tags on every link. If you schedule through Claude instead, OpusClip's connector returns each post as an approval link only you can confirm (Claude connector).

Doing it by hand, on free plans

For one webinar a month the manual version is enough, and it shows you what the agent should look for. Download the replay from the session page under Replay, Download (replay article). Import it into Descript's Free plan, 60 media minutes a month with 720p exports (Descript pricing), and read the transcript with the question list beside it. Highlight each answer, then run Copy highlights to paste those passages into a new composition, one per clip (highlights article).

OpusClip's Free plan will clip the same file: 60 credits a month, a watermark, no editing, and exports that lapse after 3 days (pricing page). Enough to compare its picks with yours, not to post under a brand.

The paid route adds the trigger, the matching against questions, clean exports and a shortlist that waits in a collection rather than in someone's memory. Livestorm also sells its own clipping add-on, AI Studio, in beta for Pro and Enterprise accounts on an annual contract priced by sales, with a trial that ends at 240 minutes of recordings or 30 days (AI Studio article). To stay inside one tool, run that trial on the same webinar before building anything.

The monthly bill, tool by tool

All prices in US dollars, checked on 26 October 2026. Each ended session is one n8n execution, discarded ones included, because a webhook trigger counts once per inbound request (executions) and a Wait pauses that execution rather than starting another.

One meter sits outside the table. Someone who registers through a clip and watches the on-demand version counts as an attendee and spends a Livestorm credit, €2.50 each on the smallest Pro pack (pricing). For example, 40 such viewers in a month use 40 x 2.50 = €100 of credits. A clip that works is paid for on the far side too, so size the pack for success.

Where the vendor's default and yours part

OpusClip sorts results by its own Virality Score, highest first, and for ClipAnything it partly scores how well a clip fits the prompt (Virality Score article). That is the vendor marking its own homework, and a tool billed per minute of source does well when every recording looks worth clipping. Your ranking is the question list, written by the people you want to sell to. Keep the score as a tiebreak.

Did the clips earn their keep?

Count on-demand registrations per webinar from clip links, read by utm_source in the event dashboard, plus the hours between the session's end and the last clip scheduled. The baseline is the three webinars you noted before building.

Then a holdout, because a strong topic flatters any method. With two webinars a month, clip only one of them for the next two months, alternating which, and compare on-demand registrations from social per webinar.

Watch the agent too, through the share of its shortlist the owner keeps. My rule of thumb: below half for two webinars running means the prompt and instructions need rewriting before the model takes the blame, because the clips are answering questions nobody asked.

If you would rather have the workflow built, run against that holdout and documented for whoever looks after it next, that is what the agentic marketing service is for.

FAQ

Can the agent post a clip on its own?

No. Its one tool calls a single endpoint, the one that adds a clip to a collection, so nothing it can reach publishes. Keep it that way if you swap in an MCP server: OpusClip's server at mcp.opus.pro commits posts the moment an agent calls the tool, while its Claude connector returns an approval link (Claude connector).

My webinars run on Zoom. Does this still work?

The clipping half does. OpusClip imports Zoom recordings by link, so step 3 becomes one request with the Zoom URL as videoUrl (create project). Paste the question list into the agent's input from wherever your Q&A is kept.

Can Submagic do the clipping instead?

From YouTube, yes. Its Magic Clips endpoint takes a youtubeUrl, a webhookUrl and clip lengths between 15 and 300 seconds, at one Magic Clips credit per project (Magic Clips API). If your recordings already go to YouTube, that call replaces step 3; the Submagic entry covers its plans.