File Storage Integrations

File storage integrations handle the documents, images, and files that your forms collect. When a user uploads a resume, signed contract, photo, or any other file through a file upload field, Buildorado can automatically store it in the right folder in your cloud storage service. All file storage integrations authenticate via OAuth 2.0 and store credentials with AES-256 encryption through AWS KMS.

Google Drive

Google Drive is the most popular cloud storage integration in Buildorado. Upload files from form submissions and organize them into folders automatically.

Setting Up Google Drive

1. Navigate to Settings > Integrations in your Buildorado dashboard.
2. Find Google Drive and click Connect.
3. Sign in with your Google account in the authorization popup.
4. Grant the following permissions:
   • drive.file -- Create and manage files created by Buildorado
   • drive.readonly -- View files and folders for navigation
5. Once authorized, Google Drive shows as Connected with your Google account email.

You can connect both personal Google accounts and Google Workspace (formerly G Suite) accounts. For Google Workspace, your administrator may need to approve the Buildorado app in the Google Admin console.

Operations

uploadFile

Upload a file from a form submission to Google Drive.

Output:

createFolder

Create a new folder in Google Drive.

Output:

listFiles

List files in a Google Drive folder.

Output:

File Upload from Form Fields

The most common pattern is mapping a form file upload field directly to the Google Drive upload action:

[Form: Job Application]
  -- [Google Drive: Upload resume]
    fileField: {{form.resumeUpload}}
    folderId: "1ABC123_folder_id_here"
    fileName: "{{form.lastName}}_{{form.firstName}}_Resume"

Buildorado handles the file transfer automatically. The file is streamed from Buildorado's temporary storage to Google Drive without requiring you to manage URLs or binary data.

Folder Organization Patterns

Create a folder per submission:

[Form: Project Submission]
  -- [Google Drive: createFolder]
    folderName: "{{form.projectName}} - {{submission.createdAt}}"
    parentFolderId: "root_projects_folder_id"
  -- [Google Drive: uploadFile]
    fileField: {{form.projectFiles}}
    folderId: {{googleDrive_1.id}}

Finding Folder IDs

To find a Google Drive folder ID:

1. Open the folder in Google Drive in your browser.
2. Look at the URL: https://drive.google.com/drive/folders/FOLDER_ID_HERE.
3. Copy the FOLDER_ID_HERE portion and use it as the folderId value.

Tips for Google Drive

• Files uploaded through Buildorado count against the connected Google account's storage quota.
• The drive.file scope means Buildorado can only access files it created, not your entire Drive. This is a security best practice.
• For multiple file uploads (when a form field accepts multiple files), Buildorado uploads each file individually. Use a loop node if you need to process each file separately.
• Custom file names support template variables, making it easy to create descriptive, searchable file names.

OneDrive

OneDrive provides cloud storage for Microsoft 365 users. The integration works with both personal Microsoft accounts and organizational (work/school) accounts.

Setting Up OneDrive

1. Navigate to Settings > Integrations and click Connect next to OneDrive.
2. Sign in with your Microsoft account in the authorization popup.
3. Grant permissions for file read and write access. The following scopes are requested:
   • User.Read -- Read your profile
   • Files.ReadWrite.All -- Read and write files
   • offline_access -- Maintain the connection
4. Once authorized, OneDrive shows as Connected.

Operations

uploadFile

Upload a file to OneDrive (up to 4MB).

Output:

listFiles

List files in a OneDrive folder.

Output:

createFolder

Create a new folder in OneDrive.

Output:

Tips for OneDrive

• OneDrive for Business has different storage limits than personal OneDrive. Check your organization's allocation.
• Shared folders in OneDrive are accessible if the connected user has write permissions.
• The upload limit for the uploadFile operation is 4MB. For larger files, consider using the Google Drive integration or direct API calls via the HTTP Request node.

SharePoint

SharePoint integration manages SharePoint sites, lists, and list items. It is designed for working with SharePoint list data rather than document library file uploads.

Setting Up SharePoint

