Skip to content
Talk to us+31 318 894 615
Service Automation SuiteService Automation Suite

Integration · automation · orchestration

Integrations

Connect your applications. Take care of the work between them. We combine data, actions and process agreements. Start with one bottleneck and build further together using reusable components.

Explore the possibilities
Explore what is possible.
Clear filters

24 platforms

TOPdeskTOPdesk

TOPdesk

Current data, tasks and feedback across departments.

Service & suppliersAssets & cloud
12 combinations with TOPdesk
AFASAFAS

AFAS

An HR change. Access, assets and service move with it.

Finance & projectsHR
9 combinations with AFAS
ProgressProgress

Progress

Connect student and education processes with service.

Education & students
Google WorkspaceGoogle Workspace

Google Workspace

A new colleague, scattered account lists.

Workplace & access
DocusignDocusign

Docusign

The contract is signed. The work has not started.

Documents & signing
MicrosoftMicrosoft DefenderMicrosoft Defender

Microsoft Defender

A security alert. With the right follow-up.

Monitoring
Jira Service Management by AtlassianJira Service Management

Jira Service Management

Service requests in Jira Service Management. Connected follow-up.

Service & suppliers
Matrix42Matrix42

Matrix42

Service work in Matrix42, connected to your other teams.

Service & suppliers
MicrosoftMicrosoft SharePointMicrosoft SharePoint

Microsoft SharePoint

SharePoint documents and lists, connected to your workflow.

Documents & signing

No starting from scratch for the next integration.

Reusable components, configured around your agreements. We agree together how management and maintenance are organised.

  1. Configure togetherAgree sources, data and responsibilities.
  2. Build furtherReuse matching rules and agreements.
  3. Stay in controlReturn outcomes and follow up exceptions.
What is already available?

This directory shows applications and possible use cases. For each combination, we assess available interfaces, existing components and your environment. You know what can be reused and what still needs configuring together.

Build visually. Connect smartly.

From idea to working integration.

Retrieve data, combine what you need and follow up with the right action. API Composer and Data Flow Composer work together in one platform. Build step by step, with our help to get started.

Process example · HR → TOPdesk

New colleague? Data in the right place.

From fictitious HR data to a person in TOPdesk: select, link the department and prepare the data for use.

  1. API Composer Retrieve

    Read employee data from the HR system through an API.

  2. Data Flow Composer Select & combine

    Select fields and combine HR data with departments from TOPdesk.

  3. Data Flow Composer Prepare

    Map fields and prepare the values TOPdesk expects.

  4. API Composer Execute & check

    Use the result to create a person in TOPdesk and review the response.

API ComposerConfigure your API request and test the result.
API Composer: Configure your API request and test the result.
Data Flow ComposerSelect fields and add the value for the linked department.
Data Flow Composer: Select fields and add the value for the linked department.

Actual product screens from our course, using fictitious training data. Click to enlarge. Configuration and available APIs determine what your integration can do.

Build & combine

Use existing components as a foundation for your next integration.

Learn & build

A consistent way to retrieve, process and execute, with guidance from Scope4mation.

Hand it over

Give components and steps clear names so a colleague can follow the structure and take over.

Something changed? Adapt.

Adapt your integration, test the result and keep building. Let your process grow with your needs.

Beyond the first integration.

Use the same data and rules in your next process.

Start with one use case. Connect customer, employee and asset data, for example, and agree which source is authoritative. Reuse those relationships, a matrix where needed and configured actions in the next workflow. Agree who maintains the data and rules. Expand without repeatedly connecting and maintaining the same information.

Supplier finished. Is the internal work complete?

A supplier closes its ticket while internal verification or user confirmation is still missing.

Combine
Relate both tickets and the affected service. Use external completion to trigger a check, not automatically close the internal ticket.
The outcome determines what follows
Confirmed: complete internally. Rejected: return the reason and request correction. No response: assign follow-up to the agreed group.
The benefit
Fewer prematurely closed tickets and clear ownership of the next action.
Signature declined. Keep the process moving.

A request awaits a ValidSign signature. Declining, expiry and technical failure each need different handling.

Combine
Link the request, signing request and document. Read the available status and apply agreed conditions to determine the next action.
The outcome determines what follows
Signed: process the document and confirm the activity. Declined: route the reason to the owner. Temporary technical failure: retry only under the configured error rule.
The benefit
Appropriate follow-up for each outcome without counting a sent signing request as completed work.
Ordered, delivered and actually in use?

Procurement, a supplier and technical inventory each hold part of the picture. A delivered asset is not automatically assigned to its correct owner.

Combine
Compare orders, delivery details, serial numbers and inventory with central ownership relationships. Keep missing confirmations part of the workflow.
The outcome determines what follows
Matching data: update the agreed records. Unknown device, unexpected owner or unconfirmed delivery: create work for the correct support group.
The benefit
Fewer gaps between administrative and technical records and targeted follow-up of discrepancies.

Your process needs more than a standard action?

Configure the missing API request, input and output in API Composer. Use its response in the next step and combine it with data tables, forms and automations. Extend the same product and reuse the configured building blocks.

Use Service Automation Suite to update a ticket in TOPdesk, for example, with fields available through its API, such as category, priority, status and support group. For another application, configure its request and field mapping. The outcome determines the next action: confirm, add information or request review, not merely check whether the request arrived.

Build it yourself: explore the technical approach

Need to publish data or let others submit it? Endpoint Composer exposes a configured Service Automation Suite data object with selected methods and security profiles. Other building blocks handle subsequent processing.

A conversation with coffee and tea on the table
Scope4mation

Pull up a chair. Or join us online.

Over coffee, tea or online: tell us what you are working on.

We can help with the integrations, automation and coordination your process needs, even if your application is not listed yet.

SasjaHello.How can I help you today?