Core Concepts

Organizations

An Organization is the top-level tenant in FlowTrux. Every resource - workspaces, workflows, AI providers, MCP servers, knowledge bases, forms - belongs to an organization.

Each user belongs to one organization (one email = one organization). The organization's capabilities depend on the subscription plan - from Free (basic usage) to Enterprise (full team collaboration). Paid plans require a billing address; business entities can provide a Tax ID.

Organization
├── Workspaces
│   ├── Workflows
│   ├── Forms
│   ├── Shared pages
│   └── Global variables
├── Shared resources (assigned to workspaces)
│   ├── AI Provider Keys
│   ├── MCP Server Configs
│   └── Knowledge Bases
├── Members (with roles)
└── Invites

Workspaces

A Workspace is a logical grouping within an organization that provides resource isolation. Workflows, forms, and shared pages live inside workspaces, and you can control which shared resources (AI providers, MCP servers, knowledge bases) are available in each workspace.

Use workspaces to separate concerns - for example, a "Production" workspace and a "Development" workspace, or per-team workspaces in a larger organization.

Key properties:

• Name and optional description for identification
• Enabled resources - which organization-level AI providers, MCP servers, and knowledge bases are available to workflows in this workspace
• Members - which MEMBER-role users can access this workspace
• Member permissions - what MEMBER-role users can do with the workspace's content (edit, delete, execute, publish)
• Globals - workspace-scoped variables available in workflows via {{global.key}}

Navigation

The workspace you are working in is part of the URL, so links and bookmarks always point to a specific workspace:

The left sidebar shows a tree with the organization at the top and your workspaces beneath it - each with its Workflows, Forms, and Pages sections. Owners and Admins see Create workspace and Resources actions in the header. Switching workspaces is just navigation - no reload, no mode switch.

First Visit

On your first visit FlowTrux asks a single, skippable question - "What will you automate?". Your answer:

• Pre-selects the template gallery category closest to your field.
• Creates a working demo workflow in your workspace - it needs zero configuration and runs on your plan's included AI credits, so you can press Run and see a real execution within your first minute.

You can change or delete everything the onboarding creates.

Workflows

A Workflow is a directed graph of nodes and edges that defines an automation. Workflows are stored as JSON containing the node definitions, their configurations, and the connections between them.

Workflows belong to a workspace. When a workflow runs, nodes execute in order following the connections - branches run as their conditions allow, and parallel paths run side by side.

Nodes

FlowTrux has five node types, each with a distinct color:

Each node produces output that downstream nodes can reference using template variables:

{{steps.agent-1.output.response}}
{{steps.action-2.output.data.items}}
{{trigger.data.webhookPayload}}

Execution

When a workflow runs, the engine:

1. Starts at the Trigger node
2. Traverses connected nodes in BFS order
3. Resolves template variables from previous node outputs
4. Executes each node (API calls, LLM requests, evaluations)
5. Stores results in the execution context under steps.<nodeId>.output
6. Records execution history with per-node logs, timing, and status

Executions can be streaming (SSE for real-time updates) or synchronous (wait for completion). Webhook triggers support fire-and-forget mode for background execution.

Template Variables

Data flows between nodes through Handlebars-style template variables:

When a template is the entire value (e.g., "{{steps.x.output.array}}"), the original type is preserved - arrays stay arrays, objects stay objects. When embedded in a string (e.g., "Count: {{output.count}}"), the result is string interpolation.

AI Usage and Credits

Agent nodes work out of the box - you do not need your own AI provider API key to get started. Without a key, agent calls draw from your plan's monthly AI credits. Different models consume credits at different rates, more capable models use more per call. When you add your own provider key in Resources → AI Providers, agent calls in workspaces using that key are billed directly by the provider and are not limited by the credit allowance.

Roles and Permissions

FlowTrux uses role-based access control at the organization level:

Member Permissions

For MEMBER-role users, permissions are configured per workspace and cover the workspace's content - workflows, forms, and shared pages:

Owners and Admins always have full permissions in all workspaces.

Invite Flow

Adding new members to an organization:

1. An Owner or Admin creates an invite in Settings > Members, entering the invitee's email and optionally pre-assigning workspaces
2. The new user receives the invite link (also sent by email) and registers
3. A membership request is created and waits for approval
4. The Owner or Admin approves the request in Settings > Members
5. On approval, the user joins the organization as a Member with access to the pre-assigned workspaces

One email address corresponds to one organization - a user cannot belong to several organizations at once.

Next Steps

• Editor Basics - learn how to use the visual workflow editor
• Quickstart - build your first workflow