Insights & updates from our experts
A new standard integration lets organizations that use Xurrent connect with customers and providers that use TOPdesk software. This integration allows for requests, changes, attachments and other data to be transferred between both organizations while ensuring that information stays in sync.
The Xurrent TOPdesk Connector, created by Joost-IT, is a near real-time two-way integration between TOPdesk and Xurrent, making it possible for organizations to work from a single source without switching between platforms. Employees will be less prone to making errors in the process, leading to increased efficiency and productivity and introducing businesses to a more seamless collaboration with customers and suppliers.

Stephen Ley, managing partner at Joost-IT, said: “Software integrations, especially between different organizations, can account for a significant share of specification, coding and testing efforts during software implementations. Standard Connectors like this can greatly diminish both the lead time and the costs for such projects.”
Stephen Ley – Managing Partner at Joost-IT
To set up the Connector, Joost-IT organizes a workshop with the different stakeholders to determine and define when and which information should be exchanged between the two platforms. The gathered information is captured in the functional specification document. After document approval and validation by a Joost-IT integration specialist, the actual connection is configured and tested in a QA environment in close collaboration with all stakeholders. Deployment to production is done after customer approval and testing, to ensure a successful deployment. The lead time for such a connection is about 4 weeks.
More information about the integration can be found in the Xurrent TOPdesk product brochure.

A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.






.webp)





.webp)
.webp)














