ShareDo supports a number of different integration patterns, including:

• Pre-Built connectors – ShareDo provides a number of pre-built connectors to common applications. These pre-built connectors are designed to streamline the configuration of standard integrations
• REST APIs – ShareDo is designed “API first”. This means that all of its APIs are published and available for consumption by third-party applications.
• Event Triggers and workflows – when significant business events occur in ShareDo, a business event is raised. These events can then be used to trigger business functionality or workflows.
• Extensible Workflow Actions – the ShareDo workflow engine is designed to be extensible. You can create additional workflow blocks to integrate with external systems.
• External Integration engine support – ShareDo can quickly be integrated with external engines such as Microsoft Power Automate, K2 or Azure Data Factory.

Pre-Built Connectors

To streamline the integration with external systems, ShareDo provides a number of pre-built connectors that can be configured with little or no IT input. These integrations are typically configured via modeller/features.

Pre-built integrations cover common integration scenarios, such as:

• Document Management System (DMS) integrations – for systems such as iManage and O365.
• Common Vertical Integrations – for UK legal, this includes the likes of the Moj Portal and the land registry.
• Address and know-your-customer (KYC) lookups.
• Email and Calendars.

For further details, please see Global Features – Integrations within the help system.

Public APIs

ShareDo is constructed on an ‘API first’ basis. What this means in practice is that every piece of functionality that is available in the ShareDo UX is also available via a REST API. There are currently more than 400 API endpoints available for use. These endpoints enable every piece of functionality that can be performed through the UI to also be achieved through system-to-system integration.

In addition, a subset of these APIs are also made available via a versioned public API and it is typically these APIs that should be used when building external system integrations.

The /public/ moniker on the APIs indicates this and provides for clear separation between the 400+ internal APIs and the APIs meant for consumption by integrations. In addition, every API exposed from /public/ will be versioned and will provide for swagger/openApi descriptors.

These APIs are designed for easy discovery and cohesion with a general url nomenclature of:

/api/public/{area}/{version}/{resource}/{id}/{subResource}/{id}/{subResource}/{id}…. Etc

And

/api/public/{area}/{version}/{rpc}

/api/public/{area}/{version}/{resource}/{id}/{rpc}

Data can be pushed into ShareDo via the public APIs (subject to the correct security principles being held) by anyone who has knowledge of calling REST APIs via a few lines of code. That said, complex data sets may require more than a few lines of code, and hence, this could, over time, become complex.

See Calling ShareDo APIs‍.

Event Triggers & Workflows

ShareDo is based on a Complex Event Processing engine. What this means in practice is that when significant business events occur with the application, an event is raised. The events that are supported in the application can be seen within the Execution Engine Add Trigger API.

 Within this UI, you can:

• Specify the context that the event will be triggered on – this is expressed as either a work type or a work type path, e.g. for all Cases or for a specific type of Case.
• Choose the Event to be processed.
• Specifying the workflow processing logic that is to be performed on the back of the event.

Calling External Apis Via Workflow Actions

When designing a workflow to integrate with external applications, there are a number of building blocks to assist you in calling external APIs.

• REST API Block
• Javascript Block

Alternatively, for more common integrations, you may wish to create a custom workflow step - see Extending the workflow palette through custom workflow actions‍.

Integrating With External Integration Brokers Or Workflow Systems

ShareDo is commonly integrated with external workflow or integration brokers. Using the event triggers, in the same way as you can call ShareDo workflows, you can also call applications such as:

• External Workflow Systems including:
  • Microsoft Power Automate – create workflows that span disparate Microsoft applications.
  • Nintex K2 – create Enterprise workflows from within ShareDo.
• Data Integration Solutions including:
  • Azure Data Factory – ShareDo works well with integration brokers such as Azure Data Factory.

External Message Queuing solutions such as RabbitMQ or Kafka.