FlowOS Automation HubPlain-English product documentation

Workflow builder, reviewer, and AI administrator

Use AI for proposals while people retain control

FlowOS AI assists with drafts, explanations, mappings, summaries, simulations, risk signals, and diagnostics. Its output is a proposal. It does not replace validation, publishing authority, or approval for guarded actions.

Outcome
You will review an AI suggestion without allowing it to publish or write autonomously.
For
Workflow builder, reviewer, and AI administrator
Time
20 minutes

Before you start

  • AI provider configured or fake provider enabled for local testing.
  • AI permissions and monthly limits reviewed.
  • An inactive workflow draft.
Use AI for proposals while people retain control diagram
Use AI for proposals while people retain control — a text description is included inside the diagram and in the surrounding section.

#Choose a bounded AI task

Ask AI to explain a failure, suggest a draft branch, summarize an audit record, or propose field mappings. Provide only the minimum redacted context. Treat confidence and risk indicators as signals for review, not guarantees.

#Review and apply a proposal

  1. Confirm the intended workflow and inactive version.
  2. Read the proposed trigger, fields, rules, and actions.
  3. Remove unnecessary or sensitive context.
  4. Edit incorrect assumptions.
  5. Approve or reject the proposal.
  6. Validate and publish separately using the normal release process.

#Use the approval inbox for guarded actions

A guarded tool call pauses before execution. The reviewer checks the target, payload, risk, and business reason, then approves or rejects. Approval and execution are distinct events so the audit trail can show who decided and what eventually happened.

AI suggestions apply to inactive drafts and require review. Capture details
A named reviewer controls guarded work. Capture details

#Common mistakes

  • Sharing secrets or unnecessary customer data with the provider.
  • Treating a high confidence score as approval.
  • Combining proposal approval and production publishing into one unchecked action.

#Verify the result

  • The proposal targets an inactive draft.
  • Shared context is minimal and redacted.
  • A human owns the final decision.
  • Execution evidence is reviewed after approval.
Enlarged documentation screenshot