1. Navigate to Settings > Integrations and click Connect next to SharePoint.
2. Sign in with your Microsoft 365 account.
3. Grant permissions for reading and writing SharePoint data. The following scopes are requested:
   • User.Read -- Read your profile
   • Sites.ReadWrite.All -- Read and write SharePoint site data
   • offline_access -- Maintain the connection
4. Once authorized, SharePoint shows as Connected.

Operations

listSites

Search for SharePoint sites.

Output:

listItems

Get items from a SharePoint list.

Output:

createListItem

Create a new item in a SharePoint list.

Output:

Tips for SharePoint

• SharePoint permissions are inherited. The connected user must have Contribute or higher permissions on the target list.
• Use listSites to discover site IDs during setup, then hardcode them in your workflow.
• For document library file uploads, use the OneDrive integration instead, which can access SharePoint-hosted files via OneDrive paths.

Dropbox (Coming Soon)

Dropbox integration provides file storage for teams and individuals. This integration is currently in development and will be available in an upcoming release.

Setup

1. Navigate to Settings > Integrations and click Connect next to Dropbox.
2. Sign in with your Dropbox account in the authorization popup.
3. Grant permissions for file and folder access.
4. Once authorized, Dropbox shows as Connected.

Operations

Tips for Dropbox

• Dropbox paths are case-insensitive but case-preserving.
• Shared folders work if the connected account has edit access.
• Dropbox Business accounts have team folders with different permission models than personal folders.

OneNote

OneNote integration lets you create pages and add content to notebooks, useful for collecting structured notes from form submissions.

Setting Up OneNote

1. Navigate to Settings > Integrations and click Connect next to OneNote.
2. Sign in with your Microsoft account.
3. Grant permissions for reading and writing OneNote notebooks. The following scopes are requested:
   • User.Read -- Read your profile
   • Notes.ReadWrite.All -- Read and write notebooks
   • offline_access -- Maintain the connection
4. Once authorized, OneNote shows as Connected.

Operations

createPage

Create a new page in a OneNote section.

Output:

listNotebooks

Get a list of the user's OneNote notebooks. This operation takes no input fields.

Output:

listSections

Get a list of sections in a OneNote notebook.

Output:

Tips for OneNote

• OneNote pages are created in HTML format. Use standard HTML tags for formatting.
• Section and notebook IDs can be discovered using the listNotebooks and listSections operations.
• OneNote has a page content size limit of approximately 50 MB per page.

Notion (Coming Soon)

Notion integration is on the Buildorado roadmap. When available, it will support:

• Creating pages in Notion workspaces
• Adding entries to Notion databases
• Updating existing database records
• Querying databases with filters

If you need Notion integration now, use the HTTP Request node with the Notion API and an API key.

Airtable (Coming Soon)

Airtable integration is on the Buildorado roadmap. When available, it will support:

• Creating records in Airtable bases
• Updating existing records
• Listing records with filters
• Mapping form fields to Airtable columns

In the meantime, use the HTTP Request node with the Airtable API and a personal access token.

Best Practices for File Storage Integrations

Naming Conventions

Use descriptive file names with template variables to make files searchable:

fileName: "{{form.lastName}}_{{form.firstName}}_{{form.documentType}}_{{submission.createdAt}}"

Folder Structure

Organize files into a logical folder hierarchy. Create folders by date, department, or form type:

/Buildorado Submissions/
  /Contact Forms/
    /2024-01/
    /2024-02/
  /Job Applications/
    /Engineering/
    /Marketing/

Error Handling

File upload failures can occur due to storage quota limits, permission issues, or network problems. Attach an error handler node to catch upload failures and notify your team:

[Google Drive: uploadFile]
  -- error -- [Slack: "#ops File upload failed for {{form.email}}"]
  -- error -- [Email: Alert admin about storage issue]

Multiple File Uploads

When a form field accepts multiple files, Buildorado provides an array of file references. To upload each file individually with custom naming, use a loop node to iterate over the array and upload each file in sequence.