Connectors

A connector copies files from somewhere you already keep them into a folder in your LlamaCloud project, then keeps that folder in step with the source. Once the files are in a folder you can index it or run a batch over it, the same as a folder you uploaded to by hand.

Connectors replace the older data sources. Data sources were tied to a single index. A connector feeds a folder, and anything in the project can read that folder.

Supported connectors

Source	Ways to authenticate	What one folder syncs
Google Drive	Sign in with Google, or a service account key file	One Drive folder, subfolders included
SharePoint	Sign in with Microsoft, or an Entra app registration	One folder in a document library
S3	An IAM access key pair	One bucket, optionally narrowed to a prefix
Confluence	Sign in with Atlassian, or an API token	One space, every page and its attachments

OneDrive, Azure Blob Storage, Box, Notion, Slack, and Jira show up in the list as “Coming soon”. You can’t connect them yet.

Connections and connected folders

There are two things to set up, and it helps to keep them apart:

• A connection is one authorized account at one source: a Google login, an S3 key pair, a Confluence token. You set it up once per account, on the Connections tab of the Files page.
• A connected folder is a folder in your project that syncs from part of a connection: a Drive folder, an S3 prefix, a Confluence space. You make one from Files → New folder → Connected folder.

One connection can feed as many folders as you like, and each part of a source can be synced into only one folder per connection. Connections belong to a project, so another project needs its own. You can connect a given account to a project once.

The Connections tab and connected folders are only on plans that include folder syncing. Without them, the Files page shows folders you upload to yourself.

Add a connection

1. Open Files in your project and go to the Connections tab.
2. Click Add connection, pick the source, and click Continue.
3. Sign in through the popup (Authorize), or fill in the credentials form (Connect).

When the credentials are typed in, LlamaCloud checks them with the provider before saving, so a wrong secret or a missing permission fails here with the provider’s reason instead of on the first sync. Each connector page lists what’s checked. Secrets are stored encrypted and never shown again.

Create a connected folder

1. On the Folders tab, open New folder and choose Connected folder.
2. Pick the connection. If you don’t have one for that source yet, you can authorize it from inside this dialog.
3. Choose what to sync. For the sign-in versions of Google Drive and SharePoint this opens the provider’s own folder picker. The key-based connections and S3 and Confluence ask you to type or paste the location.
4. Name the folder and click Create folder.

LlamaCloud checks that the connection can read the location before it creates anything, so a typo in a bucket name or a folder that isn’t shared comes back as “not found” or “not accessible” right away. The first sync starts as soon as the folder exists.

Set up connectors with the API

Everything on the Connections tab and in New folder → Connected folder can also be done over the REST API, including building an index or running a batch over the synced folder. Set up a connector with the API walks through it for S3.

How syncing works

Each connected folder syncs about once a day on its own. There’s no per-folder schedule to set. To pull changes sooner, open the folder and click Sync now; the sync starts within a few seconds.

On each sync:

• New files at the source are added.
• Changed files are downloaded again and replace the old copy.
• Files deleted at the source, or moved out of the synced location, are removed from the folder.

Google Drive and SharePoint read only what changed since the last sync. S3 and Confluence list the whole location every time, so a large bucket or space takes longer per sync even when little has changed.

If a sync fails, the folder shows Last sync failed with the reason and retries on its own, waiting longer between each attempt.

Stop syncing, disconnect, or delete

These do different things to the files already in your project:

Action	Where	What happens to synced files
Stop syncing a folder	The folder’s sync banner	Kept. The folder stops getting changes. The connection and its other folders carry on.
Disconnect a connection	Connections tab, row menu	Kept. Every folder on that connection stops syncing at once.
Delete a folder	Folders tab	Deleted, along with the folder. This can’t be undone.

Syncing a folder again after you stop it means creating a new connected folder and picking the location again.

When a connection breaks

If a password changes, a token expires, or someone revokes access at the source, the connection shows Expired or Revoked on the Connections tab and every folder on it shows Not syncing. Those folders don’t resume on their own.

The Reconnect menu item isn’t working yet. Until it is, the fix is to disconnect the broken connection, add it again, and recreate the connected folders. The files already synced stay where they are when you disconnect, so the new folders are the only thing to rebuild.