Workflow Naming Guide
Tropikal is workflow-first. A workflow describes the customer or owner job being handled end to end: answering a visitor, qualifying a lead, drafting content, reviewing email, preparing a booking request, or handing work to an owner.
The public authenticated app host is app.tropikal.ai. ops.tropikal.ai is
retired and must not be used for browser or API traffic.
Use this language in customer docs:
| Term | Use it for |
|---|---|
| Workflow | The end-to-end job Tropikal is helping run. |
| Run | One execution of a workflow. |
| Persona | Optional AI behavior inside a workflow: tone, boundaries, and escalation rules. |
| Function | An approved action a workflow can run. |
| Knowledge | Approved sources a workflow can use when answering or drafting. |
| Capabilities | Approved actions, integrations, and tools the workflow may use. |
| Connected Data | Approved business objects synced from a connected website. |
| Channels | Places where the workflow starts or hands off, such as website chat, email, Telegram, or dashboard review. |
| Handoff | The owner-ready result: lead details, summary, draft reply, booking request, or next action. |
| Website publish destination | A workflow output that sends reviewed content to a connected website. |
Legacy technical labels
Some older database identifiers, file paths, and code symbols still use historical labels. Treat those as implementation strings, not as the product category. For customer-facing explanation, use workflow and persona.
Examples:
| Prefer | Avoid |
|---|---|
| AI Front Desk workflow | AI Front Desk as a standalone bot product |
| Configure the persona | Write the soul |
| Knowledge & capabilities | Operating map |
| Website Embed workflow | Public chat bubble as the whole product |
| Owner handoff | Raw AI output |
What belongs where
The workflow owns the job, Trigger, Work Steps, Conditions, workload package, outputs, and handoffs. The persona owns how the AI should behave while performing that job. Knowledge and capabilities define what the persona can safely use.
Do not put changing business facts into the persona. Put approved facts in Knowledge. Do not describe broad system powers in the persona. Add only the capabilities the workflow needs.
Do not present Website Embed, email, Telegram, or output destinations as persona setup. Configure where a workflow starts in the Trigger node and where it ends in the Output node. In Trigger, Channel opens Public Channels rows for Public Embed, Email, and Telegram; deeper channel settings open in the workflow inspector.
Compatibility references
Keep exact implementation strings only when accuracy matters, but explain the customer behavior as a workflow using a persona, knowledge, Connected Data, and capabilities.