Customer & work data

Microsoft SQL Server

Use available data from a local SQL Server for validation, enrichment or a service action. Service Automation Suite Agent technology can connect local and cloud processes; access and configuration depend on your environment.

From product to process

How to use the integration

Database → process

Use permitted database fields to enrich or validate records in other applications.

Keep people records current

Synchronise agreed person and organisation fields between the relevant applications.

Exceptions → tasks

Route missing information or discrepancies to the team responsible for follow-up.

Combine into one controlled process

Data → rules → execution

Combine
Customer or issue + service request + rules
Determine & check
Combine data and determine the next action
Execute & report back
Start onboarding or a work task · Notify team · Return outcome

Check sources and rules, test changes and track the outcome. Manual tasks get an owner and confirmation.

Build visually. Manage easily.

Reuse building blocks, adapt your process and test the change. Manage it yourself, together with us or let Scope4mation take care of it.

More process examples & technical details

The work between your applications

Data transferred.
But is the work complete?

Service Automation Suite connects Microsoft SQL Server with your other applications, people and rules. Keep data aligned, work moving and outstanding actions visible.

A change, request or alert

Service Automation Suite

Data, people, assets and relationships on one foundation.

Compare: What exists? What should exist?
Determine what is needed: Matrix · policy · legal requirements
Coordinate the next steps: Checks · tasks · approvals · actions

Execution ↔ feedback

Your people and tools

Microsoft SQL Server

For example. Also with other teams, suppliers and applications.

Verify. Inform. Report.

What is complete? Who needs to act? Which exception needs attention?

Start with one integration, register or check. Build on the same data and rules.

Align data

Local data. Still part of the same process.

Service Automation Suite · Central coordination

Combine data and apply rules

Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.

Information & trigger

Microsoft SQL Server

Relevant data or workflow status

Follow-up & feedback

Update, execute and record outcomes

Local data as a source
Identify the relevant SQL Server data and the access permitted for it.
Map into the process
Use the data to validate or enrich a service record or start an agreed action.
Check the outcome
Record what was done and surface errors or exceptions for the operator.

Coordinate actions

Turn a decision into completed work.

Connect a request or discrepancy to a workable process. Let people decide where needed and systems execute the agreed actions.

Service Automation Suite · Central coordination

Combine data and apply rules

Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.

Information & trigger

Microsoft SQL Server

Relevant data or workflow status

Follow-up & feedback

Update, execute and record outcomes

Define the starting point
Choose the request, change or discrepancy that needs follow-up and who decides.
Connect people and systems
Coordinate approvals, manual tasks and available system actions.
Record the result
Record which steps are complete and where someone still needs to act.

Under the hood

How to connect, test and manage the integration.

For administrators who want to understand how it works: connect Microsoft SQL Server to your other applications, map the data and use the response in the next step. Configure it centrally in Service Automation Suite.

Example configuration · shaped by your process

Synchronise data and return the outcome

Connect and test
API Composer
Choose the API method, URL and authentication. Manage the host and credentials in an environment. Test a request in Discovery and inspect the fields actually returned by the API.
Combine and compare
Data Flow Composer
Select fields, translate codes and relate records using shared data. Compare source and target to identify new, changed or incomplete records.
Execute and use the response
API Composer
Build the request body from validated data and inspect Body Preview before testing. Use the result ID in Data Context for the next request or save output to an entity. Configure write-back separately.
Recognise errors and follow up deliberately
API Composer
Configure error rules by HTTP code and/or message. A temporary API failure can use bounded retries. A missing relationship or rejection needs another route: record the cause and configure a verification task for the appropriate team, for example.

Which data do you maintain?

An example configuration, not fixed field names or a mandatory combination.

Source ID and external reference: Retain verified relationships between records and reuse them across integrations.
Fields, codes and required data: Select the required data, translate values and enrich from shared tables. Route uncertain matches for review.
Result reference and processing status: Use the available response for feedback and agreed follow-up actions.

Sent ≠ processed. Use the response and agreed validation to determine the next step.

Need to publish data yourself?

Use Endpoint Composer to publish a configured Service Automation Suite data object. Choose read and write methods and security profiles so a customer can retrieve agreed service data or a supplier can submit information, for example. Configure data selection and subsequent processing separately.

Endpoint Composer

From data to a complete process?

Combine the integration with a form, a shared matrix, a review or collaboration between service teams. For example, an approved request leads to execution in Microsoft Entra, a ValidSign signature request and feedback in TOPdesk. Your process determines the steps needed; not every use case requires all these components.

Explore the connected building blocks

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.

Time recorded, but not yet accounted for.

Service work is complete but time entries do not match a known customer, project code or agreed processing route.

Combine: Combine time entries with central customer and project relationships and accounting rules. Request specific missing information.
The outcome determines what follows: Accepted: retain the accounting reference. Rejected: have the owner correct the cause. Resending an entry requires checking whether it was already processed.
The benefit: Less investigation and correction between service and finance without automatically treating errors as billable work.

A different name does not mean a new record.

A person or organisation has a different name in the source than at a customer or supplier. Matching text again can create incorrect or duplicate relationships.

Combine: Retain verified identifiers and source rules in a shared table. Reuse the relationship for requests, tickets and other integrations.
The outcome determines what follows: Known key: use the relationship. Multiple candidates or a missing identifier: request review. Once confirmed, reuse the established relationship.
The benefit: A consistent data foundation managed by your team instead of investigated again for every connection.

Refreshing a report does not guarantee reliable data.

A source request can succeed while data is missing, differently coded or not yet fully retrieved.

Combine: Combine pagination and output mapping with agreed data checks. Use shared relationship tables to connect sources.
The outcome determines what follows: Checks passed: prepare the dataset. Deviation: request review and expose freshness. Temporary API failures follow a bounded recovery path.
The benefit: A clearer distinction between a technically successful import and information fit for decision-making.

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.

From product to workflow