Overview
A second example uses a tutorial that explains how to build a lead-scraping workflow in a no-code automation tool.
The video-to-action skill is triggered with the tutorial link. Gemini analyzes the video and creates a detailed breakdown. The breakdown includes the sequence of nodes, configuration choices, interface actions, approximate timestamps, and the expected final layout.
The resulting analysis is stored in a file. A new agent instance receives the instruction to use that file to build the same workflow.
The execution agent then:
- Opens a browser through Chrome DevTools MCP.
- Connects to the automation account.
- Reads the detailed instruction file.
- Creates the workflow structure.
- Generates and imports workflow data.
- Configures nodes.
- Maps fields.
- Selects interface elements.
- Enters a test search.
- Runs the workflow.
- Continues testing until the flow functions.
The value comes from combining two kinds of understanding. The agent needs a macro view of the complete workflow and a micro view of individual interface actions. The structured analysis provides both.
The procedure illustrates a general design pattern:
Video understanding produces a procedure. A persistent file stores the procedure. An action-capable agent uses tools to execute the procedure. Testing closes the loop.