Use Page actions → Upload files (previously Site upload/SharePoint upload) to send answer attachments, ordinary uploads or Bulk Data files to SharePoint, S3, Google Cloud Storage, Azure Blob Storage or Govforms storage. Choose a connection configured in Library settings; QA and Production use their own settings.

Select the file and evidence version

Select the Bulk Data component for corrected answers. Choose current confirmed data (default), first-submitted (submitted revision 1), or a specified submitted revision number. Choose validated CSV (default) or the untouched upload associated with that evidence. Intermediate edit numbers are not submitted revisions. Historical evidence requires retained Response history; unavailable selections fail rather than returning another file. For repeating Bulk Data, specify the zero-based repeat row.

Filename and timing

Enter the filename without extension; Govforms adds .csv for validated data or the untouched upload’s original extension. Liquid is supported, for example bulk-{{ form.submissionId }}. Use distinct filenames for separate exported revisions. Run after the respondent confirms the data; historical selections require the revision to have been retained. Use existing workflow triggers for post-submission delivery and test real files in QA.

Transfers stream through the configured store and do not use the 25 MiB Base64 allowance. Provider and execution limits still apply. This action delivers files; creating one SharePoint list item per row requires external row processing.

Bulk Data evidence and integrations

The validated CSV includes respondent corrections; the untouched upload is retained separately. Use Upload files to send a selected Bulk Data evidence version to a configured file store. API actions can send up to 25 MiB of combined raw files as Base64; larger files can be streamed through the Bulk Data download API. Submitted revision selection requires retained Response history.

Bulk Data files, submitted revisions and integration examples