Issue with the servicenow- uipath spoke integration: actions not passing inputs

Gaurav Vaze
Kilo Sage

Hello experts,

I am working on integration request to integrate with UiPath

I have installed the spoke and connection is done

Now when I am trying to use the action Add Item to Queue, I was getting dynamic input error

after diving deep, I saw the 2 interdependent actions- Get Folders and Get queues were turned off, so I copied them and activated

Yet I had same error for queue name

so instead, I used the toggle script and returned the queue name

Now the main problem is I want to pass the specific content in the form of array.object form, which I managed through script
but when the action is fired, even when the input is going well, I see output as Null

The queue is getting fired at Uipath but yet the specific content is not there

GauravVaze_0-1768581004997.pngGauravVaze_1-1768581111363.png

 



Has anyone previously worked on UiPath integration, and know the workaround then please LMK

any help will be highly appreciated

Thank you!

 

 

Gaurav Vaze

ServiceNow Developer

8 REPLIES 8

I see, I’ve confirmed this isn’t about array vs object. The UiPath Spoke ‘Specific Content’ behaves as null unless the input type matches what the action expects. In some UiPath Spoke actions, ‘Specific Content’ is effectively a String field expecting JSON text, not a native object—so passing a dictionary coerces to null. The only reliable way to validate is to hardcode Specific Content to {"ping":"ok"} (and if needed {"content":{"ping":"ok"}}) and see what the action accepts. The quickest way to end the debate (no guessing)

In the Flow where you call the UiPath action, set Specific Content to a hardcoded literal:

Test 1 (string JSON literal):

{"ping":"ok"}

Run it.

  • If the UiPath step still shows Specific Content = null, then either:

    • the field is not actually being mapped, or

    • the action expects a wrapper schema (example below), or

    • the action ignores Specific Content unless another field is set.

If that works, then your issue is simply that you were passing an object when it wants a string.

Test 2 (wrapper literal):

{"content":{"ping":"ok"}}

or

{"SpecificContent":{"ping":"ok"}}

Many integrations expect one of these wrappers.

@Gaurav Vaze - Please mark Accepted Solution and Thumbs Up if you find Helpful 

MJG

I used hardcoded values, still its the same

I am using Add item to Queue action from uipath spoke

You hardcoded Specific Content and it still comes through as null using the UiPath Spoke Add item to Queue action, so this isn’t an object vs JSON.stringify issue. This points to the spoke action not mapping/sending SpecificContent outbound (queue item is created but field omitted). Next step is to inspect the outbound request payload in IntegrationHub logs, and as a workaround bypass the spoke and call Orchestrator’s /odata/Queues/UiPathODataSvc.AddQueueItem directly with itemData.SpecificContent so the payload is fully controlled. Right now this feels like a spoke issue rather than a scripting issue on the ServiceNow side.

 

@Gaurav Vaze - Please mark Accepted Solution and Thumbs Up if you find Helpful 

MJG

I will check into it and let you know