FlowFuse Expert

FlowFuse Expert is a collection of LLM based resources provided on FlowFuse Cloud.

Access to these features is also available to Enterprise Licensed Self Hosted and Dedicated Customers.

Self Hosted customers are directed to contact support to request the necessary authentication tokens to enable the features.

The FlowFuse Expert consists of two internal components that each need to be enabled with their own token. We are working to consolidate and simplify this configuration, but this is how it needs to be done for FlowFuse 2.28.

Process

  1. Customer emails support@flowfuse.com
  2. Support/Sales needs to verify that the customer has a current Enterprise License
  3. Once confirmed, they raise a Production Change Request providing details of the Customer and post a message to #dept-engineering with a link.
  4. Engineering needs to create two access tokens for the customer.
    1. Assistant: Open the Instance Settings for the flow-gen instance in the Internal Tools Application. Under the Security settings create a new HTTP Bearer Token using the customer name as the token name. The token will only be displayed once, so make a note of it - this is the Assistant Token.
    2. Expert: Open the Instance Settings for the flowfuse-expert-api instance in the Internal Tools Application. Under the Security settings create a new HTTP Bearer Token using the customer name as the token name. The token will only be displayed once, so make a note of it - this is the Expert Token.
  5. Engineering will provide the tokens to the Support/Sales person who raised the request.
  6. Support/Sales then provide both tokens to the customer along with instructions on how and where to include this in the configuration - details below.

Configuration

Docker

The feature is enabled by adding valid tokens to the .env file used to configure a FlowFuse Platform. Tokens should be added to the ASSISTANT_TOKEN and EXPERT_TOKEN environment variables (find and replace the <Assistant Token> and <Expert Token> placeholders with the actual tokens provided by FlowFuse Support/Sales).

ASSISTANT_TOKEN="<Assistant Token>"

EXPERT_TOKEN="<Expert Token>"

Restart the core application containers for the changes to take effect:

docker compose stop forge
docker compose up -d forge

Kubernetes

The feature is enabled by adding the tokens to the values passed to the Helm chart.

  • forge.assistant.enabled should be set to true
  • forge.assistant.service.url should be set to https://expert.flowfuse.com/v1/openai
  • forge.assistant.service.token should be set to the provided Assistant Token
  • forge.expert.enabled should be set to true
  • forge.expert.service.url should be set to https://expert.flowfuse.com/v4/expert
  • forge.expert.service.token should be set to the provided Expert Token
  • forge.expert.broker.address should be set to expert-broker.flowfuse.com
  • forge.expert.broker.port should be set to 8883

Example:

forge:
   assistant:
     enabled: true
     service:
       url: https://expert.flowfuse.com/v1/openai
       token: Provided-Assistant-Token
   expert:
     enabled: true
     service:
       url: https://expert.flowfuse.com/v4/expert
       token: Provided-Expert-Token
     broker:
       address: expert-broker.flowfuse.com
       port: 8883

NOTE: For FlowFuse v2.29.0 and onward the urls (forge.assistant.service.url & forge.expert.service.url) can be omitted from the configuration as they have preset defaults