Flow Capture is in the beta phase of development and may not be available on your enrollment. Functionality may change during active development. To enable Flow Capture, contact your platform administrator to modify application access in Control Panel.
Flow Capture is a tool for recording workflows in Foundry and converting them into structured, customizable documentation. It records mouse clicks, screenshots, optional audio with transcription, and contextual metadata while you navigate an application in a recording session. Captured assets can be edited, combined with prompts and model selection, and transformed into Markdown documentation that you can review, edit, and export.
To activate Flow Capture, enable it in the Application access section of Control Panel. You can configure a checkpoint to warn users before they perform sensitive actions, such as exporting generated content.
Flow Capture provides users with auto-capture and manual capture options. Screenshots are stored as individual snapshot assets and can be included in the final documentation in context, or as standalone images.
You can optionally include a microphone recording during a Flow Capture session. Audio files and their transcriptions are stored as assets and can be used to enrich documentation generation by providing additional context and instructions.
Crop and blur areas of captured images directly in Flow Capture to remove or redact sensitive areas before generation or export.
Add a prompt to provide additional context such as style guides, desired structure or additional instructions to shape tone, level of detail, and structure of the generated Markdown.
Flow Capture offers edit and view modes, allowing users to create and preview generated documentation. View mode displays generated documentation in presentation or preview form, while edit mode can be used to modify generated Markdown, create additional recordings, and adjust images or transcriptions before re-generating, saving, or exporting.
Choose a system prompt or template, and a model to influence how content is generated. General documentation and feature requests are examples of different content types. Models and templates affect style, length, and level of technical detail.
Export the final documentation in multiple formats, such as Notepad documents, Walkthroughs, PDFs, or a zipped bundle of images and Markdown.
It is the user’s responsibility to ensure that appropriate security checks related to markings and group-based access are applied to created Flow Capture resources to reflect the security checks of the captured content.