Integrate.io Delivers Cloud-Native SharePoint Integration:
Write Directly to SharePoint from Your Data Pipeline | March 2026

We're excited to announce a new cloud-native capability that deepens Integrate.io's integration with the Microsoft 365 ecosystem. SharePoint is now available as a write destination in the package designer.

This release enables data teams to push transformed, pipeline-processed data directly into SharePoint Online libraries and lists through a fully cloud-native, API-first connection. No on-prem gateways, no custom scripts, no middleware layers, just seamless, managed data delivery into the collaboration environment where your business teams already operate.

SharePoint as a Cloud-Native Destination

Deliver pipeline-processed data directly to SharePoint Online without leaving the cloud. The new SharePoint destination component brings fully managed, cloud-native write capabilities to the package designer, completing the bidirectional integration loop alongside its existing role as a source connector.

Legacy approaches to writing data into SharePoint have typically relied on on-prem PowerShell scripts, scheduled file drops through network shares, or bolt-on automation tools like Power Automate that sit outside the data pipeline. Each of these introduces infrastructure to maintain, credentials to manage separately, and failure points that are invisible to your pipeline's observability layer.

Integrate.io takes a fundamentally different approach. The SharePoint destination connects directly through Microsoft's Graph API, the same cloud-native API layer that powers SharePoint Online, and wraps it in the same low-code, managed experience as every other destination component on the platform. Authentication is handled through OAuth, delivery is managed end-to-end by the pipeline runtime, and every write operation is logged with the same observability you get across all other pipeline steps.

Key benefits:

• Fully cloud-native architecture: Connects through Microsoft Graph API with OAuth authentication. No on-prem gateways, no VPN tunnels, no local agents to install or maintain.

• Zero-infrastructure data delivery: Eliminate PowerShell scripts, scheduled file drops, and external automation tools. The pipeline handles authentication, formatting, and delivery as a managed service.

• Bidirectional SharePoint integration: Read from and write to SharePoint Online within the same platform, enabling true round-trip cloud data workflows.

• API-first by design: Built on Microsoft's modern Graph API rather than legacy CSOM or REST endpoints, ensuring long-term compatibility with SharePoint Online's evolving cloud infrastructure.

• Enterprise-grade observability: SharePoint writes are tracked in the same job logs and monitoring dashboards as every other pipeline step. No blind spots between transformation and delivery.

• Native package designer support: Configure the destination visually with field mapping and delivery settings in the same low-code interface used for all other components. No code, no deployment pipelines.

This is especially useful when delivering scheduled reports or enriched datasets to SharePoint document libraries without maintaining file-drop infrastructure, writing back cleansed or computed records to SharePoint lists that serve as cloud-native operational data stores, replacing legacy on-prem scripts and SSIS packages that push data to SharePoint with a fully managed cloud alternative, and closing the loop on pipelines that already ingest from SharePoint Online and need to push results back to the same environment.

Why Cloud-Native SharePoint Integration Matters

Enterprise data stacks have largely moved to the cloud, warehouses run on Snowflake, BigQuery, or Redshift, ingestion is managed through SaaS connectors, and transformation happens in cloud-hosted pipelines. But the last mile of data delivery into collaboration tools like SharePoint has stubbornly remained a patchwork of scripts, scheduled tasks, and on-prem workarounds.

This creates a gap in the modern data stack. Data is cloud-native everywhere except where business teams actually consume it. Reports get manually uploaded. Lists get updated through desktop scripts tied to a single machine. File delivery depends on infrastructure that no one wants to own but everyone relies on.

By adding SharePoint as a cloud-native destination, Integrate.io eliminates that gap. The entire workflow- ingest, transform, and deliver runs in the cloud, managed as a single pipeline, with no infrastructure outside the platform. This is consistent with how Integrate.io has approached bidirectional Salesforce sync, REST API destinations, and CDC replication: every node in the data lifecycle should be fully managed, fully observable, and fully cloud-native.

For organizations in the middle of cloud migration or actively decommissioning on-prem data infrastructure, this is particularly significant. Every PowerShell script replaced by a managed pipeline component is one less piece of legacy infrastructure to maintain, monitor, and migrate. The SharePoint destination isn't just a new feature, it's a step toward a fully cloud-native data delivery layer that matches the rest of the modern stack.

