Web and API channels

The generated chat UI

Add a UI trigger and Flux builds a chat interface for the workflow. No channel setup, no credential, no external account.

Pair it with a Chat response node. It is the right choice for:

• Testing — the fastest way to talk to an agent while building it.
• Internal tools — an assistant for your own team that does not need a public channel.
• Demos — showing an agent working without connecting anything.

The API trigger

Turns a workflow into an endpoint. Your system posts to it, the workflow runs, and a Webhook response node returns the result.

That makes Flux usable as a service inside a larger architecture: a classification endpoint, an enrichment step, a summarisation call — anything you would otherwise build and host yourself.

Reading the request

What the caller posted is available to the next node through the template language:

{{POUT body.message}}

Rather than typing paths, drag the key from the trigger's Response JSON Keys into the field — see Node Template Language.

The generic chat nodes

Several nodes come in a Cognify flavour and a Generic flavour. The generic ones exist so Flux can sit behind a system that is not Cognify:

Use these when you already have a chat product, a helpdesk or a custom application and you want Flux to supply only the intelligence.

Choosing between the three