Skip to content
TROPIKALTROPIKAL Docs

TROPIKAL Connect

TROPIKAL Connect links your website or content system to TROPIKAL without asking you to paste private credentials into the browser.

After setup, your local admin screen shows discovered business objects. You choose exactly what TROPIKAL may access with three independent grants:

  • Read: TROPIKAL can list and read approved fields.
  • Write: TROPIKAL can create or update approved fields.
  • Delete: TROPIKAL can delete approved objects.

Nothing is exposed by default. Empty grants expose nothing.

How Connected Data Works

  1. Install the Connect integration for your website system.
  2. Open the local admin screen.
  3. Click Connect and complete the secure setup flow.
  4. Review discovered business objects.
  5. Enable Read, Write, or Delete only where needed.
  6. Return to the Website dashboard and sync Connected Data.

TROPIKAL then turns the approved operations into Website Functions. Website chat and jobs use those same approved Functions.

Add a Job from the website admin

After the site is connected, the local Connect Jobs card can start a central TROPIKAL setup flow. Click Add Job, then choose what the website needs:

  • Add a booking calendar creates the availability and booking Jobs together, connects the selected Google Calendar Access, and returns when both are ready.
  • Add a chat bubble creates, publishes, and binds a Website Chat Job to the connected site, then returns when Chat is live.

Calendar booking is one managed product even though it uses two Jobs behind the scenes. See Website Calendar Booking for setup, schedule, verification, and troubleshooting.

What You See In TROPIKAL

The Website dashboard shows Connected Data as business objects, not technical tools.

For each object, you can see:

  • Object name.
  • Source website.
  • Whether TROPIKAL can view, create and update, or delete it.
  • Available plain-language actions.
  • Whether writes or deletes require confirmation.
  • Last sync time and connection status.

Safety Defaults

  • No data is exposed until an admin grants access.
  • Reads return only approved fields.
  • Writes accept only approved fields.
  • Delete requires its own grant.
  • Browser pages do not receive private credentials.
  • Risky actions require confirmation where supported.