Build A Premiere Pro Timeline From A Spreadsheet
A production table can already describe which media belongs in an edit, where each item should start, and which source range should be used. This workflow turns those prepared rows into Premiere placements without requiring an editor to locate and trim every clip manually.
This recipe uses Automation Agent for Adobe Premiere. The included tool runs directly from the panel's Library without Workflow AI. Use the agent workflow via MCP when your production needs a customized table format or placement policy.
Fastest Path: Run The Library Script
- Activate the intended Premiere Timeline before opening the tool.
- Run Place Prepared Items From Table from
Library > Examples > Editing. - Choose the CSV, TSV, or TAB file and one interpretation for its media column.
- Map the columns for media, sequence position, optional source In/Out, and optional target tracks.
- Choose whether to use the active sequence, duplicate it, or create a new empty sequence with matching settings.
- Review the interpreted rows in the preview before confirming any import or Timeline change.
The tool remembers the project and sequence that were active when it started. Both setup dialogs and the preview name that target. Changing panel focus or selecting a bin during setup does not silently retarget the workflow; cancel and restart if you need a different sequence.
Video Walkthrough
Choose How The Media Column Is Interpreted
One media-reference mode applies to the entire column. The tool does not guess or mix modes automatically.
| Media-reference interpretation | Example table value | What you choose |
|---|---|---|
| Full filesystem path | /Users/you/Footage/Coffee.mp4 | Project bin for reuse or import |
| Filename | Coffee.mp4 | Filesystem search folder and Project bin for reuse or import |
| Project Item name | Coffee close-up | Project search bin and optional subbins |
| Exact Project Item reference/path | MyProject.prproj\B-roll\Coffee.mp4 | No additional location; the item must already exist |
Filesystem modes first reuse an exact media-path match inside the selected Project bin and its subbins. If no match exists, the file is imported there after confirmation. Project Item modes use existing items and do not import files. Missing or ambiguous matches are skipped and reported.
Map Placement And Source Timing
Map columns explicitly from A–AZ. The media reference is required; the other columns can describe:
- sequence position;
- Source In and Source Out;
- one-based video and audio track numbers, where
1means V1 or A1.
Timing cells accept full timecodes, explicit seconds such as 12.5s, or whole
frames such as 300f. Bare numbers are rejected. An empty sequence position
appends the row at the current sequence end. Empty or unmapped Source In/Out
cells preserve the corresponding bound of the current Project Item range.
Seconds and frames count from the beginning of the sequence or source. Sequence frames use the sequence frame rate; source frames use the interpreted source rate, with sequence fallback where the source rate is unavailable. For source timecode, choose whether values are clip-relative or use the displayed source timecode. The preview shows how the rows were interpreted before placement.
Target And Review The Result
The target can be the bound active sequence, a duplicate of it, or a new empty sequence with matching settings. Duplicate is the default safe choice. The workflow verifies the target before preview and again after confirmation instead of switching to whichever Timeline happens to be active later.
Each source contributes all of its available video and audio. Global track choices apply when a row does not name its own tracks. Target tracks must already exist. Choose whether occupied target ranges should be skipped or overwritten, then inspect the preview and final Timeline. An optional TSV report records the normalized timing and result for each physical table row.
When A Custom Variant Makes Sense
The included tool deliberately handles a general prepared-placement table. It does not infer arbitrary production semantics or populate MOGRT text and graphics parameters.
Build a saved custom variant when a recurring table contains concepts such as
roles, episode sections, layout names, export targets, or production-specific
track rules. In the walkthrough, a Role column routes visuals, voice-over, and
music to different tracks. An agent helps author that behavior once; the saved
workflow can then run repeatedly without re-prompting or Workflow AI at runtime.
Review And Limitations
- One media-reference interpretation applies to the complete media column.
- Missing, ambiguous, invalid, or colliding rows can be skipped; inspect the preview, Timeline, and optional per-row report.
- Target video and audio tracks must already exist.
- Each placed source contributes the media components it actually contains; the standard workflow does not make a per-row editorial choice to exclude linked video or audio.
- A table describes placements, not editorial quality. The editor remains responsible for timing, pacing, track routing, media rights, and the final cut.
Recommended Execution Permissions
Allow the workflow to read the table and, for filesystem media modes, the chosen source folder. Project writes should cover the bound target sequence, any duplicate or new-sequence destination, the selected reuse/import bin, and the source items whose ranges will be placed. The included workflow does not use Workflow AI or network access.
Related Workflows
- Create Your Own Recipes: turn a production-specific table contract into a saved reusable tool.
- Script Library: browse the other ready-to-run editing workflows.