> ## Documentation Index
> Fetch the complete documentation index at: https://parabola.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Can I paste a requirements doc or workflow brief to build my flow automatically?

> If you've already written up your process step by step, you can hand that directly to Prowork on the flow canvas — here's where to paste it and what to expect.

Yes — if you've already documented your process (a numbered list of steps, a workflow brief, requirements from a stakeholder), you can paste that directly into **Prowork**, Parabola's AI flow builder, and it will use it as the starting point for building your flow.

<Note>
  Support chat (the in-app chat icon) is for help using Parabola — it can't build a flow for you. To have your requirements turned into a working flow, paste them into the Prowork chat on a flow's canvas instead, as described below.
</Note>

<Steps>
  <Step title="Start a new flow">
    Open a new flow in Parabola. Prowork's chat sidebar opens automatically.
  </Step>

  <Step title="Paste your requirements as-is">
    Drop in your workflow brief, requirements doc, or numbered step list directly into the chat. You don't need to reformat it or translate it into "Parabola steps" first — Prowork reads plain-language process descriptions.
  </Step>

  <Step title="Answer Prowork's clarifying questions">
    Prowork will typically ask a few follow-up questions specific to your data before it starts building (for example, which field to join on, or what should happen for an edge case). Answer in plain language.
  </Step>

  <Step title="Review the steps as they appear">
    Each step Prowork adds is visible and editable on the canvas — nothing is a black box. If a step doesn't match your brief, tell Prowork to change it or edit the step directly.
  </Step>
</Steps>

For tips on writing a brief that gets you a more accurate first pass, see [Prowork best practices](/docs/product/overview/best-practices). For the full building walkthrough, see [Build a flow with Prowork](/docs/product/overview/build-a-flow).

## Related

* [Build a flow with Prowork](/docs/product/overview/build-a-flow)
* [Prowork best practices](/docs/product/overview/best-practices)
* [How Prowork documents your flow](/docs/product/overview/documents-your-flow)