How the System Works

This page explains what happens under the hood only to the extent needed for effective daily use.

High-Level Flow

1. You design a workflow from ordered workers.
2. A trigger (manual start, schedule, or external event) initiates a run.
3. Each worker processes data, possibly producing structured outputs.
4. Outputs can feed later workers or power widgets on dashboards.
5. Optional monetization applies when using paid shared assets.
6. Costs and earnings are recorded as events visible in your Profile.
7. System or user messages notify you of approvals, errors, or replies.

Workers & Execution

• Execution is sequential unless you introduce branches or specialized control workers.
• Conditions can skip downstream actions based on data.
• Widgets in a workflow context prepare data structures for dashboard visualization.

Data Visibility

• While editing, you can open Data Preview on a worker to see its immediate output.
• Results Preview shows final structured outputs.
• Errors Preview lists issues that occurred so you can adjust parameters.

Sharing & Community

• You may share a workflow or widget making it discoverable by others.
• Shared items can be free or paid (monthly or per‑run depending on type).
• Moderation: some submissions require approval before becoming public. You will receive a system message on approval or rejection.

Monetization & Credits

• Paid assets show a pricing chip: Paid: amount CURRENCY/unit.
• Credits are purchased in advance and used automatically when accessing or running paid items.
• Your Profile tracks both your Costs (consumption) and Earnings (others using your paid assets).

Messages

• System messages: approvals, rejections, notifications.
• User messages: direct communication between users (threaded).
• Mark messages as read to clear badges; reply inline to continue a conversation.

Roles (Moderators/Admins)

End users normally ignore roles. If you are granted moderator/admin rights, you can review pending shared worker versions and approve or reject them.

Reliability Tips

• Validate each worker incrementally using previews.
• Keep pricing changes minimal; the system limits frequent increases.
• Monitor your credits balance to avoid interruption when using paid assets.

Next: Requirements.