Alerts → service desk
Turn relevant alerts into service tickets with device context and agreed routing.
All integrations
Alerts & status
Pass tickets to TOPdesk through Collaboration Composer. Connect asset data through API Composer and DFC.
From product to process
How to use the integration
Assets → CMDB
Synchronise agreed device fields with your CMDB, for example TOPdesk or ServiceNow.
Exceptions → tasks
Route missing information or discrepancies to the team responsible for follow-up.
Combine into one controlled process
Data → rules → execution-
Combine
Alert + device + service rules
-
Determine & check
Add context, determine priority and route
-
Execute & report back
Create or update ticket · Involve the right team · Track resolution
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
Alert received.
Who takes action?
Service Automation Suite connects N-central 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 IntuneFor example. Also with other teams, suppliers and applications.
Verify. Inform. Report.
What is complete? Who needs to act? Which exception needs attention?
Maintain records Popular
Keep reality and records aligned.
Use available inventory data to update your CMDB or asset records. Keep ownership and discrepancies visible.
Combine data and apply rules
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Relevant data or workflow status
Update, execute and record outcomes
Match the data
Match available devices or resources to existing records using stable identifiers.
Update selectively
Agree the authoritative source for each field. Update only necessary data and avoid duplicate records.
Follow up differences
Have missing data or discrepancies reviewed by the team responsible for the asset.
Alerts & follow-up
Monitoring sees it. Does your service desk?
Pass tickets to TOPdesk through Collaboration Composer. Connect asset data through API Composer and DFC.
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.
Relevant data or workflow status
Update, execute and record outcomes
Receive the signal
Use the available status or event and identify repeated alerts.
Add context and routing
Connect customer, device or service context where available. Apply your priority and ownership rules.
Track resolution
Create or update a ticket and keep execution and feedback in the same process.
Customers & suppliers
Your own systems. Shared progress.
Collaboration Composer connects customer, team and supplier service environments. No separate emails to discover who picked up a ticket.
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.
Relevant data or workflow status
Update, execute and record outcomes
Share the relevant ticket
Define the ticket and context the other party needs. Keep unshared information in its own environment.
Connect progress
Align agreed fields, comments and statuses.
Track resolution
Return updates to the original request and surface missing feedback.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect N-central 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
Turn an alert into coordinated work
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.
- Alert reference and device ID
- Relate the alert to the known asset and any existing ticket before creating new work.
- Severity, customer and responsible group
- Use shared mappings and routing rules to determine priority and follow-up.
- Recovery notification and follow-up check
- Return the available recovery status and separately determine whether service handling is complete.
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.
A replacement laptop without losing context.
An employee receives a replacement device. The old asset, new record and open service or security tickets must remain connected.
- Combine
- Use the central relationship between owner and device identifiers. Combine handover, technical inventory and return with existing tickets.
- The outcome determines what follows
- Receipt confirmed: update ownership and relationships. Old device missing or uncertain match: start a targeted review instead of overwriting historical records.
- The benefit
- Current records and a traceable handover even when a management tool uses different names.
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 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.
From product to workflow
N-central 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.
