Zoho Forms vendor uploads to OneDrive: avoid duplicate folders
Set up a Zoho Forms vendor document upload automation that sends every submission to the right OneDrive folder, with no duplicate vendor folders.
Vista Viewpoint to BambooHR Integration (SFTP File Workflow)
Set up a Vista Viewpoint BambooHR integration over SFTP: export pay stubs and time cards, match each employee, and upload every PDF. See the full workflow.
TABLE OF CONTENTS
A Vista Viewpoint to BambooHR integration works best as a one-way file workflow: Vista exports time cards and pay stubs on a schedule, drops them into an SFTP folder, and an automation validates, renames, and uploads each PDF into the right employee record in BambooHR. It is the simplest reliable pattern for construction companies that run payroll in Vista and manage people in BambooHR.
What a Vista Viewpoint to BambooHR integration can (and can’t) automate
Most HR teams start with documents, because that is where the manual work piles up:
- Pay stubs (PDF)
- Time cards (PDF or report export)
Optional add-on scope (usually low lift once employee matching is solved):
- Basic demographics (name, address, craft codes, class codes, etc.)
Out of scope for the “minimal SFTP workflow” (unless you’re explicitly building it):
- Tax setup, direct deposit, benefits, or full payroll run data
- Analytics dashboards and reporting packs
The minimal integration architecture (SFTP → transform → upload)
- Export from Vista Viewpoint
- Schedule a report/export that produces the documents you need.
- Confirm whether your Vista environment can produce one PDF per employee (strongly preferred) or a combined PDF that must be split.
- Drop into a secure SFTP folder
- Vista (or a Vista-managed process) outputs files into an SFTP “drop” location.
- Keep separate inbound folders (at minimum):
/inbound/pay-stubs//inbound/time-cards/- Transform + validate (automation step)
- Validate required fields exist (employee ID / employee number, pay period, document type).
- Normalize file naming (so downstream uploads are deterministic).
- Reject or quarantine files that can’t be matched to an employee.
- Upload into BambooHR employee records
- Upload each file to the correct employee’s Files tab in the matching category. (BambooHR API upload-by-category confirmed as of October 2026.)
- Set up two employee file categories (BambooHR’s folders apply to every employee record, so you create them once):
- “Pay Stubs”
- “Time Cards”
- Put the document in the matching folder.
Employee matching: the make-or-break detail
You need a stable key that exists in both systems. In practice, one of these works best:
- Employee number (ideal)
- A mapped external ID
- Email (works, but can be messy with aliases)
If you don’t have a stable key in the exported document or filename, the workflow will stall until Vista can include it.
File naming + folder structure that avoids rework
Use a convention your team can eyeball and your automation can parse:
EMPLOYEEID_YYYY-MM-DD_PAYSTUB.pdfEMPLOYEEID_YYYY-MM-DD_TIMECARD.pdf
Recommended structure:
/inbound/pay-stubs//inbound/time-cards//processed//error/unmatched-employee//error/missing-fields/
Common gotchas (and how to plan around them)
- Time card documents are “somewhere in Vista” but nobody can find them.
- Treat this as a discovery milestone: confirm where the attachment is stored and whether it’s exportable.
- Missing report access / permission scopes.
- The integration depends on the right Vista roles/licenses to run exports.
- Combined PDFs instead of one file per employee.
- Splitting is doable, but you’ll need a reliable delimiter (employee number printed on each page).
- Non-deterministic file names coming out of Vista.
- Fix it in the transform step before you upload anything.
What drives the cost
For a document-focused integration (time cards + pay stubs) with SFTP and automated uploads, cost depends mostly on:
- How much work it takes to get clean, one-file-per-employee exports out of Vista
- How many employees and documents run through the workflow each pay period
When to consider a different approach than SFTP
SFTP is great when the source system’s cleanest output is a report or document export. If you need deeper data sync (two-way changes, complex payroll objects), consider an API-led integration instead.
Next steps
If you want this implemented, start by confirming two things in Vista:
- How pay stubs can be exported (format + schedule)
- Where time card attachments live and how to export them
Once those are confirmed, you can finalize field mapping and automate the SFTP-to-BambooHR upload flow.
Get help building this
Vista to BambooHR projects usually stall at the export step: time card attachments nobody can find, or a combined PDF with no employee number to split on. If you have hit that wall, book a ZoomFlow session and one of our consultants will map the export, the employee matching key, and the upload flow with you live.
Related Posts
Foundation payroll to BambooHR: PDF-first integration
Automate Foundation payroll into BambooHR when there’s no API. Learn a PDF-first workflow to split pay stubs, validate with CSVs, and upload to BambooHR Files.
Automate Foundation payroll pay stubs into BambooHR
If your construction payroll runs in FOUNDATION, here's how to automate pay stub generation and upload into BambooHR—no manual sorting required.
