Custom integrations
Standard connectors cover the common systems. The one that actually matters — the national registry, the legacy finance system, the sector platform nobody else integrates with — has none. So it becomes a bespoke script, written once, understood by one person, and unmaintained the day they move on.
Our in-house developers build those connections, and they write, test, document and support them. That includes the ones we maintain ourselves: the n8n Connector for Ivanti Neurons for ITSM, and the Jira Sync Plugin.
Because they are supported products rather than one-off scripts, the person who wrote yours is not the only person who understands it.
Data stops being re-keyed between systems, and the integration survives both the next upgrade and the next staffing change.
Have a question? Book a meeting
Common questions
Do you already have the one we need?
Quite possibly, and it is worth checking first. There is a range of ready-made integrations and plugins for Ivanti Neurons for ITSM, connecting to Jira, sending SMS, routing a shared mailbox into the right kind of ticket, and driving n8n workflows. Those you subscribe to rather than commission.
And if it does not exist?
We build it. It begins with a requirements meeting that pins down exactly what the integration has to do, and that scope goes into the agreement, so what gets built is the thing that was agreed, demonstrated in your own environment when it is handed over.
How do you work out how big a job it is?
By what it has to do rather than which systems are involved. Connecting to one system's API, pulling data in on a schedule, or feeding a dashboard is a contained build. Moving data between several systems, applying your own logic along the way, or anything that needs heavy testing before it can be trusted is a larger one. You are told which before committing.
Who keeps it working afterwards?
We do. The first year comes with the build, and after that it continues as a yearly subscription covering product updates and a support allowance. The integration does not quietly become your problem the day it ships, which is what usually happens to a script somebody wrote once.
What if our system is old, or has no proper API?
Nearly always there is a route to it. Which one depends on the system, and working that out is part of the requirements meeting, not something you need to have answered before talking to us.
What do you need from us?
The system at a version we can work with and its API reachable, credentials and network access at both ends, and someone we can talk to for the readiness check and afterwards for support. Integrations are built, tested and handed over remotely.
What if we need changes later, or more help than the subscription covers?
Both are added in blocks of days against a scope agreed first. That keeps a change a piece of scoped work rather than an argument about what the subscription was supposed to include.
Do we have to pay for the n8n nodes?
No. Our n8n nodes are free and open source, published by us and verified by n8n, and anyone can install them from n8n's own node panel. What a subscription licenses is the Ivanti-side piece, the part that lets Ivanti call an n8n workflow, hand it the record, wait for the answer and act on it.
Discuss your ITSM needs
Clients benefit from a no-commitment call to discuss their specific requirements.
a call