Connected Data
Connected Data is the approved business data from a connected website. It lets TROPIKAL workflows and website chat read, create, update, or delete only the objects that have 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 business objects are ready to use.
What Connected Data can do
Common examples include:
- Read approved website content.
- List available business objects.
- Create an unpublished draft.
- Update an approved content field.
- Delete an approved object when Delete access is granted.
Connected Data should stay narrow. A workflow should receive only the objects and 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 Connected Data list is not current. | Click Sync Connected Data. |
| Data synced | The latest Connected Data list is available to workflows. | Choose the object 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.
- Connected Data is synced.
- The needed write or 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 access 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.