Google Drive and Google Sheets
In this version, Google connections use a service account. Paste its JSON into the secret field; the system validates the structure and stores client_email as the visible service-account address. Grant that address access to the required spreadsheet or file.
- Create a Google connection and paste the service-account JSON into the protected field.
- Run “Test”: it confirms account authentication.
- In the source, choose Google Sheets or Google Drive and specify the file.
- Set the sheet and range and check reading. Access to the specific file is verified here.
OneDrive
| Field | What to specify |
|---|---|
| Login method | A Microsoft Entra application or user token. |
| Tenant ID / Client ID | For application-based login. |
| Client secret / Access token | The selected login method's secret. |
| Drive ID | The drive accessible to the account. |
| File path | Specified in the source relative to the selected drive. |
A user token must be renewed after expiry. For continuous operation, choose an access method agreed with your organization.
S3
Specify the HTTPS S3 API address, bucket, region, access key ID and secret access key. For temporary keys, add a session token. An optional prefix restricts the starting folder. The connector uses /bucket/key addressing; check compatibility with your storage.
FTP / FTPS
Specify the address, user, password and root folder. ftps:// means explicit TLS with certificate validation; ftp:// means unencrypted access. Passive mode is used, and the file path is relative to the root. SFTP is a different protocol and is not part of this connection type.
Network drive
The administrator first mounts the SMB/NFS resource on the system running the API and executor. The connection specifies the mounted folder's local path. Both services must see it consistently and have the required permissions. Symbolic links are not used.
Local folder through UBC Agent
“Local folder (through UBC Agent)” represents an allowed folder on the agent computer, a network resource or a mounted drive. Choose the registered agent and root folder; test reading and separately verify write permission if the flow will create files. A source reads a particular file, a destination writes its supported range, and a file-transfer block handles files and folders as objects. Agent access boundaries are not widened by selecting a file in a flow.