Read local CSV files and connect their data to your other applications. Turn a periodic export into a controlled handover, matching records and following up discrepancies.
The work between your applications
Data transferred. But is the work complete?
Service Automation Suite connects CSV-bestanden 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
CSV-bestanden
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.
Local execution within the same workflow
Source → rules → execution
Combine
A local CSV export
Determine & check
Selection, permissions, keys and allowed action
Execute & report back
Execute locally · Process results · Follow up discrepancies
Scenarios in practice
What would you like to do with CSV-bestanden?
Choose a use case and explore the related workflow steps.
Agree when the file is complete. Configure the directory and separator and select the required columns.
Connect execution
Use Data Link to process rows by a stable unique key. Configure field mapping and the agreed next action for the selected application.
Verify the result
Check empty files, missing keys and duplicates before writes. Missing source rows must not automatically trigger deletions.
Connected follow-up
PowerShell and CSV as one clear route.
A LocalScripting action produces the export. CSV Reader and Data Link perform the agreed import. Connect export failures and processing outcomes to the same follow-up.
Service Automation Suite · Central coordination
Selection, validation and feedback
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Agree when the file is complete. Configure the directory and separator and select the required columns.
Connect execution
Use Data Link to process rows by a stable unique key. Configure field mapping and the agreed next action for the selected application.
Verify the result
Check empty files, missing keys and duplicates before writes. Missing source rows must not automatically trigger deletions.
Connect work across your applications
What would you like to connect CSV-bestanden with?
Choose the role in your workflow. Explore applications from the scenarios and further directions to discuss together. We define the data, actions and available interface for each combination.
Why connect CSV-bestanden with Service Automation Suite and Scope4mation?
Get more from CSV-bestanden and the applications you already use. Our Dutch technology and process expertise connect the whole chain. Stay in control of your data, configuration and how you build further.
Service Automation Suite + Scope4mation
Process & control
One process, your own applications
Use the data you already maintain. Service Automation Suite connects requests, decisions and execution across HR, IT, facilities and suppliers. Reduce retyping and chasing separate tasks.
Who has what — and why?
Compare what someone has with what your rules require and permit. Connect discrepancies to review, action and verification of the outcome.
Share data with a purpose
Which data goes where, for what purpose and who may access it? Incorporate your classification and security requirements into the configuration of each data flow.
Autonomy & choice
Your process shapes the chain
Combine the applications that fit your organisation. Connect data and workflow steps across suppliers, so one application does not dictate your entire way of working.
Developed and supported from the Netherlands
Service Automation Suite is our own technology. At Scope4mation, you work with the people who develop the platform and help configure workflows. Discuss your needs and next steps directly with us.
Keep your options for tomorrow
Keep configuration and process knowledge transferable. When things change, we assess what can be reused, what needs adapting and how to hand over data and operations.
Build & operate together
A toolbox to keep building
Connect your applications using visual building blocks. Start with one use case and reuse connections, data and actions for the next. Build yourself, learn together and expand deliberately.
Process expertise and technical delivery
We help work through the whole process: from the current and desired state to configuration, exceptions and handover. Combining your practical knowledge with our integration and process experience.
Operate it your way
Self-Managed, Co-Hosted or Managed: operate it yourself, together, or entrust the agreed operations to us. Clarify services, maintenance, costs and expansion upfront.
Under the hood
The local interface, permissions and results.
A local CSV export
Agree when the file is complete. Configure the directory and separator and select the required columns.
Use Data Link to process rows by a stable unique key. Configure field mapping and the agreed next action for the selected application.
Check empty files, missing keys and duplicates before writes. Missing source rows must not automatically trigger deletions.
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.
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
CSV-bestanden in your workflow
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.
