Book a demo

Tell us about your use case. We will walk through composing a workflow, deploying to AWS Bedrock AgentCore, and invoking it from your product.

Floprints Composer

The conversational agent that turns natural language into validated WorkflowPlans. Self-correcting schema validation and immutable transcripts.

Overview

The Floprints Composer is a Bedrock-powered conversational agent that designs workflows. Each turn it calls exactly one of two tools:

  • ask_clarifying_question — when it genuinely needs more information
  • propose_plan — to produce or update the plan, with a 1–2 sentence summary of what changed

Self-correcting validation

Every proposed plan is validated against the Zod WorkflowPlan schema. On failure:

  1. Validation errors are fed back to the model
  2. The composer re-proposes, up to a retry budget
  3. Model iteration and timeout numbers are clamped into the allowed envelope rather than rejected outright

This makes composer output reliable enough to deploy without manual JSON editing.

What goes into a plan

A WorkflowPlan includes:

  • workflow — name and description
  • agents (1–10) — each with id, harnessName, systemPrompt, model, tools, maxIterations, timeoutSeconds, optional humanInLoop
  • execution — either sequential (linear pipeline) or orchestrator (coordinator with inline tools)

Transcript immutability

The full composer conversation — including every intermediate plan — is snapshotted into the saved workflow version as an immutable transcript. You always know exactly what the model proposed and what the operator accepted.

Editing after compose

You can refine a plan two ways:

  1. Continue the conversation — ask the composer to add agents, change execution mode, or adjust prompts
  2. Direct field edits — edit plan fields in the console before deploy

Provider lock-in

The cloud provider is chosen during composition and locked once a version exists. All deploy and execute operations happen in that provider’s scope.