Skip to main content

Getting started

Get up and running with FlowX.AI UI Toolkit in your Angular or React application. This guide walks you through installation, basic configuration, and rendering your first component.

Prerequisites

Before you begin, ensure your development environment meets these requirements:
  • Node.js 16.x or higher
  • Angular 14.x or higher
  • npm 8.x or higher (or yarn/pnpm equivalent)
  • FlowX.AI platform access and credentials

Choose your version

Select the toolkit version that matches your FlowX.AI platform version:
FlowX.AI PlatformToolkit VersionStatus
5.5.xv10.91.0Latest
5.4.xv10.59.1Stable
5.3.xv10.32.4Stable
5.0.x - 5.2.xv9.153.6 - v10.12.1Stable
4.7.11v5.103.6LTS
4.7.0 - 4.7.10v5.80.6 - v5.103.5Maintenance
For production applications, use the toolkit version that corresponds to your FlowX.AI platform deployment. Version compatibility ensures all features work correctly.

Installation

1

Install the package

Install the UI Toolkit package for your framework:
npm install @flowx/angular-ui-toolkit@latest
To install a specific version, replace @latest with the version number: @flowx/angular-ui-toolkit@5.103.6
2

Configure the toolkit

Set up the toolkit configuration with your FlowX.AI platform connection details:
Add the FlowX module to your app.module.ts:
app.module.ts
import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { FlowxModule } from '@flowx/angular-ui-toolkit';
import { AppComponent } from './app.component';

@NgModule({
  declarations: [AppComponent],
  imports: [
    BrowserModule,
    FlowxModule.forRoot({
      apiUrl: 'https://your-flowx-api.example.com',
      processApiPath: '/process',
      authToken: 'your-auth-token',
      locale: 'en-US'
    })
  ],
  bootstrap: [AppComponent]
})
export class AppModule { }
Never hardcode authentication tokens in production code. Use environment variables or a secure configuration management system.
3

Import styles

Import the base styles to ensure components render correctly:
Add the stylesheet import to your angular.json:
angular.json
{
  "projects": {
    "your-app": {
      "architect": {
        "build": {
          "options": {
            "styles": [
              "src/styles.scss",
              "node_modules/@flowx/angular-ui-toolkit/styles/main.scss"
            ]
          }
        }
      }
    }
  }
}
4

Use your first component

Start using FlowX components in your application:
my-component.component.ts
import { Component } from '@angular/core';

@Component({
  selector: 'app-my-component',
  template: `
    <flx-process-container
      [processName]="'customer-onboarding'"
      [processStartData]="{ customerId: '12345' }"
    >
    </flx-process-container>
  `
})
export class MyComponent {
}

Verify installation

Confirm that the toolkit is properly installed:
npm list @flowx/angular-ui-toolkit
You should see the installed version number in the output.

Next steps

Installation guide

Detailed installation instructions including advanced configuration options

Usage guide

Learn how to use components effectively in your application

Theming

Customize the look and feel to match your brand

Best practices

Production-ready patterns and recommendations

Troubleshooting

Module not found error

If you encounter a “module not found” error:
  1. Verify the package is installed: npm list @flowx/[framework]-ui-toolkit
  2. Clear node_modules and reinstall: rm -rf node_modules package-lock.json && npm install
  3. Ensure your package.json lists the correct version

Styles not loading

If components appear unstyled:
  1. Verify the stylesheet import in your configuration
  2. Check browser console for CSS loading errors
  3. Ensure your build tool processes SCSS/CSS files correctly

API connection issues

If components cannot connect to FlowX.AI:
  1. Verify the apiUrl in your configuration
  2. Check network tab for failed API requests
  3. Ensure authentication tokens are valid and not expired
  4. Verify CORS settings on your FlowX.AI platform instance

Build docs developers (and LLMs) love