- handbook
- Company
- Company
- Board & Investors
- Communications
- Decision making and project management
- Guides
- Organizational Structure
- principles
- Remote Work
- Security
- Access Control Policy
- AI Development and Customer Data Policy
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Cryptography Policy
- Data Management Policy
- Hardware Security Policy
- Human Resources Security Policy
- Incident Response Plan
- Information Security Policy and Acceptable Use Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Secure Development Policy
- Third-Party Risk Management Policy
- strategy
- values
- Operations
- Engineering & Design Practices
- Design
- Engineering
- Contributing
- Front End
- Packaging Guidelines
- Platform Ops
- Deployment
- FlowFuse Dedicated
- Incident Response
- Observability
- Production Environment
- Self Hosted Assistant
- Staging Environment
- Update Stacks on Production
- Product
- Blueprints
- Feature Catalog
- Feedback
- Glossary
- Market Segments
- Metrics
- Node-RED Dashboard
- Personas
- Pricing Principles
- Principles
- Product Growth
- Product Swimlanes
- Strategy
- Versioning
- vision
- Project Management
- Releases
- Security Policy
- Support
- tools
- Internal Operations
- People Ops
- Coaching Plans
- Code of Conduct
- Compensation
- Expenses
- Hiring
- Holiday & Leave
- Job Descriptions
- Account Executive
- CEO
- Chief of Staff
- CTO
- Developer Relations Advocate
- Engineering Manager
- Fullstack Engineer
- Fullstack Engineer (AI-Focused)
- Head of Marketing
- Product Manager
- Product Marketer
- Solutions Engineer
- Technical Product Manager
- VP of Sales
- PeopleOps Policies
- Performance review
- Summit
- Marketing department
- Marketing
- blog
- Brand Voice
- Community
- Company Messaging
- Customer Stories
- Events
- FlowFuse for Education
- How we work
- Lead Activation
- Lead Generation
- Marketing - Website
- Marketing Programs
- Social Media
- Webinars
- Sales department
- Sales
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
- Customer emails
support@flowfuse.com - Support needs to verify that the customer has a current Enterprise License
- Once confirmed, Engineering needs to create two access tokens for the customer.
- Assistant: Open the Instance Settings for the
flow-geninstance in theInternal ToolsApplication. 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. - Expert: Open the Instance Settings for the
flowfuse-expert-apiinstance in theInternal ToolsApplication. 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.
- Assistant: Open the Instance Settings for the
- Provide the 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 editing the configs.flowfuse.content section at the top of the docker-compse.yml file.
Add the following after the end of the npmRegistry section. The assistant and expert keys should be indented 6 spaces to match.
Insert the two tokens
assistant:
enabled: true
service:
url: https://flow-gen.flowfuse.cloud/v1/openai
token: <Assistant Token>
expert:
enabled: true
service:
url: https://flowfuse-expert-api.flowfuse.cloud/v4/expert
token: <Expert Token>
Kubernetes
The feature is enabled by adding the tokens to the values passed to the Helm chart.
forge.assistant.enabledshould be set totrueforge.assistant.service.urlshould be set tohttps://flow-gen.flowfuse.cloud/v1/openaiforge.assistant.service.tokenshould be set to the provided Assistant Tokenforge.expert.enabledshould be set totrueforge.expert.service.urlshould be set tohttps://flowfuse-expert-api.flowfuse.cloud/v4/expertforge.expert.service.tokenshould be set to the provided Expert Token