Cloud and business-system destinations

Besides folders, SFTP, SQL Server, REST and C# scripts (see Output and export), a Batch Setup can deliver its documents straight to cloud drives, document management systems and business systems. Add them on the Output & export tab under Add destination; the list is grouped by kind. Each destination has a form, a Test button that signs in and checks the folder, library or table, and can use the output above or Its own output.

Passwords, client secrets, keys and tokens are never typed into a Batch Setup: save them under Settings › Secrets and choose the secret's name in the form.

How the destinations work

File destinations (drives, storage, servers, document management) receive the files of the export — the documents' PDF or TIFF files and the data files — under their Folder, with the output's own folders and file names. Nothing is uploaded until the export is complete; if one upload fails, the files this export already uploaded are deleted again, so a retry starts clean. When the file exists chooses between keeping both, replacing or stopping (where the service allows it).

Most file destinations can also fill Metadata from the document: SharePoint library columns, CMIS properties, M-Files properties, DocuWare index fields, S3 and Azure metadata, Google Drive properties, Box and ShareFile descriptions. Each row is the target (a column, property or field name) and the value.

Business systems (ERP, accounting, CRM, service desk) get one record per document, made from Fields, with the document's files attached when Attach the document's files is on. Records are created when the export completes; if one fails, those this export already created are removed again where the system allows it (Xero drafts are marked deleted, SAP Business One documents are cancelled).

Values: fields, fixed texts and templates

In Metadata and Fields, the value can be:

Value	Example	Result
A field of the document or the batch	`InvoiceNumber`	the field's value
A fixed text	`DRAFT`	DRAFT
A template	`{{ field.InvoiceNumber }}/{{ batch.fields.Branch }}`	INV-1/Leeds

