create-workflow

To turn natural language into an executable workflow, describe your automation goal and the system maps it to the closest example, adapts the YAML to your case, and validates it against the DSL. You then approve the rendered specification before it is submitted for execution.

Template adaptation works by selecting the closest matching example from available assets and adapting its structure to your specific use case. The system validates the adapted YAML against the DSL specification to ensure compatibility before binding the data plane and submitting the workflow.

Yes, you can submit a Narrative workflow without manual YAML by stating your intent in natural language. The system drafts the workflow specification, validates the YAML against the DSL automatically, and only submits via the platform after you review and approve the rendered spec.

Workflow submission requires access to narrative-mcp and appropriate Read tools to resolve the data plane. If MCP servers or knowledge bases are unavailable, the system provides harness fallbacks and knowledge-base recommendations to proceed with the workflow generation.

If MCP servers are unavailable during workflow generation, the system automatically falls back to harness fallbacks and knowledge-base recommendations. This ensures the workflow specification process can continue, though full data plane resolution and submission may be limited until connectivity is restored.

The best way to validate a workflow DSL before submitting is to let the system walk the generated YAML against the spec automatically. After adapting the template to your intent, it validates compatibility and resolves the data plane, pausing for your explicit approval before calling the submission API.