Production services · Automation
Faiber Flow
Connect service events to governed cross-service actions.
Faiber Flow registers endpoint events, evaluates conditions, renders payload templates, gates downstream actions, and preserves run and step history for observable product automation.
AutomationFaiber Flow
Domain recordsFlowsTriggersConditionsRuns
01Trigger
02Condition
03Action
04History
01
Feature map
The production behaviors this service owns, expressed as concrete product features instead of generic modules.
Conditional nodes and templated payloads
Gated actions across enabled services
Flow run, step status, and execution history
02
Best-fit products
Customer lifecycle automation
Connect service events to governed cross-service actions.
Payment and order follow-up
Connect service events to governed cross-service actions.
Cross-service operational workflows
Connect service events to governed cross-service actions.
03
Operational gains
Less integration glue
Faiber Flow registers endpoint events, evaluates conditions, renders payload templates, gates downstream actions, and preserves run and step history for observable product automation.
Observable automation
Faiber Flow registers endpoint events, evaluates conditions, renders payload templates, gates downstream actions, and preserves run and step history for observable product automation.
Governed service actions
Faiber Flow registers endpoint events, evaluates conditions, renders payload templates, gates downstream actions, and preserves run and step history for observable product automation.
04
Connected services
FlowsTriggersConditionsRuns
Production wiring
How it runs in a Faiber project
Select the capability during deployment. Faiber records the manifest, wires service references, exposes the API boundary, and keeps lifecycle, health, logs, and administration visible in project context.
API boundary
Application code uses the service API or typed SDK contract. Identity, permissions, tenant scope, and project context stay explicit at every read and write boundary.
Manage-ready operations
Faiber Manage opens this service beside the rest of the enabled stack, so teams can inspect records, adjust settings, review health, and ask the Manage agent for guided service changes.
infera-flowConnect service events to governed cross-service actions.
Manage agent
When payment succeeds, notify the learner and create a CRM follow-up only for high-value plans.
The conditional flow can subscribe to the payment event, render the message, and gate the CRM action.
Ready to speak, explain, and apply safe service tweaks.Technical reference
Service ID:
infera-flowInternal API port: 8060These values support deployment wiring. Product code should use configured endpoints or SDK clients, not hard-coded internal addresses.
FAQ
Questions teams ask before enabling it
What does Faiber Flow add to a Faiber application?
Faiber Flow registers endpoint events, evaluates conditions, renders payload templates, gates downstream actions, and preserves run and step history for observable product automation.
How is Faiber Flow provisioned?
Select it as a project capability. Faiber records the service manifest, resolves its dependencies, and reconciles it inside the project's isolated Kubernetes namespace.
Can Faiber Flow be used with an existing frontend?
Yes. Faiber Flow exposes a defined API surface and can be integrated from an existing React application or a new Faiber project.
Production services
Works naturally with
NotificationsFaiber Messenger
View all services 
Faiber Messenger accepts direct API calls or RabbitMQ events and turns them into localized, scheduled, channel-aware notifications with durable delivery history.
Customer operationsFaiber CRM
Faiber CRM models leads, sources, campaigns, teams, workflow nodes, reminders, worklogs, webhooks, and operating statistics for customer-facing teams.
Engagement & valueFaiber Asset
Faiber Asset supports digital catalogs, live-room resources, actions, ranks, rewards, schedules, seasons, wallets, transactions, badges, subscriptions, and metered usage records.
Faiber
Provision the capabilities your product actually needs.
Start with a real project, select services explicitly, and keep code, access, deployment, and operations connected.