What Flow needs
- A description of the analysis, report, or file you need
- The business data Flow already has access to
- Nothing else — no template, no spec required
If it can be figured out, Flow figures it out
When There’s No Button For It, Flow Writes the Code
When code execution is enabled for an account, Flow can use it to work through an analysis or file request that has no ready-made view. The exact capability, accessible data, and security boundaries need to be confirmed before it is used with sensitive business information.
Who this is for
Owners who need an answer, a report, or an export that no software vendor anticipated.
The operating problem
Every pre-built dashboard eventually hits a question it wasn’t designed to answer. Normally that means exporting to a spreadsheet and doing it yourself.
A workflow from instruction to outcome
One conversation keeps the context and the work together.
- 01
Confirm that code execution is available and appropriate for the data involved.
- 02
Ask for an analysis, report, or export that has no ready-made view.
- 03
When enabled, Flow can use the data made available to that capability to prepare the analysis or file.
- 04
Review the methodology, inputs, and output before using it for a business decision.
- 05
Keep accounting, legal, compliance, and other specialist review outside the generated result.
Illustrative example — fictional prompt, response, names, and metrics; not customer results.
From context to controlled action
See the information before deciding what moves next.
Flow keeps the conversation close to the records and work it can use. The owner remains the decision point where the workflow requires approval.
What Flow creates
- A requested Excel, PDF, CSV, chart, or analysis when the capability supports it
- Cross-referencing across the business data made available for the request
- A result the owner can inspect before deciding how to use it
Where you approve
- Confirm which data sources the capability can access
- Review generated files and calculations before acting on them
- Keep credentials and sensitive data out until access, isolation, retention, and logging are verified
What to expect
Code-execution availability and its security boundaries must be confirmed for your account before relying on this workflow. Generated analysis can be wrong and is not a replacement for specialized accounting, legal, security, or compliance review.
Frequently asked questions
Clear answers before you bring Flow into the work.
When code execution is enabled, it can help prepare custom analysis and files from the data made available to the workflow.
That is an intended use of the code-execution workflow when enabled. Confirm current file formats and data access for your account.
Do not assume a security boundary from this page. Confirm access controls, isolation, logging, retention, credential handling, and review requirements before using sensitive data.
Start with the core
Bring your business context into one conversation.
The workspace is free for one person and one organization. Hire an employee only when you want more capacity.