Configure the SharePoint destination in Integrate.io ETL to write pipeline output to a SharePoint document library as CSV, JSON, or Excel.
Use the SharePoint destination component to write data from your Integrate.io ETL pipeline to a Microsoft SharePoint document library. Output is written as a single file in CSV, JSON, or Excel (XLSX) format.
The SharePoint site that contains the target document library. Enter a site name (for example, mysite) or the full URL (for example, https://company.sharepoint.com/sites/mysite). When a site name is used, the site URL is built from the tenant configured on the connection.
The document library, optionally followed by a folder path inside it. Example: Shared Documents/exports. The library must already exist. Any missing folders in the path are created when the job runs.
For CSV and Excel output, controls whether row 1 is written from the column names. For Excel output in template mode, the default is off so the template’s own header row is preserved; for every other case the default is on.
Select Excel (XLSX) as the file format to write an .xlsx workbook. Numbers and booleans are written as typed cells; text values are written as strings. Very large integers (above 2^53) and decimals with more than 15 significant digits are written as text so no digits are lost.Excel output has two extra fields:
Path to an existing .xlsx file inside the same document library. Enter the path relative to the library root, for example, Templates/Job Assignments - Blank.xlsx. You can also enter the path with the library segment in front, matching the way SharePoint displays it, for example, Shared Documents/Templates/Job Assignments - Blank.xlsx. The leading library segment is stripped automatically. The path is not relative to the folder set in Path.In template mode, the workbook is downloaded, the rows in the named sheet are replaced from row 2 down, and the result is uploaded to the destination file. Every other sheet, dropdown, formula, column style, autofilter, and named range in the workbook is preserved. The template itself is not modified.Use template mode when the output has to fit a workbook the recipient already relies on. Examples include workbooks with cross-sheet dropdowns driven by lookup tabs, or with formatting and formulas that must survive the run.Behavior in template mode:
Row 1 stays the header row. With Write header row on, it is rewritten from the column names; with it off, the template’s header is kept exactly as-is.
Rows past the last written row are removed from the sheet, so a shorter run does not leave stale data behind.
Column styles from the template are copied onto any new cells written below the existing rows.
List dropdowns whose source range points at the target sheet are extended to cover every row written, so a longer run does not silently truncate the list. The applied range (the cells the dropdown appears on) is left as the template author set it.The job fails with a clear message when the sheet name is not present in the template workbook. The message lists the sheets that are.If the target file is locked in SharePoint (for example, someone has it open for editing), the upload retries with backoff. If the file is still locked after the retries, the job fails with a message naming the locked file.Template mode holds the whole workbook in memory. The template file is capped at 100 MB by default. Set the package variable sharepoint_max_template_bytes to raise or lower the cap for a job. See Using and setting variables in your packages.
When a package has more than one SharePoint destination configured with the same Site, Path, and File Name, they are treated as one workbook. Each destination contributes its own sheet, the template is downloaded once, all sheets are written, and the file is uploaded once.Use this when the recipient’s workbook needs several tabs refreshed together, for example, a blank template with lookup tabs that each come from a different source.Destinations are grouped when they use the same SharePoint connection, Site, Path, and File Name (matched case-insensitively).Requirements for every destination in the group:
Use Excel (XLSX) as the file format.
Set a distinct Sheet Name that exists in the template workbook.
Reference the same Template Workbook.
Use the same Operation Type.
The package fails to save if any of these are not met. The validation message names the other destination it conflicts with.The upload happens once, after every destination in the group has finished writing its sheet. If any destination in the group fails, no file is uploaded.
Map fields from the upstream pipeline to output columns. Each mapping has a source field and a destination column name. The destination column name is used as the CSV/Excel header and as the JSON key.
Record cap. Each job writes at most 500,000 records to the destination. Override with the package variable sharepoint_max_records.
Template size cap. The template workbook cannot exceed 100 MB (default). Override with the package variable sharepoint_max_template_bytes.
Tenant support. Only worldwide SharePoint Online tenants are supported. National cloud hosts (.us, .cn, .de) and on-premises SharePoint Server are not supported.
