Ivanti Neurons
for LuumenAI
Read, update, and file Ivanti Neurons tickets and changes from the work itself.
Bring Ivanti Neurons tickets and changes into the work itself. LuumenAI reads the ticket, pulls the linked configuration items, follows the matching runbook, and writes back what it did — with change requests drafted from the plan and updates posted only after a human approves them.
The Ivanti Neurons toolbox
16 tools: 8 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadLook up ticketRead a ticket, its history, and linked CIs into the conversation.
- ReadSearch tickets & changesFind related incidents, problems, and changes by CI, host, or text.
- ReadGet ticket commentsWork notes and customer comments on a ticket.
- ReadList my ticketsOpen tickets assigned to you or your group.
- ReadGet change calendarScheduled changes for a CI or window.
- ReadList knowledge articlesArticles linked to a ticket or CI.
- ReadGet SLA statusTime remaining on response and resolution SLAs.
- ReadGet approvals pendingChanges waiting on an approver.
- WriteAdd work notesPost an update summarizing what LuumenAI found and did. Approval by default
- WriteFile change requestDraft a standard or normal change with the planned steps attached. Approval by default
- WriteResolve or closeMove a ticket to resolved with the audit trail attached. Approval by default
- WriteAssign ticketReassign to a person or group. Approval by default
- WriteSet priorityChange priority with the reason recorded. Approval by default
- WriteAttach evidenceAttach logs or screenshots to the record. Approval by default
- WriteLink ticketsRelate incidents, problems, and changes. Approval by default
- WriteRequest approvalRoute a change to its approver. Approval by default
One prompt, start to finish
What a governed Ivanti Neurons run looks like inside Luumen.
Questions
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — add work notes, file change request, resolve or close, assign ticket, and more — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Ivanti Neurons — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Put Ivanti Neurons to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.