UBCDATA BRIDGE
HomeIllustrative use case
Illustrative use case

Use local files in cloud workflows

Keep files on the computer or server where your team works. Agent on Windows, macOS or Linux gives Data Bridge access to the required folder so it can prepare the data and send the result to a cloud system.

ExcelCSVUBC Data Bridge AgentGoogle SheetsCloud API
HOW THE WORKFLOW RUNS
ExcelCSVUBC Data Bridge AgentGoogle SheetsCloud API
01Authorise the working folder
02Select the source
03Apply preparation rules
04Deliver the result
THE CHALLENGE

What slows the work down

A workbook lives on a desktop or network drive, but its result is needed in a cloud application. Someone repeatedly opens it, changes its structure and transfers data. The process depends on remembering the steps and choosing the correct version.

Accountants, analysts, consultants and smaller teams with repeated file-preparation tasks.
A PRACTICAL EXAMPLE

Illustrative scenario: a consultant regularly prepares reporting data from an agreed workbook template. They place the file in an authorised folder, run the workflow and receive results in designated cloud storage.

HOW THE WORKFLOW RUNS

From the first step to the right action.

01

Authorise the working folder

Configure Agent on an available Windows, macOS or Linux computer. Add the required folder, file masks and only the read or write permissions the process needs.

02

Select the source

Connect the folder through Agent and define the file, sheet or range. Agree how the current version is selected so an earlier document is not processed accidentally.

03

Apply preparation rules

Check columns, standardise formats and calculate required measures. Inspect a simulation using an example file before relying on the workflow for repeated processing.

04

Deliver the result

Write prepared data to a connected cloud spreadsheet, API or storage location. If needed, return an agreed output file to the authorised folder and review the run history.

VALUE FOR THE TEAM

Make the work repeatable.

  • The team retains a familiar way of working with files while gaining a repeatable preparation process.
  • A first workflow can start with one stable template and a clearly defined destination.
  • Agent permissions can limit the route to specific resources rather than exposing every file on the computer.

Keep control of the result.

  • Keep the Agent computer and required network resource available while the workflow is running.
  • Grant the service account appropriate permissions and check operating-system requirements for access to the folder.
  • Process only agreed files and data, with clear naming, version selection and result-retention rules.
THE WORKFLOW OUTCOME

Repeated work on a local file becomes a controlled route to the cloud, with a defined source, maintained preparation rules and a checked destination.

Capabilities behind this workflow
FROM IDEA TO WORKING FLOW

Bring your challenge. See a way forward.

Sources, rules and outcomes — let’s build the conversation around your workflow.