Website Capabilities
Website capabilities are approved actions from a connected website. They let Tropikal workflows read, draft, update, or publish only the website work that has been enabled for that connection.
You do not need to manage the technical connection yourself. The Website dashboard checks the connection in the background, then shows whether the approved capabilities are ready to use.
What capabilities can do
Common examples include:
- Read approved website content.
- List available website content types.
- Create an unpublished draft.
- Update an approved content field.
- Publish an approved article after review.
Capabilities should stay narrow. A workflow should receive only the actions it needs for the job.
Readiness statuses
| Status | What it means | What to do |
|---|---|---|
| Ready | The website is connected and capabilities are available. | Use the website in workflows or website chat. |
| Validate required | Tropikal has not checked this connection yet. | Open the website and click Validate. |
| Connected, sync needed | The website connection works, but the capability list is not current. | Click Sync tools. |
| Tools synced | The latest website capability list is available to Ops workflows. | Choose the capability or publish destination in a workflow. |
| Blocked by policy | The website did not allow this connection or action. | Open the readiness details and contact Tropikal support if the next step is unclear. |
Publish readiness
Publishing is treated more carefully than reading or drafting. A website publish destination should be used only when:
- The website connection is ready.
- Website capabilities are synced.
- A publish action is available.
- The workflow has a review step before publishing.
- The run has approval before content is sent to the website.
If no Website publish destination appears in the workflow builder, return to the Website dashboard and validate or sync the website first.
Safe operating rules
- Start with read-only capabilities when testing a new website.
- Use draft or review steps before publishing.
- Do not expose credentials, private operations, or content the workflow should never show.
- Review important content before it goes live.