For developers

Use code where a WhatsApp flow needs an operational step

Extend the visual flow with guarded HTTP requests, JavaScript or Python code, signed outbound webhooks, workspace API tokens, and portable flow definitions.

Create a developer workspaceTry the live builder

Capabilities

The tools behind the work

Call services through guarded HTTP

HTTP request nodes block private and loopback IPs, reject HTTPS-to-HTTP redirect downgrades, strip cross-origin credentials on redirects, cap responses at 256 KB, and time out after 10 seconds.

Read the HTTP requests guide

Use JavaScript or Python where a flow needs logic

Code nodes run JavaScript or Python. Their schema requires unique input names and at least one output mapping; use distinct output variables.

Read the code nodes guide

Work with signed endpoints and scoped tokens

Outbound webhooks are HMAC-signed with a per-endpoint secret. Workspace API tokens are owner-managed, scoped to a workspace and optionally one bot, and can be revoked.

Read the security guide

Move and publish validated flow definitions

Export a Fluenta v2 flow as JSON, import validated JSON, and publish a validated versioned immutable flow snapshot. Restoring a prior publication is currently a support request.

Read the publishing guide

How a flow looks

A visual flow with explicit extension points

Keep the customer journey on the canvas while the steps that need a service call, code, or integration stay precise and inspectable.

  1. Build

    Add the operational step

    Use a visual flow, then add a guarded HTTP request or a JavaScript or Python code node where the workflow needs it.

  2. Connect

    Use the integration boundary

    Send an outbound webhook with HMAC signing, or use a workspace API token that is scoped to the workspace or bot.

  3. Exchange

    Move the definition as JSON

    Export a Fluenta v2 flow definition when you need a portable JSON artifact, then import through validation.

  4. Publish

    Create a versioned live definition

    Validate the flow before publishing so the live bot uses a versioned immutable publication snapshot. Restoring a previous publication currently requires a support request.

Start from the flow, then add the operational step

Build the journey visually, test it in the simulator, and publish the version you intend to run.

Create a developer workspaceTry the live builder