TD SYNNEX provides partner APIs for orders, delivery information and invoices. Explore connecting that data to TOPdesk and administration through Service Automation Suite. For government and healthcare, keep requests, partial shipments, receipt and location together and follow up missing records.
The work between your applications
Procurement data matters when the follow-up is correct.
TD SYNNEX provides partner APIs for orders, delivery information and invoices. Explore connecting that data to TOPdesk and administration through Service Automation Suite. For government and healthcare, keep requests, partial shipments, receipt and location together and follow up missing records.
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.
Procurement & receipt
A partial shipment belongs to the same request.
A municipality or healthcare organisation orders equipment for several sites. Service Automation Suite can relate order lines to requests, request receipt confirmation and keep remaining work with the responsible team.
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
Procurement & receipt
Connected workflow
Records, review and confirmation
Link internal and external references
Relate the approved request to the supplier order and its lines. Retain sites and cost centres from your own administration.
Process partial shipments without duplicates
Recognise each shipment and repeated update. Add available serials and confirm receipt before recording equipment as issued.
Verify records and completion
Compare quantities, available identifiers and receipt with TOPdesk and the agreed operational source. Route missing data or discrepancies to a task; an invoice does not prove deployment.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect TD SYNNEX 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
API availability varies by region, platform and partner agreement. Check order, shipment and invoice fields available to your account; serial numbers are not guaranteed for every product. Start with read access and controlled record updates. Purchasing requires separate approval. 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.
Request, order and line reference
Store the relationship between the internal request and available external references. Recognise repeated updates before creating anything.
Item, person, location and available status
Map only available data and define the source for each field. Dispatch status does not confirm receipt or handover.
Confirmed receipt, exception and follow-up task
Update records after the agreed checks. Fitness-for-use decisions for protective equipment remain with authorised personnel. An uncertain order outcome requires review before retrying.
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.
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.
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.
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 TD SYNNEX
Company assets
From delivery and handover to management and returns. Connect records to what management tools actually observe.
