Automated Clip Task Queue
When a new episode is marked export-ready in Descript, WebRun reads the transcript and scene markers to identify the three to five most shareable moments, creates a clip task in the Notion clip queue for each segment with the timestamp, a one-line description, and the platform it suits best, and posts a Slack summary so the team can start cutting immediately.
How do I automatically create clip tasks from new podcast episodes?
When a Descript episode is export-ready, WebRun reads the transcript and scene markers to identify the three to five most shareable moments, creates a Notion clip task for each with the timestamp, a description, and a suggested platform, and posts a Slack summary so the team can start cutting right away without any briefing.
- Every episode generates a ready-to-action Notion clip queue without a briefing call
- Editors see the best clip moments the moment an episode is export-ready
- No promising shareable segment is missed due to manual review taking too long
Built for podcast producers · podcast editors · content marketers · social media teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
web.descript.comin a real browser with your saved login - no setup, no API keys. -
1
Descript - identify shareable segments from transcript
WebRun opens Descript to identify shareable segments from transcript. - Open the completed episode project in Descript
- Read the transcript and scene markers to identify the three to five most engaging or quotable moments
- Note the timestamp range, the topic, and whether the moment suits short-form video, audiogram, or a quote card
Done when Three to five clip candidates are identified with timestamps and context.
-
2
Notion - create a clip task per segment
WebRun opens Notion to create a clip task per segment. - Open the podcast clip queue database in Notion
- Create a new task page for each clip candidate with the episode title, timestamp range, a one-line description of the moment, and the suggested platform
- Set each task status to To Do so the editor can pick them up immediately
Done when A Notion clip task exists for every identified segment, ready for the editor to start.
-
3
Slack - post clip queue summary to the team
WebRun opens Slack to post clip queue summary to the team. - Post a Slack message to the podcast channel summarizing the new clip tasks: episode title, number of tasks created, and a link to the Notion clip queue
- List the top clip candidate with its timestamp and a one-line description so the team sees the best moment immediately
Done when The team has a Slack notification with the clip queue summary and a Notion link to get started.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it export or post clips automatically?
No. WebRun identifies segments and creates tasks in Notion, but it never exports video files or posts clips to social media. The editor picks up each task, cuts the clip, and posts it on their own schedule.
How does it pick which moments to clip?
It reads the Descript transcript and scene markers, looking for strong quotes, topic pivots, and moments the editor flagged. You can add a prompt in the workflow settings to focus on specific themes or formats.
What if I want more or fewer clips per episode?
You can set the number of clip tasks to create in the workflow settings. The default is three to five, but you can lower it for shorter episodes or raise it for longer ones with more shareable content.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.