After Dropbox is connected to Fostr, it becomes a central source for storing and sharing content within the AI workspace. This page outlines which file and folder details are ingested, how synchronization runs, and the way Fostr uses Dropbox content to enhance Records, Actions, and collaborative workflows with real‑time context.

How Sync Works


Once Dropbox is connected, Fostr actively maintains up‑to‑date file and folder information so that workflows always pull from accurate metadata. Updates flow into Fostr in two ways:

Administrators can adjust how frequently the automatic refresh occurs at the tenant or workspace level. For example, fast‑paced teams may want more frequent syncs, while project archives may only need occasional updates. Fostr also tracks credential health, providing alerts if tokens expire or access rights change so admins can quickly restore connectivity.

Note: While Dropbox APIs do support webhook triggers in some scenarios, the integration in Fostr prioritizes scheduled cycles plus workflow checks to strike a balance between timeliness and efficiency.

What Data Gets Pulled


Fostr limits ingestion to the Dropbox attributes that matter most for operational workflows, keeping Recordsets lean and relevant.

Core data always included:

Optional or conditional data points:

Left out by default:

Organizations that want to incorporate older materials can ask for a selective backfill import, which loads legacy files or folders into Recordsets for reference without overwhelming the workspace.

Security and Access Behavior


Dropbox remains the single source of truth, while Fostr provides a structured lens for using storage data inside automated workflows. All metadata is encrypted when stored in Fostr and protected at the environment level. Credential values are write‑protected and can only be managed by admins or authorized stakeholders.

Access rules are layered:

  1. Dropbox permissions control the baseline. If the connected Dropbox account cannot see a file, Fostr will not surface it.
  2. Fostr roles add context filtering. Even when files sync successfully, only users with the right roles in Fostr (Admins, Implementers, Operators tied to a workflow) will see them in Records or Actions.