Article published on the 25th of March 2026.
Contents
1. Introduction
WorkPoint 365 is built natively on Microsoft SharePoint and is deeply integrated into the Microsoft 365 ecosystem. This foundation makes it a natural hub for connecting business processes, documents, and data with other Microsoft services such as Teams, Outlook, Power Automate, and Azure — as well as with external systems.
WorkPoint supports integration through several well-established APIs, including the WorkPoint 365 API, SharePoint’s native APIs, and the Microsoft Graph API. Together, these provide a flexible toolbox for building everything from simple automations to enterprise-scale, event-driven integrations. But it is worth pointing out that we strongly suggest using the WorkPoint API when creating or modifying data in a WorkPoint solution.
This article serves as a starting point for partners, developers, and architects who want to understand how and when to integrate with WorkPoint 365.
Rather than focusing on detailed implementation steps, it introduces common integration scenarios, available APIs, and recommended architectural patterns. Combined with the right middleware — such as Power Automate, Logic Apps, or Azure Functions — these capabilities enable powerful, secure, and scalable integrations across your digital workplace.
2. Common use cases and scenarios
There are many ways to leverage the connectivity offered by WorkPoint 365 and Microsoft 365.
In this article we will describe some of the use cases and in broad terms how to do it.
Integrating 3rd party data in user processes
Scenario
Automatically enrich customer data during creation using an external registry.
Components involved
- External REST API (CVR registry)
- WorkPoint Automate
- Endpoint data binding
Why this works well
- Reduces manual input
- Improves data quality
- Keeps the user in a guided process
Learn more
WorkPoint Automate - Endpoint data binding
Integrating digital signature providers
Scenario
Digitally signing documents is a common requirement in document and case management solutions.
Many organizations rely on external signing providers such as Visma Addo, DocuSign, Adobe Sign, Penneo, and similar services to handle legally binding signatures.
In a typical WorkPoint 365 solution, users initiate a signing process directly from WorkPoint, select one or more documents, and provide the required signing details.
The documents are then sent to the external signing provider, and the signed versions are returned and stored back in WorkPoint as part of the business process.
Typical components involved
A standard integration with a signing provider usually consists of the following components:
- WorkPoint 365 as the system where documents, metadata, and business context are managed
- WorkPoint Automate to guide users through the signing process and collect required input
- External signing provider API to create signing requests, track status, and retrieve signed documents
- Middleware (such as Power Automate, Logic Apps, or Azure Functions) to orchestrate communication between WorkPoint and the signing provider
Although signing providers expose different APIs, they often follow similar design patterns, making it possible to reuse architectural approaches across providers.
Why this approach works well
This integration pattern allows organizations to keep users in a familiar WorkPoint experience while leveraging best‑of‑breed signing services.
By using WorkPoint Automate, signing processes can be tailored to customer‑specific requirements, including:
- Custom input forms for collecting signing details
- Support for multiple documents and signers
- Validation and enrichment of data before sending documents for signing
At the same time, the API‑based approach ensures flexibility, making it possible to switch signing providers or support multiple providers without redesigning core WorkPoint processes.
Integrating Microsoft 365 Services via the Graph API
The Microsoft Graph API is the unified gateway to the Microsoft 365 ecosystem. By integrating it with WorkPoint 365, you transcend simple document management and unlock a vast range of cross-platform automation and data-sharing possibilities.
Think of the Graph as the "connective tissue" that allows WorkPoint to talk directly to Teams, Outlook, SharePoint, and beyond. Instead of jumping between applications, you can trigger actions across the entire cloud suite from within a single WorkPoint process.
Why Integrate with Microsoft Graph?
- Unified Data Access: Access your organization's entire "Data Fabric" using a single set of credentials and one consistent API structure.
- Real-Time Collaboration: Automatically sync WorkPoint entities with Microsoft Planner tasks or Teams channels to keep your team aligned.
- Intelligence at Scale: Leverage the Graph to feed your data into AI models, enabling automated email drafting or intelligent document summaries.
We recommend starting with the Microsoft Graph Explorer to discover the full range of available endpoints.
Explore our latest use cases:
Learn how to connect entities to Microsoft Planner - Creating Planner Plans for Entities or see how we use Graph endpoints to process email content with AI - Send an e-mail reply suggested by AI.
3. Working with the WorkPoint 365 API
WorkPoint 365 provides a powerful and flexible Web API that enables organizations to integrate WorkPoint functionality into their own systems and workflows. The API supports a wide range of operations, making it ideal for both developers and business users looking to automate processes or extend platform capabilities.
We strongly recommend utilizing the WorkPoint API for all CRUD operations (create, update, delete) on items and entities. This ensures optimal request scheduling to prevent tenant throttling, while automatically triggering essential background processes—such as security replication, inheritance, and data aggregation—to maintain system integrity.
Key Capabilities
With the WorkPoint 365 API, users can:
- Manage Business Modules and Entities: Create, update, and retrieve data from business modules like projects, cases, or contracts.
- Automate Document Handling: Upload, tag, and retrieve documents, manage metadata, and control document lifecycle events.
- Manage sites and site collections: See how many site collections are available, as well as create sites and register site collections.
- Work on documents: Create, convert and edit PDF files, create and copy documents.
- Manage items in lists: Create, edit and delete items in lists as well as change stage in entities.
Common Use Cases
Here are some typical scenarios where the WorkPoint 365 API is used:
- CRM Integration: Synchronize customer data between WorkPoint and external CRM systems like Dynamics 365 or Salesforce.
- Project Automation: Automatically create project sites and assign roles when a new opportunity is won in a sales system.
- Document Synchronization: Keep documents in sync between WorkPoint and external file storage systems such as SharePoint Online or OneDrive.
- Custom Dashboards: Build dashboards that pull real-time data from WorkPoint for reporting or operational monitoring.
- Compliance Workflows: Trigger document retention or approval workflows based on metadata or lifecycle events.
- Mobile App Extensions: Enable mobile apps to interact with WorkPoint data for field workers or remote teams.
- Third-Party Notifications: Use webhooks to notify external systems (e.g., Teams, Slack, or ERP platforms) when key events occur in WorkPoint.
Authentication and Access
Access to the API requires proper authentication using either delegated or application permissions.
Admins can configure access through Azure Active Directory to ensure secure and compliant integration.
You can read more about setting up authentication here: Creating Application Registration for Authentication
Getting Started
To explore the API and test endpoints, visit the WorkPoint 365 Swagger UI, which provides interactive documentation and sample requests.
It is also highly recommended to also take a look at our Postman project, where there is additional documentation and examples of how to authenticate and use the API.
Choosing the right middleware
When integrating SaaS solutions, middleware often plays a crucial role in facilitating and orchestrating the exchange of data between systems. Choosing the right tool depends on several factors—who will implement the
integration, the complexity of the workflow, and especially the volume and scale of data being transferred.
While there are many purpose-built integration platforms available, WorkPoint 365’s deep integration with the Microsoft ecosystem makes three platforms particularly effective for building connections with other SaaS
solutions:
Power Automate,Logic Apps, and Azure Functions. These tools offer fast, flexible, and scalable options tailored to different integration needs and skill levels.
4. Integration at scale - Azure Event Grid Integration
As your WorkPoint 365 solution grows, so does the need to sync data with external systems like ERPs or custom databases.
While standard triggers work for simple tasks, enterprise-scale integration requires the WorkPoint Event Bus—a decoupled, event-driven bridge to the Microsoft Azure ecosystem.
Why Use an Event-Driven Architecture?
Rather than forcing WorkPoint to wait for an external system to respond, the Event Bus "announces" changes (like a new project or an updated entity) and moves on. This offloads the heavy lifting to Azure Event Grid, which acts as your central traffic controller.
By routing WorkPoint events through Azure, you gain:
- Performance and scalability: The Azure Event grid can scale to millions of events without taxing the WorkPoint solution, and a single event can be fanned out to many receivers.
- Reliability: Built-in retry policies and "dead-lettering" ensure data is never lost, even if a receiving system is offline, the event will still be waiting when the receiving system is back online.
- Flexibility: Easily route data to multiple "subscribers" simultaneously—such as Logic Apps, Power Automate, or custom Webhooks.
You can read more about how to configure the WorkPoint Event Bus feature here, or take a look at the Project Dashboard case study from the 2024 Partner Day presentation: WorkPoint Event Bus: Partner Day Demonstration
Comments
0 comments
Please sign in to leave a comment.