Requests & approvals · Service Automation Suite
An approval does not execute anything. Service Automation Suite connects forms, decisions and actions to your existing systems, through to signing and feedback.
Sound familiar?
The requester selects an unavailable item or has to re-enter information.
Service Automation Suite forms use stock from TOPdesk, for example, and show follow-up questions using your matrix, including from the SSP.
A more complete request with fewer follow-up questions.
Approval is in, but accounts, assets and activities are still waiting.
Service Automation Suite starts agreed actions, such as a group change in Microsoft Entra and a task in TOPdesk. Failures follow a configured route.
The request shows what succeeded and who handles the rest.
The agreement was sent, but you still have to chase the signature and evidence.
Service Automation Suite starts a ValidSign request, for example, and returns its status and signed document to the original request.
Request, handover and confirmation stay together.
Connecting your tools
Service Automation Suite retrieves the required data, applies your conditions and coordinates actions across people and systems. For example, from a TOPdesk SSP to Microsoft Entra, asset records or ValidSign.
Not a solution only its builder understands. Together, we define data relationships, mappings and rules for reuse in future processes. We agree who tests and maintains them so a colleague can take over.
Your process leads
Other tools? We review the capabilities, APIs and permissions in your environment. Your existing systems remain where you work.
From plan to delivery
The integration is one part. The surrounding agreements make it work.
A form collects a request but does not automatically arrange execution. We connect approval to the right system action, task or signature and define which confirmation is needed to complete it.
We agree upfront which step waits, who supplies the information and when to check again. Service Automation Suite follows the configured route without silently bypassing a required approval.
Arts en Zorg Groep
Arts en Zorg Groep automates joiner, mover and leaver processes from AFAS to TOPdesk, centrally managing accounts, access and assets.
Read the customer storyFrom HR change to accounts, access and assets.
Interstellar
Interstellar uses Service Automation Suite as a process layer between TOPdesk time tracking and financial processing in a growing MSP organisation.
Read the customer storyTime records connected to financial processing.
Start with what is stuck today
Bring your form or request workflow. We will look at the questions, checks and next actions that actually complete the process.
From question to execution
Changes consist of separate tasks, emails and scripts, leaving gaps in visibility and follow-up.
Service Automation Suite combines intake, workflow, system actions, collaboration and evidence.
Predictable execution, fewer handovers and better control.
Employees book in Outlook, for example, while facilities manages rooms in another system. Changes and cancellations need to reach that system too.
Use Service Automation Suite to connect Outlook to Reservations Management in TOPdesk, for example. Configure how bookings, changes and cancellations are processed and which facilities actions are required. For another combination, the available interfaces determine which exchanges are possible.
Employees keep their familiar calendar and facilities continues in its existing management environment. Configured feedback shows whether the booking was processed or still needs follow-up.
Manage MSP customer onboarding, service delivery, changes, billing and offboarding as one lifecycle.
New customers bring tenants, services, assets, contracts and exceptions that would otherwise need to be configured again for each customer.
Status, ownership and audit records remain visible from customer onboarding to controlled termination.
Make execution across customer and supplier chains verifiable without manually collecting evidence.
MSP processes span multiple customer environments and suppliers, scattering logs and evidence.
Evidence is generated as part of the process, rather than as a separate project afterwards.
A request or handover needs a signature. Separate emails make status and evidence hard to find.
Have Service Automation Suite start a signing request with ValidSign, for example, from your existing request workflow, such as TOPdesk. Process feedback and attach the signed document to the agreed record.
Request, signature and evidence stay together. Signers, document routing, permissions and error handling are configured together.
Your process leads. The tools can vary. We configure connections around the capabilities and permissions in your environment.
Explore all integration examplesOne foundation. More possibilities.
Requests, decisions and actual execution belong together, including when someone needs to supply information or take a different route.
Use Service Automation Suite forms from a TOPdesk SSP, for example, or from another request environment. Use Service Automation Suite to combine the request with system data and let the configured matrix determine additional questions and activities. Return execution and outcomes to the original request.
Use Service Automation Suite to read assets and stock from TOPdesk, for example, and filter by type, location or availability. If you use another source, configure data exchange accordingly. The selected option can become part of handover, signing and registration without re-entry.
Define conditions, owners and approvals. Deviations receive appropriate review rather than silently following the standard route.
Start activities, data changes or signing through the configured workflow. Keep manual tasks part of the process too.
Retain which person selected which asset and which request the action belongs to. Reuse those relationships for delivery, signing and administration.
Sending a command or offering a document is not the same as execution. Let confirmed outcomes determine the next step and keep rejections and failures visible.
Relationships, mappings and process agreements have a recognisable place in the same environment. Colleagues can follow configuration and processing without first reconstructing the original builder’s personal approach.
Your process keeps evolving after go-live. Handle an extra field, changed owner, new exception or small workflow change from the same foundation: adjust it, review the impact, test it and track processing. Agree who manages it, who reviews changes and when our support is needed.
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.
A request awaits a ValidSign signature. Declining, expiry and technical failure each need different handling.
Additional access is approved for a limited period. A checkbox alone does not preserve why, for whom and until when.
Procurement, a supplier and technical inventory each hold part of the picture. A delivered asset is not automatically assigned to its correct owner.
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 approachNeed 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.