Introducing the Reworked Expression Editor 

The Expression Editor has been redesigned from the ground up to make building expressions faster and more intuitive. New copy and insert buttons let you add any expression directly, no manual typing required. Clicking any function now opens a detail panel on the right showing its full description, parameters, and usage examples, so there's no more hunting through external documentation mid-build.

A parameter legend below the syntax line makes it immediately clear which inputs are required and which are optional. Related functions are now surfaced contextually to help users discover the right tool for the job without breaking their flow. We also added a dedicated DateTimeConverter, removing the need to manually locate, input, and convert datetime fields when working with date expressions. A built-in cURL import rounds out the update, letting users pull pre-built Postman API calls directly into the editor without switching context.

Introducing NetSuite REST API Support

The ETL platform now supports NetSuite via its REST API using SuiteQL, giving users a modern, query-based alternative to the JDBC connector for accessing NetSuite data. This release also includes a JDBC driver upgrade from version 8.10.136.0 to 8.10.184.0, improving compatibility and stability for existing NetSuite JDBC connections.

Introducing the Universal OAuth Connector

The Universal OAuth Connector now supports HTTP Basic Authentication as part of the OAuth 2.0 flow, enabling connections to providers that require this handshake during token exchange. Automatic token refresh has also been implemented, so long-running pipelines no longer fail silently when access tokens expire mid-job.

Introducing the Native Shopify Source 

The native Shopify source component now supports both full load and incremental loading, with pre-defined objects aligned to the approach used by the HubSpot connector for consistency across the platform. The underlying OAuth connector issue that previously caused Shopify authentication failures has been resolved as part of this work.

New Connectors

Four new connectors ship in this release, extending the platform's reach into email, productivity, marketing, and file collaboration workflows.

• Gmail Connector: Users can now ingest CSV and Excel attachments directly from a Gmail inbox using service account authentication, with support for both full and incremental load modes and automatic metadata extraction.
• Google Sheets Connector: A new bidirectional connector lets users read from and write to Google Sheets using service account authentication, supporting both source and destination use cases within the same job.
• Constant Contact Connector: Users can now connect to Constant Contact via OAuth 2.0, fetch contact objects and email campaigns, and use dynamic field discovery during schema import.
• SharePoint as a Destination Component: SharePoint can now be used as a write destination within the Package Designer, in addition to its existing role as a source, completing the loop for teams already using SharePoint in their pipelines.

New Features

• Schedule Webhook Notifications: Users can now receive service hook notifications for schedule lifecycle events, creation, activation, and deactivation, keeping external systems in sync with job schedules automatically.
• Import cURL from Postman: The REST API source component now includes an import cURL button, allowing users to paste a cURL command directly from Postman to pre-populate the request configuration without manual re-entry.
• Save and Validate Option: A Save and Validate option has been added to the Save button dropdown in the Package Designer, allowing users to trigger validation without leaving the editing context.
• File Storage Header and Data Row Customization: Users can now specify which row contains headers and which row data begins during CSV and Excel file imports, handling files with non-standard layouts that previously required pre-processing.
• Previewer Error Detail: The Previewer now displays specific error log output instead of a generic error message, making it significantly easier to diagnose and resolve preview failures.

Improvements

• Schema preview in source components now supports up to 800 fields, up from 500, giving users a more complete view of wide tables.
• Search inputs have been added to the connections dropdown and the components list in the Package Designer, reducing navigation time when working with large connector sets.
• The SharePoint destination editor consolidates the document library and folder path into a single field, with clearer labeling and alignment with the source component layout.
• The REST API source component now auto-detects and suggests the correct JSONPath after schema load, reducing manual configuration for nested JSON responses.
• The SFTP connector now supports Ed25519 key pairs for public key authentication and has been upgraded to handle modern OpenSSH servers that require ETM (Encrypt-then-MAC) algorithms.
• The schema importer timeout has been increased from 30 to 60 seconds, reducing failures on slower or larger schemas.

What’s Coming Next on Integrate.io?

• Spark-based data processing engine
• Granular role-based access control (RBAC)
• 80+ new SaaS connectors
• Package validation improvement

All updates are rolled out. Connector availability may vary by plan. You can read more detailed information on all features that make Integrate.io a leader in data pipeline automation, which is available on Integrate.io's Documentation Page.