Across teams and systems
Connect HR, IT, facilities, finance and suppliers through shared data and rules. Your process shapes the setup.
All integrations
Service & progress
HaloITSM brings tickets, service requests and your service team's work together. Service Automation Suite connects that service delivery with your other applications and suppliers. Keep relevant data and progress together, with HaloITSM as your team's workplace.
Continuity, experience & maintenance
Why Service Automation Suite alongside HaloITSM?
HaloITSM’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.
From product to process
How to use the integration
Connect service desks
Exchange agreed tickets, comments and statuses with a customer, supplier or another team.
Assets → CMDB
Synchronise agreed device fields with your CMDB, for example TOPdesk or ServiceNow.
Request → execution
Link service requests to approvals, tasks and supported system actions.
Combine into one controlled process
Data → rules → execution-
Combine
Request + customer + existing record
-
Determine & check
Apply rules and determine follow-up
-
Execute & report back
Involve another service desk · Execute tasks · Return status
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
Work from HaloITSM.
Connect the next steps.
Your team works in HaloITSM. Connect tickets, progress and relevant data with other teams and applications without repeatedly entering the same information. Service Automation Suite keeps follow-up connected to the original ticket: who needs to act, what has been done and what still needs attention?
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
For 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.
Customers & suppliers
The service continues. The information does not.
Exchange tickets, actions and available asset context with HaloITSM. Let Service Automation Suite track status and exceptions between service teams.
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.
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.
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
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 HaloITSM 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.
From product to workflow
HaloITSM 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.
