The quickest way to create a BPMN diagram in Just Flow It is to describe your process in plain text. Type a description of your workflow into the input box, click Generate, and the AI produces a complete BPMN 2.0 diagram — including tasks, gateways, events, pools, and lanes — ready to export or refine. The more detail you provide, the closer the result will be to exactly what you need.
Using the text input box
Type your process description directly into the text input field on the home screen or the editor. There is no required format or template — write naturally, as if you were explaining the process to a new team member. When you’re ready, click Generate to produce the diagram.
Even a single sentence like “A customer places an order and we ship it” will produce a valid BPMN diagram. You can always add more detail and regenerate to get a more precise result.
Tips for writing an effective description
A well-written description gives the AI enough context to place the right elements in the right places. Keep these guidelines in mind:
Name the roles involved. Use job titles or role names rather than “someone” or “they.” The AI maps named roles to pools and lanes automatically.
Call out every decision point. Phrases like “if the invoice is approved,” “when stock is available,” or “depending on the customer tier” tell the AI to insert gateways with the correct branches.
Describe exception and error paths. If something can go wrong — a payment failure, a rejected application, a missing document — mention it. These become error events or alternative sequence flows in the diagram.
List parallel activities. If two things happen at the same time, say so: “simultaneously, the warehouse team picks the items while the finance team prepares the invoice.” The AI will add a parallel gateway.
Mention start and end points. Be explicit about what triggers the process and what a successful completion looks like.
Longer descriptions generally produce more accurate diagrams. If your first result is missing a step or a decision, add those details to your prompt and click Regenerate.
Example prompts
Use these examples as a starting point. Notice how each one names roles, lists decisions, and describes outcomes.
Example 1 — Purchase approval workflow
A purchase request is submitted by an employee. The line manager reviews it
and either approves or rejects it. If rejected, the employee is notified and
the process ends. If approved and the request is over $5,000, it is escalated
to the finance director for a second approval. Once fully approved, the
procurement team raises a purchase order and sends it to the supplier.
The supplier confirms receipt and the process ends.
Example 2 — Customer onboarding
A new customer submits a sign-up form on the website. The sales rep reviews
the application and checks the customer's credit score. If the score is below
600, the sales rep sends a rejection email and the process ends. If the score
is 600 or above, the sales rep creates an account in the CRM, the finance team
sets up a billing profile, and the onboarding specialist sends a welcome email
with login credentials. Both the finance and onboarding tasks happen in parallel.
Example 3 — IT support ticket
A user submits a support ticket through the helpdesk portal. The system
automatically assigns the ticket to the first-line support team. The agent
reviews the ticket and either resolves it immediately or escalates it to
second-line support if the issue is not resolved within 2 hours. Second-line
support investigates and applies a fix. Once the fix is confirmed by the user,
the agent closes the ticket and sends a satisfaction survey.
Avoid overly vague descriptions such as “handle the order” or “process the request.” Generic language produces generic diagrams. Name every role and every outcome you care about.
