For developers

Visual orchestration without a no-code ceiling.

Keep the customer journey inspectable on the canvas while APIs, code, secrets, webhooks, and scoped tokens handle the operational steps.

Start building freeExplore a live workflow

The problem

Operational logic should not make the customer journey opaque

A workflow needs more than messages, but handing its logic to an untracked collection of scripts makes it difficult to inspect, test, or hand over. Fluenta keeps the journey visual while making extension points explicit.

Outcomes

What remains inspectable

  • The HTTP or code step and its success and error branches.
  • The variables that enter and leave a code node.
  • The flow definition that is exported, imported, validated, and published.
  • The credential boundary between a saved secret and runtime execution.

Capabilities

The tools behind the work

Use a guarded HTTP boundary

HTTP nodes support GET, POST, PUT, PATCH, and DELETE; private and loopback addresses are blocked, redirect downgrades are rejected, responses are capped at 256 KB, and requests time out after 10 seconds.

Read the HTTP requests guide

Add JavaScript or Python logic

Code nodes run JavaScript or Python in a non-persistent, network-denied sandbox. They require explicit inputs and output mappings, with success and error branches.

Read the code nodes guide

Keep credentials outside the canvas

HTTP templates resolve named secrets only at execution time. Outbound webhook deliveries are HMAC-signed. The public REST API uses workspace-scoped API keys that may be pinned to one bot, carry a role, and can be revoked.

Read the REST API reference

Move a validated flow definition

Export and import validated Fluenta v2 JSON, then publish a versioned immutable snapshot after validation.

Read the publishing guide

How a flow looks

Extension points with explicit outcomes

The workflow still shows where a service call, code path, webhook delivery, or published definition belongs—and what happens when it fails.

  1. 01 · Build

    Keep the journey on canvas

    Use visual nodes for customer-facing state and make every operational extension a named step.

  2. 02 · Extend

    Call code or an HTTP endpoint

    Use declared inputs, output mappings, and explicit success and error edges.

  3. 03 · Exchange

    Move the definition as JSON

    Export or import a validated Fluenta v2 flow definition when the workflow needs a portable artifact.

  4. 04 · Publish

    Publish the reviewed version

    Validation precedes a versioned immutable publication snapshot.

Example workflow

Order-status lookup with a safe fallback

  1. 01Customer provides an order ID.
  2. 02HTTP node calls the approved order endpoint with an explicitly mapped response.
  3. 03Condition routes by fulfilment state.
  4. 04A code node normalizes a returned value only where the flow needs logic.
  5. 05Error path hands off to a person with the captured context.

Demonstration workflow using a first-party Fluenta template.

Product truth

Runtime limits and error model

HTTP nodes
Methods are GET, POST, PUT, PATCH, and DELETE. Requests time out after 10 seconds; response bodies are capped at 256 KB. Private and loopback addresses are blocked, HTTPS-to-HTTP redirect downgrades are rejected, and cross-origin credentials are stripped on redirects.
Code runtime
JavaScript and Python run in non-persistent, network-denied sandboxes. Default execution timeout is 5 seconds and can be configured up to 30 seconds. Source is limited to 20,000 characters; stdout is capped at 4,096 characters and a returned JSON result at 16,384 bytes.
Secrets
Named secrets can be referenced by HTTP templates. They are resolved only in the HTTP executor and do not enter the rendered template, trace, or logs.
Webhooks
Outbound webhook deliveries use a per-endpoint secret for HMAC signing.
API keys
Keys are scoped to a workspace and optionally one bot. They carry an owner, editor, agent, or viewer role, can be used by the public REST API according to their audience, and can be revoked.
Error model
HTTP and code nodes expose success and error outcomes. Publish validation reports invalid graphs before a workflow can be published; code execution returns a bounded error result for syntax, runtime, timeout, or invalid-result failures.
Documentation available today
Guides exist for the REST API, API keys, HTTP requests, code nodes, security, and publishing.
Planned documentation and tooling
Webhook reference, flow JSON schema reference, SDK or generated client, example repository, changelog, and status page are planned. They are not linked here because they are not available public pages today.

Metrics

Numbers visible to the operator

  • Workflow executions
  • HTTP success path
  • HTTP error path
  • Code success path
  • Code error path
  • Published version
  • Conversation handoff

Questions

Before you build

Can code make arbitrary network calls?

No. Code runs in a network-denied sandbox. Use a guarded HTTP node for a service call.

Can secrets leak into a workflow trace?

Named HTTP secrets are resolved only at execution time and are not included in rendered templates, traces, or logs.

Is there a public API reference or SDK?

The REST API reference is available at /docs/api. SDKs are not shipped.

Read the developer quickstart

Start with the visual journey, add a controlled operational boundary, and test the success and error paths before publishing.

Start building freeExplore a live workflow