Across teams and systems
Connect HR, IT, facilities, finance and suppliers through shared data and rules. Your process shapes the setup.
All integrations
Integration · Service Automation Suite
Connect TOPdesk to HR, identity, monitoring and suppliers. Coordinate tickets, equipment and employee workflows with controlled execution.
Continuity, experience & maintenance
Why Service Automation Suite alongside TOPdesk?
TOPdesk’s own integration capabilities can be a good fit. Service Automation Suite and Scope4mation help configure the complete workflow and keep it running, with agreed execution, checks and maintenance.
Process & coordination
Execution and confirmation
Define who acts, which approval is needed and when a step is complete. Keep exceptions and feedback with the same process.
Together with Scope4mation
Use our integration and process experience. We configure the workflow for your applications, available APIs, modules and permissions.
Continuity & costs
Maintenance is part of the solution
APIs, permissions and processes change. Agree who tests changes, resolves failures and verifies operation.
Keep knowledge transferable
Document source rules, configuration and operations so a colleague can take over and continuity does not depend on one builder.
Compare the whole lifecycle
An included connector does not make configuration, testing, operations and handover free. With a self-built solution you organise these yourself; with us you agree the support required.
Data & dependencies
Know where your data goes
Document hosting, processing, support access and involved suppliers. Explicitly assess processing or access outside the EU. The country of establishment alone does not tell the whole story.
Retain control through change
Agree ownership, documentation, export and handover. Service Automation Suite adds a central configuration, so define our role and maintenance responsibilities clearly too.
More from your existing applications.
Get more from TOPdesk.
Across departments.
TOPdesk as the central place for your service delivery. Service Automation Suite automatically keeps people, assets and relationships up to date and connects your other applications to the work in TOPdesk. Less retyping, comparing and chasing. More from the tools you already have.
It does not stop at one import or integration. Start small, but connect the pieces properly: shared data, rules and checks that your next process can build on.
Executed and evidenced.
Record decisions, tasks and confirmed results against the right TOPdesk record. Make the configured process traceable, including for audits. See what is complete and which exception still needs action.
Combine into one controlled process
Data → rules → execution-
Combine
TOPdesk request + HR + equipment
-
Determine & check
Profiles, rules and approval determine the route
-
Execute & report back
Entra account action · Equipment handover · Signing · Report back to the request
View the complete onboarding example
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.
People & organisations
The right data with every ticket.
A change in HR or business administration should carry through to the people and organisations your service team works with. Without retyping or maintaining separate spreadsheets.
What Service Automation Suite coordinates centrally
Service Automation Suite recognises relationships across systems, combines data with a central register and applies agreed source rules. Incomplete or conflicting data calls for review, not blind overwriting.
What this enables
Your team works with current people and company records. The same context can be reused for requests, changes and employee processes.
For example, in your setup
From AFAS to TOPdeskKeep people and companies current in TOPdesk.
Use AFAS as the source for people, branches or companies in TOPdesk. Service Automation Suite matches relationships and updates agreed fields, giving tickets and requests the right context.
Read the right source data
Read relevant people and organisation data from AFAS. Use agreed identifiers to match the same relationships.
Update TOPdesk selectively
Create missing records and update changed fields and relationships. Data managed elsewhere stays with its authoritative source.
Build on that context
Use current person and organisation data in service requests, changes and employee lifecycle workflows. Data sync is the foundation; workflow execution is the next step.
From Youforce to TOPdeskKeep people and companies current in TOPdesk.
Use Youforce as the source for people, branches or companies in TOPdesk. Service Automation Suite matches relationships and updates agreed fields, giving tickets and requests the right context.
Read the right source data
Read relevant people and organisation data from Youforce. Use agreed identifiers to match the same relationships.
Update TOPdesk selectively
Create missing records and update changed fields and relationships. Data managed elsewhere stays with its authoritative source.
Build on that context
Use current person and organisation data in service requests, changes and employee lifecycle workflows. Data sync is the foundation; workflow execution is the next step.
Assets & ownership
Not just populated. Verified too.
A technical inventory tells you what a management tool sees. Asset management also needs to know what was ordered, delivered, assigned or returned.
What Service Automation Suite coordinates centrally
Service Automation Suite combines supplier and asset registers with observations from management tools. You define the authoritative source for each field. Differences receive an owner and a follow-up action.
What this enables
Records you can build on for handover, returns, replacement and actual-use checks. A device that disappears from inventory has not necessarily been returned.
For example, in your setup
Assets from IntuneAsset Management uses current inventory.
Connect inventory from Microsoft Intune to TOPdesk Asset Management. Service Automation Suite matches devices and relationships, maps attributes and keeps agreed records current.
Select relevant inventory
Use available device attributes and the agreed scope. Define the authoritative source for each field.
Match and update
Avoid duplicate assets, update changed fields and connect the right people to their assets.
Connect records to follow-up
Connect missing data, a changed owner or an employee departure to tasks, changes or asset returns.
Assets from SCCMAsset Management uses current inventory.
Connect inventory from Microsoft SCCM to TOPdesk Asset Management. Service Automation Suite matches devices and relationships, maps attributes and keeps agreed records current.
Select relevant inventory
Use available device attributes and the agreed scope. Define the authoritative source for each field.
Match and update
Avoid duplicate assets, update changed fields and connect the right people to their assets.
Connect records to follow-up
Connect missing data, a changed owner or an employee departure to tasks, changes or asset returns.
Configuration Management → Asset Management
From configuration management to asset management. Without a big bang.
With a phased setup in Service Automation Suite, you do not need to convert all legacy configuration items at once. Keep them and their links to tickets, and create new assets that refer to the original item.
We also link the new assets to person cards and other relevant records, such as locations and related assets. Preserve these connections as you migrate step by step.
What Service Automation Suite coordinates centrally
Move with control:
- Retain the original context. The new asset references the old CI; existing ticket relationships are retained.
- Keep names recognisable. Old label: “LAP-042 (legacy)”. New asset: “LAP-042”.
- Map item types. Map CI types to clear asset types and organise sprawling records.
- Clean up fields. Retain useful fields. First check which integrations depend on them.
- Align integrations. Align imports and follow-up actions with the new setup.
What this enables
Build the new asset register while retaining the original context. Compare, verify and approve each selection, reducing dependence on one major cutover. This reduces the risk of losing connections between tickets, relationships and ongoing workflows.
For example, in your setup
TOPdesk migrationKeep the old item. Build the new asset alongside it.
This example describes a Service Automation Suite setup alongside the legacy register, rather than the native TOPdesk migration wizard. Start with one object type or a limited selection. The reference between old and new means existing ticket relationships do not all need to be reassigned at once. Agree any additional history and attachments to transfer for each environment.
Map data and relationships
Map existing configuration item types to the new asset types. Identify required fields, people, relationships and ticket references. Omit unused fields from the new model after checking integration dependencies. Original information can remain with the old item.
Link the new asset to the old item
Create the new asset with the agreed data and a reference to the original configuration item. Also link the new asset to the correct person cards and other relevant records, such as locations and related assets.
Agree which relationships to transfer or recreate and verify them. Retain the old item and its existing ticket relationships.
Keep names recognisable
For example, rename the old label “LAP-042” to “LAP-042 (legacy)” and name the new asset “LAP-042”. Change the display label, not the identity of the old item. Check references before processing the next selection.
Check your integrations too
Compare counts, content and relationships. Test adapted imports and follow-up actions. Agree the cutover point and fallback plan, and have the responsible owner approve the transition.
Employees & access
The employee journey crosses departments.
A new colleague needs more than an account. Assets, service activities and HR administration must align across onboarding, role changes and offboarding.
What Service Automation Suite coordinates centrally
Use a matrix in Service Automation Suite to relate roles to access, assets and tasks, for example. Service Automation Suite combines those rules with current HR and TOPdesk data. Agree who maintains the matrix, then connect questions, approvals and execution in TOPdesk, IAM and other systems.
What this enables
Access, assets and tasks move with the employee. Results return to the record and, where agreed, to HR. Exceptions remain visible until followed up.
For example, in your setup
Onboarding with a matrix and formsThe right questions and activities for this employee.
Use role, department, location and start date to determine the workflow. Reuse what is already known and ask specifically for what is missing.
Combine and determine
Combine HR and TOPdesk data with your matrix for access, assets and work. Determine the questions and activities relevant to this situation.
Add what is needed automatically
Offer additional questions through a form. Let new information add or update the required activities instead of manually rebuilding the entire onboarding workflow.
Execute and report back
Execute account, asset and service tasks through the configured workflow. Record status and results in TOPdesk and agreed HR records; exceptions remain part of the same process.
OnboardingFrom employee change to a complete start.
Service Automation Suite connects IAM to the wider employee workflow. Use a matrix in Service Automation Suite to relate roles to access, assets and tasks, for example. Combine those rules with current HR and TOPdesk data and agree who maintains the matrix. This determines the changes and actions needed.
Combine available information
Use the HR change and current person, access and asset data. Forms or reviews supply missing information and exceptions.
Let the matrix define the route
Service Automation Suite applies role profiles, conditions and effective dates. Start or update the TOPdesk change with appropriate activities for HR, IT and facilities.
Execute, confirm and update
Connect account and group actions to asset handover and confirmation. Include ValidSign signing and file storage where needed. Return outcomes to the activities.
Complete the loop with HR
Once the account is created, write agreed account data or status back to AFAS or the chosen HR source. The TOPdesk activity receives the same outcome. HR and IT no longer need to copy or chase confirmation separately.
Role changeA different role. An appropriate new setup.
Service Automation Suite connects IAM to the wider employee workflow. Use a matrix in Service Automation Suite to relate roles to access, assets and tasks, for example. Combine those rules with current HR and TOPdesk data and agree who maintains the matrix. This determines the changes and actions needed.
Combine available information
Use the HR change and current person, access and asset data. Forms or reviews supply missing information and exceptions.
Let the matrix define the route
Service Automation Suite applies role profiles, conditions and effective dates. Start or update the TOPdesk change with appropriate activities for HR, IT and facilities.
Execute, confirm and update
Connect account and group actions to asset handover and confirmation. Include ValidSign signing and file storage where needed. Return outcomes to the activities.
Complete the loop with HR
Return confirmed changes or revocations to TOPdesk activities and, where agreed, the HR source. Employee records, execution and follow-up stay aligned.
OffboardingDeparture known. Access and assets follow through.
Service Automation Suite connects IAM to the wider employee workflow. Use a matrix in Service Automation Suite to relate roles to access, assets and tasks, for example. Combine those rules with current HR and TOPdesk data and agree who maintains the matrix. This determines the changes and actions needed.
Combine available information
Use the HR change and current person, access and asset data. Forms or reviews supply missing information and exceptions.
Let the matrix define the route
Service Automation Suite applies role profiles, conditions and effective dates. Start or update the TOPdesk change with appropriate activities for HR, IT and facilities.
Revoke, recover and complete
Connect revocation of access and groups to asset returns. Update relationships and records, keeping open activities visible until their outcome is known.
Complete the loop with HR
Return confirmed changes or revocations to TOPdesk activities and, where agreed, the HR source. Employee records, execution and follow-up stay aligned.
Back to AFASReturn the outcome to AFAS too.
AFAS can supply data and receive outcomes. Have a completed workflow step update agreed data in AFAS. This is a separate route, not an automatic reversal of every sync.
Identify confirmed execution
Use the confirmed completion of an activity, such as account creation. The outcome, not merely the command, triggers feedback.
Define what AFAS should receive
Service Automation Suite applies matching, mapping and processing rules. Only selected data is written back.
Update and record the outcome
Process through the available AFAS interface and link success or failure to the original workflow.
Manage accessApproved. Executed under control.
Connect an approved request to account or access actions. Policy and authorisation remain authoritative.
Record the decision
Check the approved person, access and duration. An unapproved request does not authorise execution.
Choose the executor
Execute the available account or group action through the configured connection. If HelloID manages the lifecycle, Service Automation Suite connects to it without duplicating its rules.
Report the result
Record whether the action succeeded. Route errors or exceptions to the authorised operator; sending a command is not proof of successful execution.
SSP, forms & execution
Your SSP request sets the whole process in motion.
From requesting an asset to executing a change: combine your TOPdesk SSP with Service Automation Suite forms, current data and actions in other systems.
What Service Automation Suite coordinates centrally
Service Automation Suite brings TOPdesk stock, filters and central registers into your form. The matrix and answers determine additional questions, approvals and activities. Execution, signing and registration follow, with feedback to the request.
What this enables
From request to recorded execution. The selected asset, owner, status and documents stay connected to the same change or activity.
For example, in your setup
Automate SSP requestsFrom an SSP request to execution and feedback.
The employee starts in the TOPdesk Self-Service Portal. Service Automation Suite coordinates the next steps, including data, choices or actions needed from other systems.
Start with context
Use the request and existing person, organisation and asset data as the starting point. Apply the agreed matrix to determine questions, choices and approvals.
Complete the information and execute
Request missing information through a form and let answers start or update additional activities. Connect approvals, manual tasks and system actions to the same request.
Return to the requester and record
Record confirmed outcomes in TOPdesk and return status and results to the original request. Follow up errors or missing confirmations instead of incorrectly closing the request.
Forms in your SSPCurrent stock and relevant choices in your form.
Use Service Automation Suite forms from your SSP and combine TOPdesk information with data from other sources. The form is part of the process, not just an input screen.
Retrieve available options
Read assets and stock from TOPdesk and filter by type, location and availability. Also use central tables or data from other applications for selection lists.
Adapt questions to the situation
Use the matrix, existing data and previous answers to determine additional questions or choices. Ask targeted follow-up questions for onboarding or an asset request.
Put the choice into action
Record the answer against the correct person, change or activity. Start configured follow-up actions such as approval, handover, signing and registration, and return the outcome.
Asset handoverSelect an asset, request a signature and record the handover.
For example, issuing a laptop from a TOPdesk change. Go beyond sending a signing request: keep the selection, asset, employee and confirmed handover together.
Select with the right context
Let the employee or operator select an available asset through a form. Filter by type, location or stock and record the relationship to the correct change or activity.
Connect signing to its outcome
Use the selected details in the ValidSign document. Sending a request does not complete the handover: make the next step depend on the confirmed signing status. Rejection or failure requires follow-up.
Update relationships, records and administration
After the agreed confirmation, assign the asset to the employee and record status and document in the activity. The same process can forward the signed document to the correct HR record, for example in AFAS.
Trigger Service Automation Suite from TOPdeskA TOPdesk event starts the next steps in Service Automation Suite.
Let a request, status change or activity start a Service Automation Suite process through a configured action sequence or API call. The user keeps working in TOPdesk.
Define the trigger and context
Define which event starts the action and which reference to the ticket, change or activity accompanies it. Configure access for that call.
Coordinate the workflow
Service Automation Suite retrieves required data, applies conditions and matrices and executes agreed steps in other systems. A form can supply missing information.
Return the outcome
Return the outcome and any errors to the original record. Base the next step on confirmed processing.
SigningOne signature. A complete record.
Connect a request or activity to digital signing. Keep the document, signing status and follow-up with the same record.
Request ready
The document and signer details are checked. An agreed status or activity triggers the next step.
Request signatures
Service Automation Suite can start a signing request in ValidSign and retrieve or receive its available status. Agree how to handle rejection, expiry or errors.
Back in TOPdesk
Return the status and signed document to the original record. Complete the activity only after the agreed check.
Sign for equipmentEquipment handed over. Receipt confirmed.
An employee joins or changes roles. Connect the HR change to a laptop or phone handover and request digital confirmation of receipt, for example through ValidSign. Service Automation Suite brings the employee, asset, document and follow-up together. Configuration follows your rules and the available interfaces.
Define the equipment handover
Use employee and role data from the chosen HR source. Check the assigned equipment, required approval and handover owner. Link employee and asset to the same request or activity.
Request confirmation of receipt
Prepare a receipt or equipment loan declaration with the correct employee and asset data according to your rules. Start a signing request in ValidSign, for example, and track the available signing status. Sending a request does not mean receipt has been confirmed.
Store evidence and follow up exceptions
After confirmed signing, store the document or its reference with the correct asset and record, for example in TOPdesk. Assign an owner to declined or expired requests and missing data. Configure feedback to HR only where available and agreed.
Organise changesA change that does not stop at approval.
Make change management repeatable: the right questions, approvals and activities, with clear ownership. Service Automation Suite connects actions beyond TOPdesk and brings outcomes back.
Start with a workable process
Configure a change template with required information, authorisation points, activities and owners. From a workplace request to an office move.
Connect decisions to execution
Let approved activities trigger system actions: request signatures, update data or manage access. Manual tasks remain part of the same workflow.
Know what is actually complete
Return results to the change and its activities. The team can see which steps are complete and where someone still needs to act.
ReservationsBook a room. Keep both environments current.
Reservations keeps room bookings aligned in Outlook and TOPdesk in both directions. No need to create, update or cancel twice. View availability from Outlook or Exchange.
Book in Outlook or TOPdesk
Create the room booking in the environment where you work. Reservations processes it in the other environment too.
Align updates and cancellations
Keep updates and cancellations aligned in both environments, so cancelled bookings do not keep rooms unnecessarily unavailable.
Surface conflicts and status
Receive a notification for a conflicting booking and review processing status in the portal. Track availability and exceptions without comparing two calendars manually.
Suppliers & collaboration
Collaborate without retyping the work.
Customers, suppliers and internal teams each work in their own environment. A handover only works when context, ownership and feedback travel with it.
What Service Automation Suite coordinates centrally
Service Automation Suite connects agreed information and process steps across parties. Define what is shared, how statuses are mapped and who acts when an update or confirmation is missing.
What this enables
The service team keeps progress together. Administrative processing can continue too, such as sending time entries to the correct customer or project in AFAS.
For example, in your setup
Customers & suppliersYour own service tools. Shared progress.
Stop calling suppliers for status updates. Collaboration Composer (CC) connects customer and supplier service environments to TOPdesk. Contracts and service agreements stay in TOPdesk; CC connects execution across parties.
Agree the handover
Define which ticket goes to the other party and which customer data, fields and attachments may be shared.
Connect tickets
Service Automation Suite can create or update linked tickets and map agreed comments and statuses to the other environment.
Keep progress together
Return updates to the original ticket. Keep handover failures, conflicts and missing feedback visible.
Time entries to AFASService work in TOPdesk. Processing in AFAS.
Connect time recorded on tickets, changes and activities to the right customer or project in AFAS. Current person and company data provides the foundation.
Collect service time
Use agreed time records and their related person, organisation and work.
Match customer and project
Match the sales relationship and project in AFAS. Route missing data for review.
Process after the agreed review
Connect data to time accounting or invoicing. Finance retains review responsibility; the workflow receives the outcome.
Checks & follow-up
Detecting a deviation is just the start.
A report or technical alert does not resolve a deviation. You need to know whether it is valid, what risk it poses and who will follow up.
What Service Automation Suite coordinates centrally
Service Automation Suite compares the actual situation with your records and agreed rules. Enrich signals with business context, request an assessment and start a targeted activity or corrective action.
What this enables
Decisions, actions and outcomes remain traceable. This supports internal checks and audit preparation without treating a sent command as proof of execution.
For example, in your setup
IAM & auditabilityFrom access decision to demonstrable execution.
A closed ticket does not explain why access was granted or what actually happened. Connect the IAM decision to approval, TOPdesk activities and outcomes from the systems involved. Support auditability and accountability, including within BIO2.
Record the decision with the request
Connect the person, reason and required approval to the requested access or assets.
Connect activities to actual outcomes
Return system actions and manual confirmations to the TOPdesk change and activities. A sent command does not prove successful execution.
Keep exceptions actionable
Show what was executed, what differs and who must act. This supports controls and reviews; compliance also requires appropriate policies and operations.
Alerts & follow-upFrom a technical alert to actionable work.
Connect monitoring to TOPdesk. Go beyond creating a ticket: add context and enable the right party to take action.
Identify what needs attention
Receive a relevant alert and match it to the customer, device or affected service.
Make the ticket actionable
Enrich the ticket and apply agreed priority and routing. Identify repeated alerts to avoid unnecessary duplicate work.
Enable the right team
Connect the incident to its owner or supplier and track resolution. Return recovery information or the next step according to your process.
Data & BI
Use your TOPdesk data beyond TOPdesk.
Combine service data with the rest of your organisation for analysis, reporting or targeted customer information.
What Service Automation Suite coordinates centrally
Service Automation Suite reads data, combines it with shared relationships and prepares it for its intended use. Configure the appropriate selection, access and checks for each consumer.
What this enables
A usable data foundation for BI and scoped customer information without giving every consumer direct access to all source systems.
For example, in your setup
TOPdesk data for BIRead data and prepare it for analysis.
Use available TOPdesk data through APIs and OData where available, enriched with data from other systems. Prepare a coherent dataset for BI.
Read the relevant data
Retrieve agreed tickets, activities, people or assets through configured access. Define the fields and selections needed for reporting.
Relate and prepare
Use shared tables to identify customers, owners and devices. Combine sources and align definitions and values before making them available to BI.
Maintain and verify
Configure refresh and validation. Surface failed processing so incomplete datasets are not unknowingly used as current information.
Targeted customer informationMake information available without exposing everything.
Give a customer or other consumer access to agreed information through a configured endpoint, not the entire underlying TOPdesk environment.
Define what may be shared
Define permitted records, fields and customer selection per consumer. Exclude internal information from the published selection.
Configure access and filtering
Configure authentication, permissions and processing in Service Automation Suite. Enforce the scope for every request, not just in the form display.
Test and maintain
Test permitted and denied access. Agree who maintains selection rules and access as customers, data or systems change.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect TOPdesk 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
Transfer a ticket and receive its resolution
Connect and test
API ComposerChoose 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 ComposerSelect 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 ComposerBuild 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 ComposerConfigure 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.
- Ticket number and external reference
- Store the relationship between both records in a shared table and reuse it for subsequent updates.
- Status, priority and support group
- Translate codes using centrally managed tables. An external status does not automatically close the internal ticket.
- Response, resolution and outcome
- Write the available response to the related record and check agreed completion conditions.
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 ComposerFrom 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 blocksBeyond 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.
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.
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 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.
Start with what you need now.
Start plan from €595 per month.
Use our TOPdesk expertise to configure the first step together. Check plan capacity and terms; we agree the configuration and support needed.From product to workflow
TOPdesk in your workflow
Clothing & equipment
Equipment issue and return with the safety region
Connect NIPV to activities for the region. Confirm equipment issue and return, update records and follow up missing equipment.
Explore the scenario under Company assetsPart of one workflow
From delivery to current asset records
Supplier data creates the initial record. Then compare with Intune, for example, and update TOPdesk selectively according to your source rules. Follow up exceptions and verify confirmed outcomes again.
Explore the scenario under Company assets
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.
