IT service management · 10 pre-built actions
Ivanti integration with Nexus
Drive Ivanti service requests from governed workflows. Authenticate, work with business objects, submit service requests from templates and add journal notes as steps in a recorded run.
Pre-built actions
What you can automate
10 pre-built Ivanti actions, grouped by what they work on.
10
PRE-BUILT ACTIONS
- 01Business Objects actions create, read, update and delete Ivanti records.
- 02Service Request Templates actions read templates and their parameters.
- 03Submit Service Request and Journal Notes actions open requests and record progress.
Workflow
How it fits into a Nexus workflow
Ivanti steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Ivanti API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Request from another system
An approved request in another tool is submitted to Ivanti from the matching template, with parameters filled by Rules + Code.
Progress notes from automation
Each automated step adds a journal note so the service desk can follow what ran.
Onboarding service requests
A new hire submits the equipment and access requests your Ivanti templates define.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
FAQ
Ivanti connector questions
- Which Ivanti actions are pre-built?
- Nexus includes 10 pre-built Ivanti actions across Authentication, Business Objects, Service Request Templates, Submit Service Request and Journal Notes.
- Can Ivanti start a workflow?
- Runs that use Ivanti start from a webhook, a schedule or another trigger source. Ivanti steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the Ivanti API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- ServiceNow connector
Incidents, changes and CMDB.
- Okta connector
Identity changes driven by workforce events.
- Human-in-the-loop
Where approval belongs in a running workflow.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Ivanti fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.