Templates see field (the document's fields), doc (number, class, class_name, page_count, tables), batch (name, class, fields …) and documents, as in file names. Empty values are left out.

For business systems the target can say the type and the shape:

Target	Sends
`Total:number`	a number (currency signs and thousands separators are removed: £1,200.50 → 1200.50)
`Quantity:integer`	a whole number
`InvoiceDate:date` / `PostedAt:datetime`	a date (2026-10-01) / a date and time
`Paid:bool`	true for yes, true, 1, y
`Contact.Name`	a nested object: `{ "Contact": { "Name": … } }`
`Lines:json`	the value as JSON

Record scripts: line items and other shapes

Build the record with a script runs JavaScript for what a mapping cannot express, such as line items from a table. It gets document (fields, tables, class), batch, values and mapped (the mapping's result), and returns the record:

mapped.LineItems = document.tables.Lines.map(r => ({
  Description: r.Description,
  Quantity: Number(r.Quantity || 1),
  UnitAmount: Number(r.Amount),
  AccountCode: '400'
}));
return mapped;

Microsoft 365

Destination What you need

SharePoint / Microsoft Teams An app registration in Microsoft Entra ID with the Microsoft Graph application permission Sites.ReadWrite.All (or Sites.Selected with access to the site), admin consent and a client secret. Enter the Directory (tenant) id, Application (client) id, the secret, the Site address (https://contoso.sharepoint.com/sites/Finance) and the Document library (Documents by default). For a Teams channel, use the team's site and Documents, with the channel's name as Folder. Metadata fill library columns: use the column's internal name.

OneDrive for Business The same kind of app with Files.ReadWrite.All, and the User whose OneDrive receives the files.

Destination	What you need
SharePoint / Microsoft Teams	An app registration in Microsoft Entra ID with the Microsoft Graph application permission Sites.ReadWrite.All (or Sites.Selected with access to the site), admin consent and a client secret. Enter the Directory (tenant) id, Application (client) id, the secret, the Site address (`https://contoso.sharepoint.com/sites/Finance`) and the Document library (Documents by default). For a Teams channel, use the team's site and Documents, with the channel's name as Folder. Metadata fill library columns: use the column's internal name.
OneDrive for Business	The same kind of app with Files.ReadWrite.All, and the User whose OneDrive receives the files.

Files up to 4 MB are uploaded in one request, larger ones in an upload session.

Cloud drives and storage

Destination	What you need
Google Drive	A Google Cloud service account with the Drive API enabled; save its whole JSON key file as a secret. Share the target folder with the service account's e-mail address as Editor (on a shared drive: Content manager) and copy the Folder id from the folder's address. With domain-wide delegation, Act as user makes the files belong to that user.
Dropbox	An app in the Dropbox App Console with files.content.write, its App key and App secret, and a refresh token got once by authorising the app with `token_access_type=offline`.
Box	A Custom App with Server Authentication (Client Credentials Grant), authorised by the Box admin; its Client id and secret and the Enterprise id (files belong to the app's service account) or a User id. Folder id 0 is All Files; share the folder with the service account.
ShareFile	An API client (ShareFile › API key), a user and password, the account subdomain and the target Folder id (fo…).
Amazon S3 / S3-compatible	An access key with write rights on the bucket. For IBM Cloud Object Storage create HMAC credentials and use the regional endpoint (e.g. `https://s3.eu-gb.cloud-object-storage.appdomain.cloud`); the same works for Wasabi, MinIO, Backblaze B2, Cloudflare R2, DigitalOcean Spaces and Oracle Object Storage.
Azure Blob Storage	A connection string, or the account address with a SAS token allowing create, write and delete, and the Container.

Servers and e-mail

Destination	What you need
FTP / FTPS server	Server, port, user and password. Use TLS (FTPS) is on by default; switch it off only inside your own network. For SFTP use the SFTP server destination.
WebDAV	The WebDAV address (Nextcloud: `https://cloud.example.com/remote.php/dav/files/<user>`), user and password (in Nextcloud an app password). Also SharePoint Server, IIS and Apache WebDAV.
E-mail (SMTP)	The SMTP server, sign-in, From and To. To, Subject and Message may be templates (`{{ field.SupplierEmail }}`). Send one e-mail per batch or per document; Largest attachments stops an export whose files are too large for the mail server. An e-mail cannot be called back, so make it the last destination.

Document management

Destination	What you need
CMIS repository	The repository's CMIS 1.1 browser binding address — IBM FileNet P8 (`https://host/fncmis/browser`), Alfresco (`https://host/alfresco/api/-default-/public/cmis/versions/1.1/browser`), OpenText Documentum, Nuxeo, SAP Document Management — user and password, the Folder path, and the Document type (`cmis:document` or your own). Metadata are properties by their id, e.g. `inv:number` ← `InvoiceNumber`.
M-Files	The M-Files Web address, the vault GUID, user and password, the Class id and Object type id (0 = document). Metadata are property ids: `1020` ← `InvoiceNumber`; add `:lookup` for a list property and give the item's id.
DocuWare	The DocuWare address (`https://<organisation>.docuware.cloud`), user and password, and the File cabinet id. Metadata are index fields by their database name, e.g. `INVOICE_NO` ← `InvoiceNumber`.

ERP and accounting

Destination	What you need
SAP S/4HANA	A communication arrangement for the API (e.g. Supplier Invoice Integration, SAP_COM_0057) with a communication user; the system address and, on premises, the sap-client. The Service and Entity set default to supplier invoices (`API_SUPPLIERINVOICE_PROCESS_SRV` / `A_SupplierInvoice`). To attach the PDF, give the business object (`BUS2081` for supplier invoices) and its key from the created record (`{{ created.SupplierInvoice }}{{ created.FiscalYear }}`). DocView fetches the CSRF token SAP requires.
SAP Business One	The Service Layer address (`https://b1server:50000/b1s/v1`), company database, user and password, and the Document (`PurchaseInvoices`, `Drafts` for approval, `PurchaseOrders` …). The PDF goes to the attachments folder and is linked to the document.
Dynamics 365 Business Central	An Entra ID app with API.ReadWrite.All, registered in Business Central (Microsoft Entra applications); the environment, company id and records (`purchaseInvoices` …). Files become document attachments.
Xero	A Custom Connection app in the Xero Developer portal, authorised by the organisation; its client id and secret. Choose what to create (bills are Invoices with Type `ACCPAY`). Files become attachments.
QuickBooks Online	An app in the Intuit Developer portal (scope com.intuit.quickbooks.accounting), its client id and secret, the company's realm id and a refresh token got once when the company authorises the app. QuickBooks renews the refresh token from time to time; DocView saves the new one into the same secret. Files become attachments.

CRM, service desk and integration

Destination	What you need
Dynamics 365 / Dataverse	An Entra ID app added to the environment as an application user with a role that may create the records; the environment address, the table's entity set name (plural, e.g. `incidents`) and logical name (singular, e.g. `incident`). Files become notes of the record. Lookups bind with `customerid_account@odata.bind` ← `/accounts({{ field.AccountId }})`.
Salesforce	A connected app with the client credentials flow and a run-as user; the My Domain address, consumer key and secret, and the Object (`Case`, `Invoice__c` …). Files become Salesforce Files linked to the record.
ServiceNow	An integration user with the rest_service role and create rights on the Table (`incident`, a custom table …). Files become attachments.
OData service	Any OData v2 or v4 service: its address, sign-in (user and password, bearer token, or an Entra ID app with a scope), and the Entity set. Turn on Fetch a CSRF token first for SAP Gateway services.

For Power Automate, Zapier, Make or your own API, use the REST / webhook destination (see Output and export); for anything else, a C# export script.

Try it

The Cloud drives and business systems template on the System features tab of New Batch Setup exports to a folder and has SharePoint, Xero and SAP S/4HANA destinations prepared and switched off: fill in your sign-in, click Test and switch one on. See Batch Setup templates.