Hudu supports IT documentation including assets and articles. Explore connecting documentation to TOPdesk and asset records through Service Automation Suite. For government and healthcare, including MSP delivery, keep site documentation and ownership current and verify handover before treating a change as complete.
The work between your applications
Operational documentation aligned with actual records.
Hudu supports IT documentation including assets and articles. Explore connecting documentation to TOPdesk and asset records through Service Automation Suite. For government and healthcare, including MSP delivery, keep site documentation and ownership current and verify handover before treating a change as complete.
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?
Start with one integration, register or check. Build on the same data and rules.
Documentation & handover
Change completed. Is the site documentation current too?
A department receives new equipment or a site changes. Service Automation Suite can compare agreed documentation fields with asset records and assign a targeted task to the documentation owner.
Service Automation Suite · Central coordination
Match, compare and follow up
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Source & context
Documentation & handover
Connected workflow
Records, review and confirmation
Scope customer and content
Relate the Hudu company to the correct organisation and select relevant asset fields or article links. Exclude patient records, passwords and secret keys from this data flow.
Compare agreed sources
Define the authoritative source per field: for example site and owner from TOPdesk and technical observations from management tools. A documentation copy is not automatically authoritative.
Verify handover
Have the administrator review proposed updates and update agreed fields. Return the document reference and confirmation to the TOPdesk change.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect Hudu to your other applications, map the data and use the response in the next step. Configure it centrally in Service Automation Suite.
Agree access and application scope
Hudu documents a REST API; detailed endpoint documentation is hosted in your own instance. Scope the API key to required companies and IP addresses. This example does not use password access or destructive actions. Validate available fields and write permissions first. This is an integration scenario, not a pre-tested Service Automation Suite connector.
Choose 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.
Build 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.
Configure 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.
Record ID, document and recipient
Validate the agreed data and record its relationship to the external request.
Request reference and status
Use the available API status for follow-up, distinguishing completion, rejection, expiry and technical failures.
Document and confirmed outcome
Store the available result with the related record. A sent request is not yet a completed activity.
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.
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.
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.
Signature declined. Keep the process moving.
A request awaits a ValidSign signature. Declining, expiry and technical failure each need different handling.
Combine
Link the request, signing request and document. Read the available status and apply agreed conditions to determine the next action.
The outcome determines what follows
Signed: process the document and confirm the activity. Declined: route the reason to the owner. Temporary technical failure: retry only under the configured error rule.
The benefit
Appropriate follow-up for each outcome without counting a sent signing request as completed work.
Temporary access, with the end handled too.
Additional access is approved for a limited period. A checkbox alone does not preserve why, for whom and until when.
Combine
Connect identity, approval, expiry date and the available access action. Reuse the same data for a scheduled follow-up check.
The outcome determines what follows
Revocation confirmed: record the result. Extension requested: ask for a new decision. Not revoked: raise the exception with the authorised group rather than silently completing it.
The benefit
Fewer forgotten exceptions and a traceable relationship between approval and actual access.
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.
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.
Build on the same foundation
More with Hudu
Data & administration
Connect source data and references. Surface discrepancies and route them for follow-up.
