PowerShell with Qixium Agent: scripts and results

Wiki ยท 1.1

Configure LocalScripting for schedules, User Actions or IDU; exit codes, JSON and webhook completion.

Keep using your PowerShell expertise

LocalScripting executes local PowerShell scripts through the Qixium Agent. Use a configured schedule, User Action or IDU automation to run an existing administrative action or export as part of the wider workflow.

Configure LocalScripting

  1. Create a LocalScripting connection and assign the correct Agent.
  2. Reload Agent configurations and open the generated file in C:\Qixium\configs\LocalScripting.
  3. Set ScriptFolder to the managed script directory, escaping backslashes in JSON.
  4. Place the approved .ps1 file there, reload again and check status.

Schedule or trigger execution

The Scheduler action uses application LocalScripting, action Run Script, the configured connector and script. User Actions can attach execution to supported record triggers. IDU can include the action in employee automation. Define permitted inputs, repeat-run handling and local permissions.

Return errors as errors

The supplementary IDU reference specifies exit code 0 for success and non-zero for failure. Handle cmdlet errors explicitly and verify outcomes before allowing dependent work.

Result Variables require clean JSON

When Result Variables are enabled, stdout must contain only the agreed JSON object. Extra output from Write-Host, helper cmdlets or transcripts can invalidate the result. Keep operational logging separate and free of secrets. This illustrative example does not change AD or databases and has not been run on your Agent.

$ErrorActionPreference = 'Stop'
try {
    # Example without AD or database changes.
    $result = [pscustomobject]@{
        success = $true
        checkedAtUtc = (Get-Date).ToUniversalTime().ToString('o')
    }
    $result | ConvertTo-Json -Compress | Write-Output
    exit 0
}
catch {
    [pscustomobject]@{ success = $false; errorCode = 'SCRIPT_FAILED' } |
        ConvertTo-Json -Compress | Write-Output
    exit 1
}

Webhook completion

The supplementary reference describes Output Capture Mode: Webhook for certain complex scripts and sessions, reporting output, success and exitCode with the current request context. That IDU reference is archived in Confluence: confirm the callback and supported mode for your installed version. Do not copy another instance's URL or hardcode credentials.

Script to CSV to service workflow

A controlled script exports required AD fields. CSV Reader reads the export and Data Link maps rows by a stable key. The configured next step can update agreed service records. Check export failure, empty files and missing keys before downstream writes.

Explore PowerShell integrations

Back to Agent and connectors

Sources and version

Sources reviewed on 6 November 2026. Screen names and capabilities depend on your installed version and configuration.

View the current version in the wiki