Tropikal Concepts
These are the main Tropikal words you will see in the dashboard and docs.
| Term | Meaning |
|---|---|
| Workflow | The job Tropikal runs from start to finish. |
| Run | One time a workflow runs. |
| Persona | Optional AI behavior, tone, and decision style for steps that need it. |
| Function | An approved action a workflow can run. |
| Knowledge | Approved information a workflow can use. |
| Capability | An approved source or action available to a workflow. |
| Website capability | An approved action from a connected website. |
| Review step | A checkpoint where a person approves or rejects work before it continues. |
| Website publish destination | A workflow output that sends reviewed content to a connected website. |
Workflow
A workflow is the whole job. Examples:
- Answer a website visitor and prepare a lead handoff.
- Summarize forwarded email for owner review.
- Draft a blog article and send it for approval.
- Publish approved content to a connected website.
Workflows can start from a channel, a schedule, or a manual run.
Run
A run is one execution of a workflow. The Runs page shows what happened: which steps ran, what needs review, and whether the output succeeded.
Persona
A persona is optional. Use one when an AI step needs a tone, role, or behavior rule.
You do not need a persona for every workflow. A workflow that only moves structured data, calls a function, sends a notification, or publishes approved content may not need one.
Function
A function is an approved action. It can read information, create a draft, send a handoff, or call a connected service.
Functions can be used:
- directly from the Functions area when enabled,
- inside a workflow step,
- or by an AI step when the selected persona is allowed to use it.
Knowledge & Capabilities
Knowledge is the information a workflow can rely on. Capabilities are the approved actions it can take.
Keep both narrow. A workflow should only see the information and actions needed for the job.
Website capabilities
When you connect a website, Tropikal can sync the website actions that are approved for workflows. For example, a website might expose a safe action for publishing an approved article.
These actions appear as Website capabilities after the website is validated, connected, and synced.
Review steps
Review steps keep important work human-approved. Use review before publishing, sending external messages, or changing website content.