Knowledge & Capabilities

Knowledge & Capabilities define what a workflow can safely use. Knowledge contains approved source material. Capabilities are approved actions, integrations, and tools that can fetch live data, save a record, call an approved service, or operate a connected website.

The workflow owns inputs, outputs, and handoffs. A persona decides how an AI step should speak or reason when that step needs behavior. Knowledge & Capabilities define the safe boundary.

Functions and capabilities can be used directly, inside a workflow, or through a persona-backed AI step. A workflow does not need a persona to call a deterministic function, send an output, or use a website publish destination.

Start with the workflow boundary

Before adding a capability, decide:

• What the workflow is allowed to do.
• Whether it is read-only or writes data.
• Which fields the workflow can send.
• What confirmation is needed before a change.
• What error message should be shown to a user.

The capability definition should be narrower than the underlying system. If the workflow only needs to create leads, expose a create-lead function instead of a general database endpoint.

Common capability patterns

Pattern	Example	First-pass safety rule
Lookup	Check appointment slots or order status.	Read-only and scoped to one record type.
Capture	Save lead details from a chat.	Require the user to provide contact details first.
Draft	Create unpublished content.	Do not publish automatically.
Update	Change a website content field.	Confirm record and field before writing.
Website capability	Read site content, create a draft, update approved fields, or publish reviewed content.	Validate and sync the website first, then require review before publish.

Link capabilities to a workflow

Functions and integrations are reusable. Add the capability to the workflow step that needs it. If the capability should be available to an AI step, choose the persona for that step and make sure the persona is allowed to use the capability.

Test with one request that should use the capability and one request that should not.

Write clear tool descriptions

The model chooses capabilities from names, descriptions, and parameters. Use plain descriptions:

{
  "name": "create_lead",
  "description": "Save a new sales lead after the visitor provides name, contact method, and interest.",
  "parameters": {
    "name": "string",
    "contact": "string",
    "interest": "string"
  }
}

Avoid generic names like call_api or run_action. They make capability choice less predictable.

Handle tool failures

Tell the persona how to recover:

• If a required field is missing, ask a follow-up question.
• If a resource is unavailable, explain what failed in user language.
• If a write action is denied, do not retry with broader permissions.
• If a destructive action is requested, ask for explicit confirmation.

Website capabilities

When a website is connected, the Website dashboard can sync approved website capabilities into Ops workflows. A workflow can then read approved website information, create drafts, or publish reviewed content when the website exposes those actions.

If a website capability is not available:

1. Open the Website dashboard.
2. Validate the website connection.
3. Sync capabilities.
4. Confirm the needed action is listed.

Update the website connection or contact Tropikal support rather than broadening the workflow beyond what it needs.