Semantic Workflows

Semantic workflows let you define multi-step workflows at a high level. The system handles type bridging, data enrichment, validation, and execution automatically.

How It Works

Describe your goal in natural language. The system discovers relevant tools, identifies type mismatches, finds adapters, generates plans, validates them, and executes with monitoring.

Type Bridging

When tools have incompatible schemas, the system automatically inserts adapters. For example, converting a CRM lead to a billing customer requires field mapping and type conversion—the system handles this automatically.

Hole Filling

When data is missing required fields, the system enriches it automatically. It can look up missing information from external APIs, infer values from related fields, or prompt you for input when it can’t fill gaps automatically.

Formal Verification

Every plan is verified before execution. The system checks for cycles, validates type compatibility, ensures policy compliance, and verifies all tools are available. Plans include Cognitive Trust Certificates (CTCs) proving correctness.

Skills

Save verified workflows as reusable building blocks. Skills execute faster and cheaper than rebuilding workflows each time. Share skills across agents and teams.

Building Workflows

Using flow.into

Define workflows directly using the flow.into tool:

{
  "goal": "Create invoice from Salesforce lead",
  "lead_email": "user@example.com"
}

The system generates a plan, validates it, and executes it automatically.

Using discovery.plan

Generate plans automatically from natural language goals:

{
  "goal": "Create invoices for all qualified leads",
  "policy": {"max_cost": 100}
}

The discovery engine finds tools, plans the workflow, and returns a verified plan you can execute.

Interactive Playground

Use the Playground to explore workflows interactively. Type your goal, review discovered plans, choose based on cost and safety, then execute and save as a skill.

Key Features

Automatic Adapter Insertion

When types don’t match, the system finds and inserts adapters automatically. You don’t write transformation code.

Data Enrichment

Missing fields are filled automatically through lookups, inference, or user prompts. The system handles enrichment strategies transparently.

Multi-Objective Optimization

Plans are optimized across cost, latency, and risk. The system presents multiple options on the Pareto frontier—you choose based on your priorities.

Self-Healing

When plans fail, the system attempts automatic recovery. It can insert missing adapters, enrich missing data, retry with backoff, or request approvals as needed.

Use Cases

Lead-to-Revenue Workflows

Convert leads to invoices automatically. The system handles type conversions, data enrichment, multi-system coordination, and error handling.

Data Sync Across Systems

Keep customer data synchronized between Salesforce, HubSpot, and internal databases. The system handles field mapping, conflict resolution, and partial failures.

Compliance Workflows

Generate reports that aggregate data from multiple systems, redact PII automatically, require approvals, and maintain audit trails.

Hybrid Cloud and On-Premise

Create workflows that span cloud integrations and on-premise systems via Private Connectors. The system routes requests transparently.

Monitoring

View all workflow executions in the Runs tab. See plan structure, inputs, outputs, credits consumed, latency per step, errors, CTC references, and approval events.

Every execution generates a receipt showing estimated vs actual credits, breakdown by step, duration, and CTC reference.

Best Practices

Start with discovery instead of hardcoding tool names. This makes workflows adapt if you switch integrations.

Use skills for repeated workflows. First execution builds and validates the workflow. Subsequent executions use the skill, which is faster and cheaper.

Enable approval gates for destructive operations. Configure approval channels and auto-approval rules in policy settings.

Monitor credit consumption. Set budgets and track usage to prevent runaway costs.

Version your skills. When updating a skill, create a new version instead of overwriting. This enables rollback and A/B testing.

Troubleshooting

If no plan is found, check that required integrations are enabled and semantic types are annotated correctly. You may need to add a custom adapter.

If type mismatch occurs, verify tool annotations are correct. You may need an intermediate adapter or can use the generic type converter.

If plan validation fails, check the error message for specific violations. Fix policy issues or simplify the plan.

If approval is required but no channel is configured, set up an approval channel in policy settings.

If credits are insufficient, add credits, choose a cheaper plan, or optimize the workflow to remove unnecessary steps.