How can we help you?

Uniflect is an integration and data-flow platform. You design visual flows inside workspaces, connect external systems with connectors, store structured data in workspace databases, and expose flows or queries as HTTP APIs — with monitoring, analytics, and Copilot built in.

Most teams start with one of these patterns:

• Sync data between SaaS tools (CRM → warehouse, tickets → spreadsheet)
• Automate webhooks into multi-step workflows (validate → transform → notify)
• Publish an integration as a live HTTP endpoint for partners or internal apps
• Stage records in a workspace database before downstream steps run

You do not need every feature on day one. A single workspace with one HTTP-based integration is enough to learn the designer, runs, and debugging.

Registration creates three things at once: your user, an organization (Personal or Company), and a default workspace you can open immediately.

Steps:

1. Open your Uniflect URL (local dev: http://localhost:9000) and go to Register (/auth/register).
2. Choose Personal (solo) or Company (team admin, invites, org-wide settings).
3. Enter name, email, and password, then submit.
4. You are signed in and land on the organization dashboard (/).

Personal vs Company: Personal is ideal for evaluation and solo builders. Company adds Organization administration — invite members, assign org roles, and govern multiple workspaces under one org.

If registration fails, check email format, password policy, and that your backend is reachable (self-hosted: confirm DATABASE_URL and migrations).

Sign in: Go to /auth/login, enter email and password, optionally Remember me, then Sign in. You should reach the organization dashboard.

Forgot password: On the login page, choose Forgot password, submit your email, and follow the reset link. Links expire; request a new one if needed.

Common login problems:

• Invalid credentials — confirm caps lock and the correct instance URL (staging vs production).
• Redirect loop — clear site cookies; in dev, ensure the backend JWT secret did not change between restarts.
• Account pending invite — you may need to accept an organization invite email before first login.

Sessions use JWT tokens from the backend; when a token expires you are prompted to sign in again.

This path mirrors how most teams onboard without getting lost in optional features:

1. Skim the organization dashboard — workspaces list, marketplace entry, account menu.
2. Open the default workspace (or Add workspace if you need a named project).
3. Read the workspace sidebar — Integrations, Connectors, Databases, APIs, Monitoring.
4. Create your first integration — Trigger + HTTP (or Log) steps, Save definition, Run now.
5. Open run detail — confirm each step status and output; fix config and re-run if needed.
6. Bookmark the Help Center — guides with screenshots plus this FAQ for quick answers.

Avoid production connectors until you have a successful manual run. Use public test APIs (e.g. httpbin) or Log steps to validate templates first.

Organization level (after login): dashboard, Workspaces, Marketplace, Account, and Administration (org admins).

Inside a workspace, the left sidebar is your daily toolkit:

• Integrations — flow designer, run history, manual runs
• Connectors — installed adapter instances and credentials
• Data mappings & Email templates — reusable workspace resources
• Databases & APIs — tables and published HTTP endpoints
• Monitoring & Analytics — operational metrics and custom dashboards
• Copilot — AI help for flows and debugging

Everything in that list is scoped to the workspace — another workspace in the same org does not see your integrations or keys unless you share access via roles.

Mobile / tablet: The UI is responsive. You can review runs, monitoring, and notifications on smaller screens. Flow design (canvas, drag-connect, dense config panels) is best on desktop.

Theme: User menu → Preferences → Theme → Light, Dark, or System (follows OS).

Language: When multiple locales are enabled, Preferences → language dropdown updates UI strings for your session.

Neither theme nor language changes integration definitions or run data — only presentation.

A full local stack (via ./uniflect.sh dev) typically exposes:

• Frontend — 9000 (UI)
• Backend API — 4000 (auth, workspace APIs, Copilot)
• Marketplace — 4100 (connector adapters)
• Workflow — 4200 (flow execution)
• Help Center / docs — 9200
• Landing page — 9100 (optional)

PostgreSQL is required. Redis is optional in dev; set FLOW_USE_REDIS=true when you want BullMQ-backed queue processing closer to production.

If a service is down, connector steps and runs fail in predictable ways — check health endpoints and logs before debugging individual flow steps.

Open Account from the user menu (top bar).

Profile: Update first and last name. Email changes may require admin approval depending on deployment — check with your org admin if the field is read-only.

Security: Change password by providing current password plus new password twice. Use a unique password; Uniflect stores only a salted hash server-side.

Preferences: Set theme (light / dark / system) and language when available. These apply to your browser session only.

Sign out from the same menu when using a shared machine.